What's new in version 2603.1.0.0

Aptean EDI • Release Note • 8/26/2026 •

Features

With the features added in this release of the Aptean EDI extension,

The Aptean EDI 846 (Inventory Inquiry/Advice) outbound process has been enhanced to consider Inspection Hold inventory when calculating and reporting item availability when the Aptean Inspection Status extension is installed. Inventory that is on Inspection Hold is excluded from the reported available quantity, ensuring that trading partners receive accurate inventory information that reflects only inventory available for shipment. This enhancement applies to both lot-tracked and non-lot-tracked items. For lot-tracked items, WarehouseQty entries for lots that are on Inspection Hold are suppressed.

The Aptean EDI extension has been integrated with the Aptean Inspection Status extension. For more information, see Integrations

The system supports applying purchase contract prices to inbound Aptean EDI 855 Purchase and Aptean EDI 810 PURCH messages when the Contract Management extension is installed. If an active purchase contract exists for the vendor and item, the system applies the contract cost and populates the Contract No. and Contract Line No. fields on the purchase document. If the item is an alternate item on an active purchase contract, the corresponding contract cost is applied. If no active purchase contract exists, the system continues to use the cost from the inbound EDI message.
When the VALIDATE port option is enabled and the inbound cost differs from the contract cost, the system displays the standard price validation prompt during inbound message processing

The system supports applying sales contract prices to inbound Aptean EDI 850, Aptean EDI 860, ORDERS D96A Sales Order Inbound, and Aptean EDI 945 Level 4 Sales Invoice messages when the Contract Management extension is installed. If an active sales contract exists for the customer and item, the system applies the contract price and populates the Contract No. and Contract Line No. fields on the sales document. If the item is an alternate item on an active sales contract, the corresponding contract price is applied. If no active sales contract exists, the system continues to use the price from the inbound EDI message.
When the VALIDATE port option is enabled and the inbound price differs from the contract price, the system displays the standard price validation prompt during inbound message processing.

The Aptean EDI extension has been integrated with the Aptean Contract Management extension. For more information, see Integrations

With this release of the Aptean EDI extension,

The inbound Aptean EDI 856 Purch message processing has been enhanced to improve warehouse receipt matching. When an ASN is received with a blank Bill of Lading field, the system matches the ASN against the purchase order lines instead of requiring a Bill of Lading value. When a matching unposted warehouse receipt exists for the same purchase order lines, the system updates the existing warehouse receipt and increases the quantities. If no matching receipt is found or the existing receipt has already been posted, the system creates a new warehouse receipt.
The ALWAYS_CREATE_RCPT port option controls warehouse receipt creation when processing an ASN:
- Yes — The system always creates a new warehouse receipt for each ASN, regardless of whether a matching unposted warehouse receipt exists.
- No — The system updates the existing matching unposted warehouse receipt instead of creating a new receipt.
The system no longer writes the Bill of Lading field value to the Vendor Shipment No. field on the Purchase Order page. The value is written only to the warehouse receipt, where it is used as a matching key and traceability reference.
When an ASN does not contain usable item detail records, the system displays a descriptive failure message indicating that no item detail was found and no warehouse receipt was created, instead of continuing silently or displaying a cryptic error.

The outbound Aptean EDI 810 (Invoice) message has been enhanced to correctly handle item charges when both a consolidation port option and INCLUDE_LINE_CHARGES are enabled. A new Text port option, ADD_CHARGES_TO_PRIC2, allows users to define which item charges are consolidated into the item's unit price and which are reported as separate SAD (Service Allowance/Charge Detail) segments, ensuring each charge is reported exactly once and the 810 total is accurate.
The ADD_CHARGES_TO_PRIC2 port option controls how item charges are reported in the outbound Aptean EDI 810 message:
Absent — All item charges are consolidated into the unit price, preserving existing behavior.
Present but blank — No item charges are consolidated. All charges are reported via the existing paths.
Present with codes — Only the listed item charges are consolidated into the unit price. All other charges are reported as SAD segments or at the header level.

The outbound Aptean EDI 204 (Carrier Load Tender) and Aptean EDI 204LR (Logistics Run variant) messages now support sourcing data from posted warehouse shipment records, ensuring all required fields remain populated after posting. In JustFood, this also applies to the Logistics Run. The system automatically sends a 204 or 204LR at the time of posting if one has not already been transmitted. Users can also manually send the message after posting using the Send Outbound Carrier Load Tender action on the Posted Warehouse Shipment and Posted Load Arrival pages.

The following UI/UX changes have been made in this release.

The ALWAYS_CREATE_RCPT port option has been added to the Aptean EDI 856 Purch XML port.
The ADD_CHARGES_TO_PRIC2 port option has been added to the Aptean EDI 810 BCW outbound XML port.
The VALIDATE price option has been added to the Aptean EDI 855 Purchase port.
The Request for Routing Inst. No. of Pallets, Request for Routing Inst. No. of Cartons, and Stackable BCW fields have been added to the EDI Whse. Document page and the Warehouse Shipment page.
The Send Outbound Carrier Load Tender action has been added to the Posted Warehouse Shipment page.
The Send Outbound Carrier Load Tender action has been added to the Posted Load Arrival page.

The following issues have been resolved in this release.

ID	Description
384770	The Aptean EDI 940 (Warehouse Shipping Order) and Aptean EDI 943 (Warehouse Shipping Order Acknowledgement) outbound messages incorrectly emitted OrderStatusCode = N (New/Original) when a user re-sent a warehouse pick instruction and selected Replace or Delete in the dispatch prompt.
384037	An error occurred when copying a company, causing a "DataTransfer is only usable during upgrade and installation code" error.
381878	The system fails to process a standard inbound 855 Purchase Order Acknowledgment flat file without manual XML edits, and line acknowledgment status codes for price changes, quantity changes, item substitutions, and rejections do not update the corresponding purchase order lines.
376688	The system did not support selecting multiple records when executing the Reset or Ignore actions on the EDI Messages page for multiple inbound or outbound EDI messages.
374253	The system incorrectly displayed the "Do you want to send updated outbound instruction to dispatch?" confirmation dialog when manually sending the initial Warehouse Shipment or Warehouse Receipt EDI messages, regardless of the Process Shipment Outbound Dispatch Advice Changes and Process Receipt Outbound Dispatch Advice field values configured on the EDI Setup page.