What's new in version 2603.0.0.0

Aptean EDI  •  Release Note  •  7/22/2026  • 

Features

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

  • The system adds the Require Item Reference EDI UOM field on the EDI Setup page and the REQ_ITEMREF_EDI_UOM port option to control item reference matching during inbound message processing.
    • When the REQ_ITEMREF_EDI_UOM port option is set to Yes and the inbound message contains an EDI unit of measure value, the system matches an item only when the EDI Unit of Measure field value is defined on the Item Reference Entries page.
    • When the REQ_ITEMREF_EDI_UOM port option is set to No, the system preserves the existing behavior and matches the item even when the EDI Unit of Measure field value is not defined, allowing a fallback match.
  • The system introduces support for the Aptean EDI 753 BCW (Request for Routing Instructions) outbound port, allowing routing instruction requests to be generated from warehouse shipments. The port processes warehouse shipment information, related shipment lines, and source document data while excluding items configured in the outbound item exclusion list.
  • The system also supports automatic generation of original, revision, and cancellation routing instruction messages through the Warehouse Shipment Outbound Request for Routing Instructions field on the EDI Setup page.
  • When the Warehouse Shipment Outbound Request for Routing Instructions field value is:
    • Always: The system automatically generates revision and cancellation messages when qualifying shipment changes or cancellations occur.
    • Prompt: The system prompts the user before generating revision or cancellation messages.
    • No: The system preserves the existing behavior and does not generate revision or cancellation messages automatically. Additionally, the system adds the Send Request for Routing Instructions action to the Warehouse Shipment page, allowing users to manually generate Original, Revision, or Cancellation routing instruction messages.
  • The system supports processing the ServiceAllowanceChargeHeader records during inbound Aptean EDI 812 message processing. The system creates the corresponding G/L Account or Charge (Item) lines on the sales document and the related EDI document amount entries.
  • The system supports processing the Terms Type Code and Terms Basis Code field values from inbound Aptean EDI 850 and Aptean EDI 860 messages. The system stores the Terms Type Code and Terms Basis Code field values on the related EDI document.
    • When the TERMS_TYPE_CODE port option is set to Yes, the system updates the Payment Terms Code field value on the related sales header using the translated Terms Type Code field value.
    • When the TERMS_TYPE_CODE port option is set to No, the system preserves the existing behavior and does not update the Payment Terms Code field value.
  • When the Status Management extension is installed, the system updates the Status Mgt. Description field value during inbound Aptean EDI 860 Purchase Order Change message processing. If processing reopens a sales order, the system resets the Status Mgt. Description field value to the default value defined in the associated Status Management Flow.

Integrations

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

  • The system adds the PaymentTerms and TotalQuantity text elements to the HeaderRecord element of the outbound Aptean EDI 850 OUT BCW XML port. The PaymentTerms text element value is populated from the Payment Terms Code field value on the Purchase Order page. The TotalQuantity text element value is calculated as the sum of the Quantity field values for all purchase lines where the Type field value is Item.
  • The system also exports each purchase comment line as a separate NoteRecord text element, where the NoteInstructions text element contains the corresponding comment text.
  • The system adds the EstablishmentLocationID text element to outbound Aptean EDI 856, Aptean EDI 856 Consolidated, and Aptean EDI 856 Level 4 messages. The system populates the EstablishmentLocationID text element value using the translated Location Code field value. If no translation exists, the system uses the Location Code field value. If the Location Code field value is blank, the EstablishmentLocationID text element remains empty.
  • The system improves mapping of the ShipQtyUOM and ST AddressLocationNumber text element values in outbound SPS 856 Consolidated ASN messages. The ShipQtyUOM text element value is populated from the OrderQtyUOM text element value when available; otherwise, the system preserves the existing behavior and derives the value from the translated Package Line Unit of Measure Code field value. When the inbound message does not contain an ST address segment but includes a BY address segment, the system populates the ST AddressLocationNumber text element value from the AddressLocationNumber text element value in the BY address segment, zero-padding single-digit values to a minimum of two digits.

Enhancements/Modifications

With this release of the Aptean EDI extension,

  • The system updates the captions of fields and actions on the EDI Setup page to use the standardized <Business Central Document> - <Message Type> naming convention, providing consistent message names throughout the application.
  • The system supports recalculation of EDI Packages using license plate data. The existing F&B package recalculation logic has been moved from the Aptean EDI extension to the Aptean EDI Bridge for F&B extension.

UI/UX changes

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

  • The Require Item Reference EDI UOM field has been added to the EDI Setup page.
  • The Warehouse Shipment Outbound Request for Routing Instructions option (No, Always, Prompt) has been added to the EDI Setup page.
  • The Request for Routing Inst. No. of Pallets, Request for Routing Inst. No. of Cartons, and Stackable fields have been added to the EDI Whse. Document page.
  • The Earliest Requested Pickup Date/Time, Latest Requested Pickup Date/Time, and Deliver No Later Than Time fields have been added to the EDI Warehouse Document page.
  • The Terms Type Code and Terms Basis Code fields have been added to the EDI Document pages.
  • The Send Request for Routing Instructions action has been added to the Warehouse Shipment page.
  • The REQ_ITEMREF_EDI_UOM port option has been added to the following Inbound XML ports.
    • Aptean EDI 810
    • Aptean EDI 812
    • Aptean EDI 850
    • Aptean EDI 860
    • Aptean EDI 945 Level4 SI
  • The TERMS_TYPE_CODE port option has been added to the following ports:
    • Aptean EDI 850 Inbound
    • Aptean EDI 860 Inbound
  • The Aptean EDI 753 BCW (14180876) outbound port has been added to the EDI Ports list page.
  • The Warehouse Shipment Outbound Carrier Load Tender field has been added to the EDI Setup page.