What's new in version 2601.1.0.0
Features
With the features added in this release of the Aptean EDI extension,
- The system updates the UPCCode and SKU text elements when processing the Aptean EDI 832 message using item references.
-
The system automatically sets the EDI Document field value to True on the Sales Order and Posted Sales Invoice pages when the following conditions are met:
- The sell-to customer has an Invoice Port Code field value defined.
- The Send EDI Invoices for Manual Orders toggle on the related Customer Card page is turned on.
This applies when the associated posted sales invoice is created through:
- Combine sales shipments
- Sales order posting
- Sales invoice posting
- Get Shipment Lines action.
-
The system automatically updates the date fields in Aptean EDI 940, 940 SO, and 943 XML ports as follows to ensure consistent and accurate outbound messages:
The updates ensure that the dates in outbound EDI messages are taken from the correct source fields. For 940, the system uses the EDI document first and falls back to the Sales Header if needed, while 940 SO only uses the sales header. For all 943 messages (including Levels 3 and 4), the DeliveryDate tesxt element value is inherited from the transfer’s receipt date and NotAfterDate text elemnt field value from the shipment date, and if these are blank, the message fields remain blank. This keeps XML messages accurate without changing the original records.
- The system maps the TotalTransactionAmount text element value in the Aptean EDI 855 outbound message to the Amount Including VAT field value in the sales header. This value corresponds to the InvoiceTotalAmount text element in the related Aptean EDI 810 outbound message.
-
The system supports a GS1 Prefix field value length of up to 12 characters on the EDI Setup page, in line with the updated GS1 standards. Additionally, the EDI package header has been updated to ensure that the UCC128 fields correctly reflect the extended GS1 Prefix length while maintaining the total UCC128 value at 18 digits.
These enhancements ensure continued compliance with GS1 standards and support accurate SSCC barcode printing without affecting the existing 18-digit UCC128 structure.
- The system updates the unit of measure field values in outbound documents by using the corresponding field values from the Warehouse Shipments or Inventory Pick pages instead of the Sales Order page. Additionally, the system maps the text elements in the Aptean EDI 940/940 INVPICK outbound message using the following hierarchy instead of the Aptean EDI 850 values.
- The system maps the EDI translation value.
- If no translation exists, the system maps the ERP value.
- If the ERP value is not available, the system maps the EDI document value.
- If none of these values are available, the system leaves the field blank.
-
The system enhances Aptean EDI inbound 850 sales order processing & inbound 860 sales order change request to improve the accuracy and control of mapping the Requested Delivery Date and Shipment Date field values by adding the FORCE_SHIP_DATE port option.
Enhancements/Modifications
With this release of the Aptean EDI extension,
- The system skips empty EDI messages when executing the Run EDI Jobs action and continues processing the remaining messages. This enhancement prevents job interruptions and improves overall EDI processing reliability. This enhancement addresses the issue reported in bug ID #350262.
-
The following changes have been made to ensure compatibility with Business Central, version 28.
- The InitFromItemJnlLine method signature has been updated in the EDIINVRPTProcessMgmtBCW codeunit.
-
The ShowItemAvailFromItemJnlLine method has been replaced with ShowItemAvailabilityFromItemJnlLine, which uses the Item Availability Type enum in the EDIPhysInventoryJournalBCW page.
UI/UX changes
The following UI/UX changes have been made in this release.
- The Carrier Load Logistic Run EDI Port field has been added to the Shipping Agents page.
- The FORCE_SHIP_DATE port option has been added to the Aptean EDI 850 & Aptean EDI 860 ports.
Resolved issues
The following issues have been resolved in this release.
| ID | Description |
|---|---|
| 350262 | The system fails to create the Aptean EDI 204 LR message from the logistic run header when the 204 EDI LR Port field value is defined on the Shipping Agents page. Instead, the job queue processes the Aptean EDI 204 message from the warehouse shipment header. |
| 346798 | An error occurs on the Warehouse Shipment page when the FB_CREATE_SSCCS port option is set to False and the box level is incomplete while processing inbound DESADV messages. |
| 354254 | The system incorrectly processes the message or fails to validate the absence of item lines when the XML contains only packaging lines while processing the RECADV messages. This issue occurs when the FB_USE_PCKG_LINES port option is set to Yes. |
| 352306 | The system incorrectly retrieves item details from the Aptean EDI 850 inbound message when processing the Aptean EDI 810 outbound invoice message after creating a manual sales invoice using the Get Shipment Lines action. |
| 357194 | The system fails to update the QtyAvailable text element when processing the Aptean EDI 846 message. This issue occurs when the Inv. Inquiry Location Filter field value is left blank on the related Customer Card page and all the port options are set to No on the EDI Port Card page. |
| 354377 | An error occurs on the Customer Card page when processing the Aptean EDI 846 message. This issue arises when the Inv. Inquiry Location Filter field value on the related Customer Card page contains multiple locations. |
| 346128 | The system incorrectly generates duplicate SAD segments at both the header and line levels in the Aptean EDI 855 message when multiple details segments are available. This causes header charges to be applied to each line, resulting in incorrect totals. |
| 353447 | An error occurs when processing the inbound Aptean EDI 850 messages if the FB_MANUAL_PRICE and INSERT_LINE_DISCOUNT port options are set to Yes and the Aptean Advanced Pricing extension is installed. |
| 347176 | The system does not function based on the Process Shipment Outbound Dispatch Advice and Process Receipt Outbound Dispatch Advice field values on the EDI Setup page when generating or deleting Aptean EDI 940 or 943 messages from the released warehouse shipments or receipts, including those created from sales, transfer, purchase, purchase return, or sales return orders. |
| 345676 | The system fails to display the sales invoice header details on the EDI Message Linkage page after posting the sales invoice. |
| 350624 | The system fails to use the EDI translations linked directly to the EDI port for the Aptean 832 Outbound message. Additionally, the system incorrectly display the caption for the CareInfo field in the XML. |
| 347135 | The system incorrectly stops the entire job queue when processing warehouse shipments (Aptean EDI 204 messages) without a shipping agent, causing system-wide interruptions. |
| 357791 |
|