What's new in version 2604.0.0.0
Aptean EDI
•
Release Note
•
10/21/2026
•
Features
With the features added in this release of the Aptean EDI extension,
- The Aptean EDI 855 – Purchase Order Acknowledgment now populates the ShipFromLocation element from the Sales Order's Location Code using this priority:
- Location's LSP Location GLN
- ShipFromLocation-specific EDI Translation
- Generic Location EDI Translation
- Raw Location Code
- Blank if the Sales Order has no Location Code
- The existing ship-from address fields continue to fall back to Company Information when applicable.
- The outbound Aptean EDI 940 (Warehouse Shipping Order) message now includes the JCPLoadControl field in the BEG segment, sourced from the Appt. Reference No. field on the Warehouse Shipment or Sales Order. This applies to the Warehouse Shipment, Sales Order, and Inventory Pick variants of the 940 ports.
- The inbound Aptean EDI 850 (Purchase Order) and Aptean EDI 860 (Purchase Order Change) messages have been enhanced to set the sales order Location Code from the ShipFrom facility in the message, controlled by the new USE_EDI_SHIPFROM port option. When enabled, the ShipFrom value is resolved to a Location in the following order:
- The Location whose LSP Location GLN equals the ShipFrom value
- The ShipFrom value translated using an EDI Translation scoped to ShipFrom
- The ShipFrom value translated using a generic Location EDI Translation
- The Location whose Code equals the ShipFrom value
- An error when no match is found
- The resolved Location is applied to both the Sales Header and all Sales Lines, overriding the standard Business Central default.
- A blank or absent ShipFrom raises no error and leaves the Location to standard Business Central logic. When USE_EDI_SHIPFROM is disabled, the ShipFrom value is ignored.
UI/UX changes
The following UI/UX changes have been made in this release.
- The USE_EDI_SHIPFROM port option has been added to the following Inbound XML ports.
- Aptean EDI 850
- Aptean EDI 860
Resolved issues
The following issues have been resolved in this release.
| ID | Description |
|---|---|
| 392867 | The outbound EDI 856, DESADV D01B Level 4, and EDI 943 transactions were incorrectly marked as Ignored when package data generation failed, instead of being marked as Failed. This prevented failure notifications from being triggered. |
| 370104 | The inbound RECADV D01B message proposed an incorrect Weight Qty on Item Tracking Lines when processing a Catch Weight item, using the quantity value directly instead of calculating from the average weight recorded in the Item Ledger Entries. |
| 393586 | The outbound Aptean EDI 943 (Warehouse Stock Transfer Shipment Advice) Level 3 and Level 4 messages incorrectly resolved lot, expiry date, and license plate details from Item Ledger Entries instead of the existing reservation entries when a shipment contained a mix of plated and non-plated packages. |
| 392696 | The Recalculate EDI Packages action incorrectly rebuilt AWM packages using a different path than creation, created surplus package headers for drop-ship shipments, and left F&B SSCC package headers incorrectly stamped. |
| 392697 | The outbound DESADV message reported an incorrect dispatch quantity for AWM license plate packages when a pick was registered in multiple partial takes, using the quantity from a single Detailed Warehouse Entry instead of the total reserved quantity. |