What's new in version 2601.0.0.0

Aptean EDI  •  Release Note  •  1/28/2026  • 

Features

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

  • The system updates the text element values based on the value selected in the EDI Reference Type field on the Item Reference Entries page while processing the multiple Aptean EDI messages.

    This functionality allows you to configure GTIN, UPC, SKU, and EAN values directly on the Item Reference Entries page, ensuring that the appropriate reference value is used during EDI message processing.

    The options available in the EDI Reference Type field are:

    • Blank
    • UPC
    • EAN
    • SKU
    • GTIN

  • The system displays a confirmation message when you update the item number in a sales order line that is associated with a processed Aptean EDI 850 message. If you select No, the system retains the EDI-related field values in the processed EDI message. If you select Yes, the system deletes the associated values from the EDI message.

  • The system updates the unit of measure value in the inbound documents as per the following hierarchy when processing any of the related Aptean EDI inbound message.

    1. The Sales Unit of Measure field value on the Item Reference Entries page.
    2. The translation value of the item unit of measure in the inbound file.
    3. The translation value of the unit of measure in the inbound file.
    4. The unit of measure in the inbound file.
    5. The EDI Unit of Measure field value on the Item Reference Entries page.

  • You can define the Sales Unit of Measure Code, EDI Qty. per Sales Unit of Measure, and EDI Unit of Measure field values on the Item Reference List page.

  • The system updates the buy-from section on the Purchase Order page while processing the Aptean EDI 210 message based on the USE_NAV_BILLTO port option.

    • If the USE_NAV_BILLTO port option is set to Yes, the system maps the buy-from address in the following order:
      1. The buy-from vendor address defined on the associated Vendor Card page.
      2. The address of the associated vendor.
    • If the USE_NAV_BILLTO port option is set to No, the system maps the buy-from address from the Aptean EDI 210 inbound file.

    The system updates the ship-to address on the Purchase Order page based on the USE_NAV_SHIPTO option on the EDI Port Options page.

    • If the USE_NAV_SHIPTO port option is set to No, the system updates the purchase order address fields directly from the Aptean EDI 210 inbound file.
    • If the USE_NAV_SHIPTO port option is set to Yes, the system updates the purchase order address fields from the ship-to address instead of using the inbound file.

  • The system sends the posted sales shipment and posted transfer shipment related details while processing the DESADV D01B L1 Sales Shipment Outbound and DESADV D01B L1 Transfer Shipment Outbound messages respectively similar to the DESADV D96A L1 Sales Shipment Outbound and DESADV D96A L1 Transfer Shipment Outbound but with different XML structure.

  • The captions of the DESADVD96A L1 SalesShipmentBCW and DESADVD96A L1 TransShipmentBCW ports have been updated to DESADVD96A L1 SaleShipExpBCW and DESADVD96A L1 TranShipExpBCW, respectively, to improve readability and consistency.

  • The system copies the configuration of the EDI port options when the Copy EDI Port Options toggle is turned on. You can turn on this toggle on the Copy EDI Port page by selecting the Copy EDI Port action on the related EDI Port Card or EDI Ports list page.

    Additionally, the system displays a warning message if a Code field value is added to an entry on the EDI Port Option List page without defining the EDI Port Code field value.

  • The system prevents the creation of a warehouse receipt if an error occurs while processing the Aptean EDI 944, Aptean EDI 944 Level 4 and RECADV D01B L4 WhseRcptImpBCW messages.

  • The system updates the CountryofOrigin text element when processing the Aptean EDI 856 messages based on the following hierarchy:

    1. The translation value defined for the Country/Region of Origin Code field on the EDI Translation page.
    2. The value in the Country/Region of Origin Code field on the related Item Card page.

    If both values are blank, the text element remains empty.

  • The system updates the UPCCode text element while processing the ORDERSD96A Purchase Order Outbound message as per the following hierarchy:

    1. The GTIN field value on the related Item Card page.
    2. The Reference No. field value on the Item Reference Entries page with the Reference Type field value set to Bar Code and the Variant Code field value defined.
    3. The Reference No. field value on the Item Reference Entries page with the Reference Type field value set to Bar Code and the Variant Code field value is left empty.

    If all these field values are empty, the UPCCode text element is left blank.

  • Enhancements have been made to the system while processing the Aptean EDI 204 OUT and Aptean EDI 204 Logistics Run messages as follows:

    • The system updates the SCACCode text element with the SCAC field value from the related shipping agent code on the Logistics Run page when Aptean JustFood is installed, or from the related Warehouse Shipment page when Aptean JustFood is not installed.
    • The system updates the LadingDescription text element with the Description field value in the related warehouse shipment lines.
    • The system processes the message when translating values, even when a value is defined in the EDI Port field on the EDI Translations page.
    • The system updates the ShipToLocation text element with the Ship-to Code field value in the warehouse shipment when it is created from a sales order. If the warehouse shipment is created from a transfer order, the ShipToLocation text element is updated with the Transfer To field value on the Location Card page.

  • You can recalculate EDI packages for posted sales shipments and posted transfer shipments when they were not created due to the Packaging No. Series field value not being defined on the EDI Setup page. For existing EDI packages, executing the Recalculate EDI Packages action replaces the current package numbers with new ones.

    However, when the action is executed without the Packaging No. Series field value on the EDI Setup page, you will receive an error.

  • The system updates the information of the Item (Charge) type in the sales order lines to the SAD segment field values while processing the Aptean EDI 855 message when the INCLUDE_LINE_CHARGES port option is set to Yes. However, this functionality is applicable only when the SAD_ALLOWANCES port option is set to No, else the existing functionality remains.

  • You can define if an EDI message has to be ignored if the status of it is new, active, or pending using the Ignore action from the All EDI Messages list page or on the respective EDI Messages page. When this action is executed from the list page, it displays a notification message. However, if it is executed on the EDI Messages card page, you will receive a confirmation message.

    If the Ignore action is executed for a message that has already been processed, an error appears.

    Additionally, all the messages with Ignored status are skipped when processed manually or through job queues.

  • The system correctly maintains data alignment in outbound ports using the text flat file type. If any text element in the XSD is incorrect, the system leaves the corresponding space empty instead of shifting subsequent values.

  • The system updates the SCACCode and Routing text elements are updated as per the following hierarchy while processing the Aptean EDI 940 Inventory Pick message.

    SCACCode

    When the Shipping Agent Code field value is defined on the Inventory Pick page,

    1. The SCAC field value on the Shipping Agents page associated with the shipping agent code in the first line of the Inventory Pick page.

    2. The translation value of the shipping agent code in the first line of the Inventory Pick page.

    3. The Shipping Agent Code field value in the first line of the Inventory Pick page.

    When the Shipping Agent Code field value is left blank on the Inventory Pick page,

    a. The Agent field value on the Sales Order page when the pick is created from sales order.

    b. The Shipping Agent Code field value on the Transfer Order page when the pick is created from transfer order.

    Routing

    When the Shipping Agent Code field value is defined on the Inventory Pick page,

    1. The translation value of the shipping agent code in the first line of the Inventory Pick page.

    2. The Shipping Agent Code field value in the first line of the Inventory Pick page.

    When the Shipping Agent Code field value is left blank on the Inventory Pick page,

    a. The Agent field value on the Sales Order page when the pick is created from sales order.

    b. The Shipping Agent Code field value on the Transfer Order page when the pick is created from transfer order.

Enhancements/Modifications

With this release of the Aptean EDI extension,

  • The system updates the Expiration field value in EDI UCC package label 5 to Mixed when printing labels for unposted documents that contain multiple lots. This enhancement addresses the issue related to bug ID #341593.

  • The system updates the BOL text element with the associated source document number when processing the Aptean EDI 210 message. When processing the Aptean EDI 214 message, the system inherits the BOL text element value and updates the Appointment Date and Appointment Time field values on the Logistics Run page based on the inherited value. This functionality applies only when Aptean JustFood is installed. This enhancement addresses the issue reported in bug ID #340211.

  • When Aptean JustFood is installed, the system updates the BOL, SalesOrder, and SCACCode text elements as follows while processing the Aptean EDI 204 Logistics Run message.

    • SCACCode - The SCAC field value of the related shipping agent code on the associated Logistics Run page.
    • BOL - The Source No. field value on the Logistics Run page.
    • SalesOrder - The Source Doc. Ref. No. field value on the Logistics Run page.

    When there are multiple Source No. or Source Doc. Ref. No. field values associated to it, the BOL and SalesOrder text elements are left blank.

    This enhancement addresses the issue reported in bug ID #340212.

UI/UX changes

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

  • The DESADV D01B L1 Sales Shipment Outbound and DESADV D01B L1 Transfer Shipment Outbound ports have been added.
  • The USE_NAV_BILLTO and USE_NAV_SHIPTO port options have been added to the Aptean EDI 210 port.
  • The INCLUDE_LINE_CHARGES port option has been added to the Aptean EDI 855 port.
  • The Recalculate EDI Packages action has been added to the Posted Sales Shipment and Posted Transfer Shipment pages.
  • The Ignore action has been added to the All EDI Messages and EDI Messages pages.
  • The EDI Reference Type field has been added to the Item Reference Entries page.
  • The Sales Unit of Measure Code, EDI Qty. per Sales Unit of Measure, and EDI Unit of Measure fields have been added to the Item Reference List page.
  • The Copy EDI Port Options toggle has been added to the Copy EDI Port page related to the EDI Port Card and EDI Ports list pages.
  • The Ignored option has been added to the Status field on the General FastTab of the EDI Messages page.
  • The captions of the DESADVD96A L1 SalesShipmentBCW and DESADVD96A L1 TransShipmentBCW ports have been renamed as DESADVD96A L1 SaleShipExpBCW and DESADVD96A L1 TranShipExpBCW, respectively.

Resolved issues

The following issues have been resolved in this release.

IDDescription
344891
  • The system incorrectly updates the item charge amount from the SAC13 text element when a UOM conversion exists for the related item while processing the Aptean EDI 810 or Aptean EDI 855 messages.
  • The system fails to apply the rounding precision defined on the EDI Port, EDI Setup, and General Ledger Setup pages, causing SAC values in outbound Aptean EDI 810 and 855 messages to differ from the inbound Aptean EDI 850 message.
341593The system fails to update the Expiration field value in EDI UCC package label 5 when printing labels from unposted documents, even though the associated warehouse shipment has an expiration date defined in the related item tracking lines.
342526The system incorrectly displays an error message only if the ShipmentIDNumber field value is defined when processing an Aptean EDI 944 or Aptean EDI 944 Level 4 message. However, the system can process the Aptean EDI 944 message when any one of the DepositorOrder, ShipmentIDNumber, or PurchaseOrderNumber text element is defined.
343469When Aptean JustFood is installed, an error occurs when executing the Send EDI Price Catalog action on the Customer Card page because the system uses the item cross reference table instead of the item reference table.
327890An error occurs when executing the Send Sales Acknowledgement action on the Sales Order page with the SAD_ALLOWANCE port option set to Yes in the Aptean EDI 855 port.
340555The system incorrectly includes the Reference section while processing the INVOIC D01B Sales Credit Memo Outbound and INVOIC D01B Sales Invoice Outbound messages even though the reference type is not defined in the related sales invoice or sales credit memo.
340556The system fails to update the catch weight item-related information when the same lot number is used multiple times while processing the RECADV D01B L4 WhseRcptImpBCW message.
340211When Aptean JustFood is installed, the system fails to update the Appointment Date and Appointment Time field values on the Logistics Run page while processing the Aptean EDI 214 message even though the corresponding values are available in the inbound file.
340212When Aptean JustFood is installed, the system incorrectly updates the BOL, SalesOrder, and SCACCode text elements while processing the Aptean EDI 204 Logistics Run message.
333361The system fails to update the lot information in the item tracking lines associated to the Warehouse Shipment page when it is created from the transfer order while processing the Aptean EDI 945 and Aptean EDI 945 Level 4 messages.
333830The system fails to update the EDI Outbound Pick Status BCW field value to Update on the Warehouse Shipment page when a value is added to the Shipping Agent Code, Shipping Agent Service Code, or Appt. Reference No. field values. This issue occurs only when these fields were previously left blank and then updated.
332641
  • The system fails to display an error message when there are no lines in the warehouse receipts related to the sales return order, purchase order, and transfer order while processing the Aptean EDI 943 Level 3 and Level 4 messages.
  • The system incorrectly includes packaging details for the warehouse receipt related to the sales return order or purchase order while processing the Aptean EDI 943 Level 3 and Level 4 messages.
323902The system fails to display the correct EDI packages on the EDI Package page related to the posted sales shipment and posted transfer shipment that are created via Aptean EDI 945 message.
337291The system fails to create the EDI packages in the Pallet > Carton > Item hierarchy as created through the SSCC. This issue occurs when the EDI packages are created by the Aptean EDI 945 Level 4 message.