What's new in version 2406.0.0.0

Features

• You can now process EDI messages by filtering EDI ports as per the defined EDI Processing Group field value on the Process EDI By Group report page. You can process the following actions:
  • Inbound Receiving: Create inbound EDI messages from inbound EDI ports and their connection settings to receive files.
  • Inbound Processing: Process inbound EDI messages.
  • Outbound Processing: Create outbound EDI messages from applicable documents.
  • Outbound Sending: Process outbound EDI messages and send files based on the EDI port’s connection settings.

This filter applies to all related actions. If no processing group is set, it will process EDI ports that do not have a processing group. This applies to creating messages as well as receiving and sending files.

• You can process EDI messages for sales return orders and sales credit memos through the Aptean EDI 812 port.

• While processing EDI messages for sales orders through the Aptean EDI 812 Inbound port, if the Unit Cost Price field value is defined in the inbound file, the system uses this value in the Unit Price field for the sales lines of the associated order. If the Unit Cost Price field value is not defined, the system uses the Amount field value in the Unit Price field for the sales lines.

  • For line entries with the Type field set to Item, the system uses UOM conversion for the quantity and the specified unit of measure in the associated item reference document, updating the value in the sales lines.
  • For line entries with the Type field set to G/L Account, if the Qty. field value is defined in the inbound file, the system uses this value in the sales lines of the associated order. If the Qty. field value is not defined, the system assigns a default value of 1.

• You can delete the sales order by setting the value of the TSet Purpose Code field as 01 in the inbound file while processing through the Aptean 860 Inbound port.

• While processing the EDI Message, the Unit of Measure Code field value on the warehouse shipment line gets inherited with the corresponding Dynamic Value field value defined on the EDI Translations page for the UOMofSizeInnerPack field value on the EDI Messages page. If the EDI Value field is not configured for the defined unit of measure code, the system will inherit the value from the source document. This scenario is applicable while processing the EDI messages through the below mentioned ports:

  • Aptean EDI 940
  • Aptean EDI 940 Inventory pick Outbound
  • Aptean EDI 940 SO

• While processing the EDI messages through Aptean EDI 945 and Aptean EDI 945 Inbound port, the Unit of Measure Code field value on the warehouse shipment line gets inherited with the corresponding EDI Value field value defined on the EDI Translations page for the UOM_warehouse field value on the EDI Messages page. If the defined unit of measure is not registered on the Unit of Measures page, the system will inherit the value from the source document.

• You can update the price and quantity fields simultaneously on the existing sales line by setting the LineItemChangeCode field value to PQ in the inbound file while processing through the Aptean 860 Inbound port. Similarly, to replace the existing line, the field is set to RZ.

• You can assign select EDI message fields with respect to the Dynamics Value, with different Related Message Field Name field value on the EDI Translations page. The system will cross-check the combination of the EDI value, dynamics value, and related message field name before processing the EDI messages.

• You can process the Aptean 860 EDI messages if the AssignedIdentification field value is not defined in the inbound file. The system attempts to find a matching line number based on the item number. It finds the item number using the values defined in the BuyersCatalog, Filler2, Filler3, and VendorsCatalog fields of the inbound file.

• EDI messages are created regardless of format errors when receiving files by executing one of the receive actions on the EDI Port Card page or when received during scheduled EDI jobs.

• A notification message is received when the License Status field on the EDI Setup page has an Inactive or Expired value, and any send or receive action is executed through the ports.

Enhancements/Modifications

• While processing the EDI messages, the system will map GTIN field value defined on the Item FastTab of the Item Card page, if for that defined inbound document the UPC Number, SKU, and Style field values aren’t configured on the EDI Translations and Item Reference Entries page. This scenario is applicable while processing the EDI messages through the below mentioned ports:
  • Aptean EDI 810 Purchase
  • Aptean EDI 850
  • Aptean EDI 856 Purchase
  • Aptean EDI 947
• While processing the EDI messages through the Aptean EDI 945 port, if the CaseLot field value is defined in the inbound file, the system inherits the value in the Lot No. field on the Item Tracking Lines page of the associated sales order. If CaseLot field value is not defined in the inbound file, the system does not modify the existing item tracking lines.
• While processing the EDI messages for sales order via the Aptean EDI 940, Aptean EDI 940 Inventory Pick, and Aptean EDI 940 SO ports, the system displays the TotalWeight field value on the EDI Messages page.
  The TotalWeight field value is calculated as the product of WarehouseOrderLine.Quantity and WarehouseOrderLine.Gross Weight field values.

Integrations

Modifications were made to this extension to accommodate integration of the Aptean EDI extension with the Aptean Serial Shipping Container Code extension via the Aptean Integration Layer extension, while deprecating the functionalities of the Bridge app.

UI/UX changes

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

• The following ports have been added to Aptean EDI:
  • Aptean EDI 210 Inbound
  • Aptean EDI 214 Inbound
• The Process EDI By Group report page is added to the Aptean EDI extension.
• The EDI Translations list page is added to the Aptean EDI extension.
• The Send Credit/debit adjustment action is added to the Sales Credit Memo and Sales Return Order pages.
• The EDI Translation action is added to the following card and list pages:
  • Customer
  • Vendor
  • Item
  • Ship-to
  • EDI Port
• The Related Message Field Name field is added to the EDI Translations page.
• The following fields are added to the Totals group of the Aptean EDI 940 and Aptean EDI 940 Inventory pick ports.
  • TotalWeight
  • WeightUOM
  • Volume
  • VolumeUOM
• The Dispatch Groups page is renamed to Processing Groups.

Resolved issues

The following issues have been resolved in this release.