What's new in version 2602.2.0.0

Aptean EDI  •  Release Note  •  6/24/2026  • 

Features  

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

  • The system supports automatic generation of outbound Aptean EDI 204 change (05) and cancellation (01) messages when a warehouse shipment is modified or deleted after the original tender (00) message has been sent. You can configure this behavior using the Warehouse Shipment Outbound Carrier Load Tender field value on the EDI Setup page. The available options are:

    • Always: The system automatically sends outbound messages without user confirmation.
    • Prompt: The system requests user confirmation before sending the outbound message.

    • No: The system does not generate outbound messages.

        
  

  • The system supports the Tab Delimited option in the File Type field on the EDI Port Card page. You can use this option to convert XML messages to and from tagged tab-delimited files by using a JSON descriptor configured on the EDI port. This file type supports complex, nested message structures for both inbound and outbound EDI processing.
    If a JSON descriptor is not configured or contains invalid data, the system stops the conversion process, displays an appropriate error message, and updates the Status field value on the EDI Message Header page to Failed. The existing XML and Text file types continue to operate without changes.

          

  • When an inbound Aptean EDI 850 message contains the AppointmentNumber text element value, the system updates the Appointment Number field value on the EDI Document page. The system uses the Appointment Number field value to populate the AppointmentNumber text element value in outbound Aptean EDI 856, Aptean EDI 856 Cons., Aptean EDI 940, Aptean EDI 940 SO, and Aptean EDI 940 Inv. Pick messages. If the Appointment Number field value on the EDI Document page is left blank, the system retrieves the AppointmentNumber text element value from the corresponding inbound Aptean EDI 850 message. If the inbound Aptean EDI 850 message does not contain the AppointmentNumber text element value, the system leaves the AppointmentNumber text element value blank in the outbound message.

          

  • The system supports additional item attribute mappings in outbound Aptean EDI 832 Price Catalog messages. The system updates the Pack, InnerPack, NetWeight, CountryofOrigin, and HTSCode text element values using the corresponding item master field values.
    When the Apparel Management extension is installed, the system also updates the RetailPrice, ColorDescription, and SizeDescription text element values using the corresponding apparel-related field values.

      

Enhancements/Modifications

   With this release of the Aptean EDI extension, you can configure the USE_LINES_SHIP_DATE port option for the EDIFACT ORDERS D96A Inbound port to control how the Shipment Date field value is updated during inbound message processing.
  • When the USE_LINES_SHIP_DATE port option is set to Yes, the system applies base calendar logic to the Shipment Date field value in the sales line and updates the Shipment Date field value in the sales header with the earliest valid shipment date. This ensures that the Shipment Date field value in the sales header is aligned with the Shipment Date field values in the sales lines.

  • When the USE_LINES_SHIP_DATE port option is set to No, the system maintains the existing behavior.

UI/UX changes

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

  • The USE_LINES_SHIP_DATE port option has been added to the EDIFACT ORDERS D96A Inbound port.
  • The INSERT_BILLTO_CUST port option has been added to the Aptean EDI 850 port.
  • The Tab Delimited option has been added to the File Type field on the EDI Port Card and EDI Port List pages.
  • The Upload JSON Descriptor, Download JSON Descriptor, and View JSON Descriptor actions have been added to the EDI Port Card page.
  • The Appointment Number field has been added to the EDI Document page.
  • The Warehouse Shipment Outbound Carrier Load Tender field has been added to the EDI Setup page.

Resolved issues

The following issues have been resolved in this release.

IDDescription
371167The system did not allow EDI messages to be reverted from the Ignored status to the Pending status on the EDI Messages page. Additionally, no confirmation message was displayed before applying the Ignore action.
370009The system incorrectly calculated the NumberOfCartons text element value in outbound Aptean EDI 856, Aptean EDI 856 Cons., and Aptean EDI 856 Level 4 messages when shipment lines contained items with the Exclude from Outbound EDI BCW field value turned on and the EDI Dispatch Advice Package Type field value was set to Pallet.
373483The system fails to automatically generate the outbound Aptean EDI 940 SO (Instruction to Dispatch) message through the Job Queue when the EDI Status BCW field value on the Sales Order page is not set to Released.
375570The system incorrectly assigns the Sell-to Customer field value during inbound sales order processing when the same EDI translation value was mapped to multiple customers.
374253The system incorrectly maps the SAC segments in outbound Aptean EDI 855 messages, resulting in incorrect allowance and charge information.
375663The system incorrectly updated the Qty. to Ship field value in the sales and warehouse shipment lines when processing Aptean EDI 945, Aptean EDI 945 SO, and Aptean EDI 945 Level 4 inbound messages containing multiple CaseLot text element values for the same item.
377273The system incorrectly updated the Bill-to Customer No. field value during manual processing of inbound Aptean EDI 850 messages, overriding the value configured on the Customer Card page.
375159The system did not apply the configured Quantity Rounding Precision field value to the QtyofChange text element value in outbound Aptean EDI 855 messages, resulting in inconsistent quantity rounding.