What's new in version 2602.1.0.0

Aptean EDI  •  Release Note  •  5/27/2026  • 

Features

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

  • The system includes updates across EDI processing components, XMLports, and related pages to address warnings and ensure compatibility with Business Central version 27.

  • The system supports the creation of EDI packages for drop shipment purchase orders during inbound Aptean EDI 856 Purch message processing through the DROPSHIP_PKGS port option.

    • If the DROPSHIP_PKGS port option is set to Yes, the system creates EDI package records for purchase orders with the Drop Shipment field value set to True when a PackID text element value is available on a PackLevelRecord segment. The system also updates the related tracking information.
    • If the DROPSHIP_PKGS port option is set to No, the system preserves the existing behavior and does not create EDI package records.

    • When the purchase order is posted as a drop shipment, the system copies the EDI package records to the corresponding Posted Sales Shipment page, ensuring package information is available for outbound processing.

  • The system adds the UCC128Label text element to the ShipmentDetail element (940) and Detail element (943) of the outbound EDI XML ports.

    • When the Aptean License Plating extension is installed, the system populates the UCC128Label text element value using the Package No. field value from Reservation Entries page, allowing warehouse systems to associate shipment lines with physical license plates.

    • If the Aptean License Plating extension is not installed or no license plate is assigned, the system includes the UCC128Label text element with an empty value.

  • The system supports updating the Shipment Date field value in the sales order header based on line-level shipment dates during inbound Aptean EDI 850 and 860 message processing.

    • If the USE_LINES_SHIP_DATE port option is set to Yes, the system updates the Shipment Date field value on the sales order header using the earliest shipment date from the item lines.

    • If the USE_LINES_SHIP_DATE port option is set to No, the system preserves the existing behavior.

  • The system supports controlling the source of the Ship-to Code field value during outbound Aptean EDI 810, Aptean EDI 856, Aptean EDI 856 Cons., and Aptean EDI 856 Level 4 message processing through the SHIPTO_USE_ERP port option.

    • If the SHIPTO_USE_ERP port option is set to Yes, the system derives the Ship-to Code field value from the posted sales shipment or posted sales invoice header and applies the defined EDI translation.

    • If the SHIPTO_USE_ERP port option is set to No, the system derives the Ship-to Code field value from the corresponding inbound Aptean EDI 850 message and applies the defined EDI translation if available.

  • The system improves the file-receiving process for manual execution using the EDI One web service. When no files are available, the system displays a notification confirming that the process was completed successfully, and no files were found. This notification appears only after the process completes and does not affect scheduled or automated runs.

  • The Aptean EDI 945 XMLport supports overdelivery handling when the Aptean Over Under Delivery extension is installed. You can define the FB_USE_OVERDELIVERY port option on XMLports 14180908 (Aptean EDI 945 BCW), 14180849 (Aptean EDI 945 Level 4 BCW), and 14180909 (Aptean EDI 945 SO BCW) to control whether overdelivery quantities in inbound 945 messages are processed or rejected with an error.

    • When the FB_USE_OVERDELIVERY port option is set to Yes and the Aptean Over Under Delivery extension is installed, 945 inbound messages with quantities exceeding the original order quantity are processed using BC's native over & under delivery logic. The overdelivery is accepted and posted if the quantity is within the configured over & under delivery tolerance; otherwise, the transaction errors and stops.

    • When the FB_USE_OVERDELIVERY port option is set to No, the existing behavior is maintained and overdelivery always results in an error, ensuring full backward compatibility.

  • The system improves handling outbound EDI messages when no applicable detail lines are available for processing. When no lines are available to process, the system marks the message as Ignored instead of Error. Additionally, the system updates the related document with the corresponding EDI Outbound Entry No. field value ensuring that duplicate outbound messages are not created.

Enhancements/Modifications

With this release of the Aptean EDI extension, the system enhances UCC label generation for warehouse shipments by increasing the supported length of the Item Description field value in EDI UCC Label Package 5 (Object ID: 14180812). With this enhancement, the system allows processing of items with Item Description field values exceeding 50 characters. UCC label generation completes successfully without errors, and the Item Description field value is printed correctly based on the supported maximum length.

UI/UX changes

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

  • The EDI Packages action has been added to the Purchase Order page.
  • The UCC128Label field has been added to the ShipmentDetail element in the Aptean EDI 940 BCW, Aptean EDI 940 SO BCW, and Aptean EDI 940 Inv. Pick BCW XML ports.
  • The UCC128Label field has been added to the Detail element in the Aptean EDI 943 BCW, Aptean EDI 943 Level 3 BCW, and Aptean EDI 943 Level 4 BCW XML ports.
  • The DROPSHIP_PKGS port option has been added to the Aptean EDI 856 Purch XML port.
  • The FB_USE_OVERDELIVERY port option has been added to the Aptean EDI 945 BCW, Aptean EDI 945 Level 4 BCW, and Aptean EDI 945 SO BCW XML ports.
  • The SHIPTO_USE_ERP port option has been added to the Aptean EDI 810, Aptean EDI 856, Aptean EDI 856 Cons., and Aptean EDI 856 Level 4 XML ports.
  • The USE_LINES_SHIP_DATE port option has been added to the Aptean EDI 850 BCW and Aptean EDI 860 BCW XML ports.

Resolved issues

The following issues have been resolved in this release.

IDDescription
351097The system incorrectly creates duplicate package entries in the outbound 856 ASN document when a posted sales shipment is undone and re-shipped.
358060The system incorrectly mapped fields in the Aptean EDI 812 OUT BCW and Aptean EDI 812 OUT CrMemo BCW XML ports for sales, posted credit memo, and sales return order documents.
362409The system incorrectly handled percentage fields in EDI transaction ports 850 (14180900), 810 (14180902), 855 (14180903), and 860 (14180907), resulting in inconsistent percentage values.
362973The system fails to post the warehouse receipt when processing the inbound Aptean EDI 944 and Aptean EDI 944 Level 4 messages via the Job Queue.
365270The system fails to update the Lot Expiration Date field and left it blank on the UCC Package Label 5 (report 14180812) report for a posted shipping container.
367273The system fails to translate Chinese characters correctly during EDI transfers as the data is written to Blob Storage using UTF-8 encoding but read back without specifying the encoding.
369217An error occurs on the sales order page when creating Aptean EDI 855 Sales Acknowledgment messages for sales orders created from inbound Aptean EDI 850 messages that include header-level service allowance charges.
372055The system fails to apply quantity conversion for inbound Aptean EDI 850 item lines when the UOM segment is not present in the EDI message. As a result, the sales order line is created with incorrect quantities and default UOM handling instead of deriving the conversion from the configured item reference values.
372485The system fails to update the Sales Line Shipment Date field value on the sales orderpage from the StartRequestShipDate text element value during Aptean EDI 850 inbound message processing when the FORCE_SHIP_DATE port option is set to Yes. As a result, the shipment date is not consistently applied to sales order lines, causing a mismatch between header and line shipment dates.
339138The system fails to support warehouse-related outbound processes on the Manually Run EDI Processes report and does not display the Warehouse Shipment - Carrier Load Tender, Warehouse Shipment - Instruction to Dispatch, and Warehouse Receipt - Dispatch Advice options, preventing users from manually processing these document types.
357935The system fails to create EDI packages on the Posted Sales Shipment page using Advanced Warehouse Management license plate data for drop shipment orders when the related purchase order is posted.
369664The system incorrectly calculates the weight field (Information & OrderLevel segments) in the outbound Aptean EDI 856 Consolidated and Aptean EDI 856 Level 4 messages.
364805The system fails to populate the GTINBox and TotalNumberOfBoxes text element values correctly when processing the DESADV D01B Level 4 outbound message for both sales shipment and transfer shipment.
368474An error occurs when sending the Aptean EDI 832 Price Catalog message for a customer, stating that the sales header does not exist, even when item translation is configured on the Item Reference page.