What's new in version 2602.0.0.0

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

Features

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

  • The system enhances the identification of packaging items during inbound EDI message processing to improve item recognition accuracy. The system considers item reference entriesin addition to the GTIN field value on the Item Card page when determining packaging items, ensuring more reliable identification when multiple reference types are used.
  • You can define the CREDIT_NOTE_TYPE field value as 380 for the INVOIC D01B Sales Credit Memo Outbound message. When you set this value, the system generates negative quantities and amounts in the message. The system also sets the InvoiceType text element to Commercial Invoice.

  • The system improves catch weight (CAW) handling when processing the INVOIC D01B Sales Invoice Outbound and INVOIC D01B Sales Credit Memo Outbound messages.

    For catch weight items, the system determines the InvoicedQty and UnitOfMeasure text element values in the outbound messages based on the field values on the Applied Sales Price page.

    • If the Applied UOM field value on the Applied Sales Price page matches the UOM field value on the Catch Weight Setup page, the system uses the Catch weight quantity and Unit of Measure field values from the Applied Sales Price page to populate the corresponding InvoicedQty and UnitOfMeasure text element values.
    • If the Applied UOM field value does not match the UOM field value on the Catch Weight Setup page, the system uses the Quantity and Unit of Measure field values from the sales line to populate the corresponding InvoicedQty and UnitOfMeasure text element values.
  • The system supports integration with advanced warehouse management license plates during inbound DESADV message processing. When the Aptean Beverage Advanced Warehouse Management extension, Drink-IT Edition, is installed, the system updates the License Plate No. field value on the corresponding warehouse shipment using the SSCCPallet text element value from the inbound message.
  • The system updates the Allowance Code text element value in the outbound Aptean EDI 810 message by translating the Invoice Discount Code field value on the Customer Invoice Discount page. If no translation is available, the system uses the Invoice Discount Code field value directly to populate the Allowance Code text element value.
  • The system updates the mapping for SPS Commerce 850 Purchase Order and SPS Commerce 855 Sales Acknowledgement messages for the BuyersCurrency and SellersCurrency text element values. It also determines the Currency Code field value on the Purchase Orders and Sales Orders pages based on the LCY (Local Currency Code) field value defined on the General Ledger Setup page and any applicable EDI translation values.
  • The system includes the TotalUnitsShipped text element value in the Summary record of the outbound Aptean EDI 810 message.

  • The system enhances the determination of the Order Type Code field value in the sales header when processing the inbound Aptean EDI 850 and 860 messages.

    The Order Type Code field value is determined in the following order of precedence:

    • The Sales Order Type field value from the inbound message, if valid.
    • The translated value from the EDI Translation page, if a mapping exists for the inbound Sales Order Type field value.
    • The Default Order Type Code field value of the related bill-to customer.
    • The Default Order Type Code field value of the related sell-to customer.
    • The Default Order Type Code field value on the Style Setup page.

    If none of the above values are available, the Order Type Code field value in the sales header remains blank.

  • The system introduces additional inbound elements and mapping support for Aptean EDI 850, 860, and 940 messages.
    • For Aptean EDI 850 and 860 messages, the system maps the Store Name and Department Name field values to the corresponding EDI Document field values in the sales order.
    • For Aptean EDI 940 messages (Sales, Purchase Return, and Transfer Orders), the system maps the Department Number, Store Name, and Department Name field values from the associated fields on the EDI Warehouse Document page. The system determines the Not After Date field value using the following order of precedence: the Sales Order field value (when the Apparel Management extension is installed), the EDI Document field value, and the Shipment Date field value when no source document is available. Additionally, the system ensures that values from inbound Aptean EDI 850 messages are correctly updated or cleared during Aptean EDI 860 processing, including when fields are blank.

  • The system introduces an Apparel EDI Bridge to enhance item reference and matrix value mapping across inbound and outbound EDI message processing.

    The system supports apparel attributes including style code, color code, size code, dimension code, and their corresponding descriptions and retail price, improving item identification accuracy.

    • For outbound processing, the system determines these values using inbound message data where available and applies fallback logic using the EDI translation field values, item reference entries, and style-related field values.
    • For inbound warehouse processing, the system derives the Size Code and Dimension Code field values from item variant positions.

Enhancements/Modifications

With this release of the Aptean EDI extension,

  • The system enhances inbound Aptean EDI 947 processing to support improved journal template selection, location translation, and transfer transaction processing when creating item journal line records. The system determines the Item Journal Template field value based on the ActionCode text element value in the inbound message and selects the corresponding template configured on the Location Card page record and determines the Location Code field value using a priority-based translation of warehouse information provided in the inbound message. For transfer transactions, the system translates the NewWarehouse text element value to populate the New Location Code field value on the Item Journal page.

  • The system supports the outbound Aptean EDI 856 Reusable Packaging messages to track returnable assets such as pallets separately from standard shipments. You can define reusable packaging items using the Include in EDI Reusable Packaging Message field value on the Item Card page and configure the reusable packaging port using the Reusable Packaging EDI Port Code field value on the Location Card page.

    The system automatically turns on the EDI Reusable Packaging Shipment toggle in the sales header when a valid reusable packaging EDI port is assigned, and at least one item is marked as reusable packaging. This setting is carried forward to the Posted Sales Shipment page. You can generate reusable packaging messages using the Send Reusable Packaging Shipment action on the Posted Sales Shipment page.

    The system processes only reusable packaging items and excludes standard shipment items. Each message updates the EDI Reusable Packaging Entry No. field value, while maintaining previous entries tracking in the EDI log.

    The system also supports automatic message generation through the Job Queue when required configuration of field values and toggles are turned on. This functionality operates independently of the standard 856 shipment process.

  • The system enhances inbound Aptean EDI 850 and 860 message processing to improve integration with the Aptean Apparel module by supporting apparel-related data.

    The system determines the following field values using the defined order of precedence:

    • Cancel Date
      • The Completion Cancel Date field value from the inbound message.
      • The current system work date, if the inbound value is not provided.
    • Season Code
      • The Season Code field value is populated from the first sales line in the sales order.
    • Order Type Code
      • The inbound Order Type Code field value.
      • The translated value using EDI translation, if a mapping exists.
      • The Default Order Type Code field value of the bill-to customer.
      • The Default Order Type Code field value of the sell-to customer.
      • The Default Order Type Code field value on the Styles setup page.
    • Promo/Deal Number
      • The inbound Promo/Deal Number field value.
    • Division Code
      • The inbound Sender’s Division field value.
      • The translated value using EDI translation, if available.
      • The Division Code field value is populated from the first sales line in the sales order.
    • Department
      • The inbound Department field value.

  • The system introduces EDI price catalog functionality that allows you to define price catalogs with item reference filters and use them when generating outbound Aptean EDI 832 messages. You can also define filtering criteria using the Reference Type field value and apparel-related field values including the Season Code, Division Code, Style Color Code, Style Size Code, Style Dimension Code, and Style Code field values. The system uses these filter field values to determine the item references included in the outbound Aptean EDI 832 message.

    When you execute the Send Price Catalog action on the Customer Card page, the system prompts you to select an EDI price catalog. If a catalog is selected, the system applies the configured filter field values to determine which item references are included in the outbound 832 message. If no catalog is selected, the system generates the message using the existing logic.

  • The system enhances the quantity calculation logic for the outbound Aptean EDI 846 message when the CALC_ASSEMBLY port option is configured. When the CALC_ASSEMBLY port option is defined, the system calculates the QtyAvailable text element value based on the available quantity for items with the Assembly Policy field value set to Assemble-to-Order. Additionally, it uses the CalcAvailability text element value when executing the Order Promising Lines action to determine the available quantity based on the available assembly components.

  • The system updates existing purchase orders based on inbound acknowledgements messages. The 855 inbound message validates the purchase order using the incoming purchase order number and stops processing with an error if the order is not found.

    The purchase order lines are updated based on the acknowledgement status, including changes to quantity, unit price, expected receipt date, and item number where applicable. For rejected orders and lines, it prompts you to confirm deletion in interactive mode and stops processing with an error during job queue process.

  • You can configure the OVERRIDE_QTY port option to control the QtyAvailable text element value in the outbound Aptean EDI 846 message.
    • When the OVERRIDE_QTY port option is defined, the system reports the configured value as the QtyAvailable text element value for all items in the outbound 846 message.
    • When the OVERRIDE_QTY port option is not defined, the system continues to use the existing 846 availability logic to determine the QtyAvailable text element value based on inventory, order promising, and BOM calculations.
  • You can control duplicate purchase order validation during inbound Aptean EDI 850 message processing by using the IGNORE_POCHECK port option.
    • When the IGNORE_POCHECK port option is set to Yes, the system skips duplicate purchase order validation against posted sales invoices while continuing to validate against open sales orders.
    • When the IGNORE_POCHECK port option is set to No, the system validates duplicate purchase orders against both open sales orders and posted sales invoices, maintaining the existing behavior.

  • The system supports automatic processing of outbound instruction to dispatch messages for sales and warehouse documents. You can enable this functionality using the Auto Process Sales Order – Outbound Instruction to Dispatch field value on the EDI Setup page. When a valid EDI Port field value is defined, the EDI Pick Ticket toggle on the Sales Order and Sales Orders pages is turned on. When a sales order is released with the toggle turned on, the system generates outbound messages through the Job Queue.

    For warehouse receipts, the system sets the EDI Document field value to True upon release and generates outbound 943 Dispatch Advice messages when auto-processing is enabled.

    This functionality also applies to sales return, purchase, and transfer documents and supports outbound message types 943, 943 Level 3, and 943 Level 4.

UI/UX changes

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

  • The EDI Price Catalogs list page and EDI Price Catalog card page have been added.
  • The Send Reusable Packaging Shipment action has been added to the Posted Sales Shipment page.
  • The EDI Price Catalogs action has been added to the EDI Setup page.
  • The following fields have been added to the General FastTab of the Sales Order page:
    • Cancel Date
    • Season Code
    • Order Type Code
    • Division Code
  • The EDI Transfer Jnl. Templ. BCW field has been added to the EDI FastTab on the Location Card page.
  • The Include in EDI Reusable Packaging Message field has been added to the Item Card page.
  • The Reusable Packaging EDI Port Code field has been added to the Location Card page.
  • The EDI Reusable Packaging Shipment and EDI Reusable Packaging Entry No. fields have been added to the Posted Sales Shipment page.
  • The Department and Promo/Deal Number fields have been added to the EDI Document page.
  • The following fields have been added to the EDI Price Catalog page:
    • Reference Type
    • Season Code
    • Division Code
    • Style Color Code
    • Style Size Code
    • Style Dimension Code
    • Style Code
  • The Auto Process Sales Order – Outbound Instruction to Dispatch field has been added to the EDI Setup page.
  • The EDI Reusable Packaging Shipment toggle has been added to the Sales Order page.
  • The EDI Pick Ticket toggle has been added to the Sales Order and Sales Order List pages.
  • The Aptean EDI 855 Purchase Order XML port has been added.
  • The CALC_ASSEMBLY and OVERRIDE_QTY port options have been added to the Aptean EDI 846 port.
  • The IGNORE_POCHECK port option has been added to the Aptean EDI 850 port.
  • The PO_INSERT_LINE_DISCOUNT and PO_INSERT_LINE_CHARGE port options have been added to the Aptean EDI 855 Purchase Order Inbound port.
  • The VENDOR_DUNS port option has been added to the Aptean EDI 856 Reusable Packaging outbound port.

Resolved issues

The following issues have been resolved in this release.

IDDescription
357672The system fails to update the Order Type Code field value on the Sales Order page when processing inbound Aptean EDI 850 messages, resulting in incorrect or blank values.
354647The system fails to retain item matching information when the Aptean Apparel Bridge extension is not installed. It also incorrectly validates catalogs without filters, ignores the configured pricing hierarchy, and does not support barcode-based item references during catalog processing.