What's new in version 2506.0.0.0

Features

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

• While processing the Aptean EDI 943 OUT, Aptean EDI 943 Level 3, and Aptean EDI 943 Level 4 messages, the fields are mapped as follows:

  Text element in Aptean EDI 943 ports	Field name in Business Central
  ShipFromName	Buy-from Vendor Name (Purchase Order) Transfer-from Name (Transfer Order)
  ShipToName	Ship-to Name (Purchase Order) Transfer-to Name (Transfer Order)
  VendorName	Buy-from Vendor Name (Purchase Order) > Name (Company Information)

• When a sales order is created via the Aptean EDI 850 and 860 (when the LineItemChangeCode text element is set to AI) ports and processed through the Aptean EDI 855 message, the LineNumber text element in the 855 inbound file is mapped to the related EDI Ref. Line No. field value in the associated sales order line. If this field value is blank, it is mapped to the Line No. field value in the sales order line.

• The system automatically generates SSCC lines when the FB_CREATE_SSCCS port option is set to Yes, based on the configuration, if Aptean EDI is integrated with the Aptean SSCC extension via the Aptean EDI Bridge extension, and this occurs when the Aptean EDI 945 Level 4 message is processed.

• The system updates the Type field value to Item in the document lines if any of the UPC, Vendor Item Number, or Buyer Item Number fields associated with the Aptean EDI 812 message contain a value; otherwise, it updates the field value to G/L Account. This applies for sales return order, sales invoice, and sales credit memo. This enhancement addresses the issue reported in bug ID #217862.

• If the PACK_TARE_INDIC port option is set for Aptean EDI 856 Consolidated and Aptean EDI 856 Level 4 ports, the PackTareIndicator text element is mapped to the value assigned in the PACK_TARE_INDIC port option description.

  • If this field is blank, it is automatically updated with P as the default value.
  • Additionally, for Aptean EDI 856 Level 4, the PackTareIndicator field value is set to P for pack-level records and T for carton-level records, as this port supports both pack and carton levels.

• When you send the Aptean EDI 855 Out message, the ShipmentMethodCode text element is mapped to the translation value for the related shipment method code on the EDI Translations page. If this is blank, then it is mapped to the Shipment Method Code field value on the associated Sales Order page.

• The package related fields on the EDI Package page are updated in two ways, manually or through inbound document as follows:

  Field name in EDI package page	Updated from
  EDI Package Type	The Default Package Type field value on the EDI Setup page
  Carton Type	Self contained
  Carton Type Code	The Default Package Carton Type Code field value on the EDI Setup page
  Pkg. Data Source	Manual, if the package is created manually or 945, if it is created through inbound document

  Additionally, when processing the associated message through Aptean EDI 856 port, the PalletTypeCode text element is updated with Default Package Carton Type Code field value on the EDI Setup page. This functionality is applicable when the Aptean Packaging extension is installed.

• When integrated with the Aptean Pack and Ship extension, the package related fields on the EDI Package page are updated as below:

  Field name in EDI package page	Updated from
  EDI Package Type	The Carrier Package Type field value on the Package card page
  Carton Type	Self contained
  Carton Type Code	The Carton Type Code field value on the Package card page
  Pkg. Data Source	Manual, if the package is created manually or 945, if it is created through inbound document

  Additionally, when processing the associated message through the Aptean EDI 856 port, the PalletTypeCode text element is mapped as follows:

  • The translation value for the Carton Type field on the EDI Translations page.
  • The Carton Type Code field value on the associated EDI Packages page.

• When integrated with the Aptean bcFood extension through bcFood bridge app, the package related fields on the EDI Package page are updated as below:

  Field name in EDI package page	Updated from
  EDI Package Type	The Default Package Type field value on the EDI Setup page
  Carton Type	Self contained
  Carton Type Code	The Default Package Carton Type Code field value on the EDI Setup page
  Pkg. Data Source	Manual, if the package is created manually or 945, if it is created through inbound document

  This works similarly when integrated with the Aptean LinkFresh extension through LinkFresh bridge app.

UI/UX changes

The Default Package Carton Type Code field has been added to the Packaging FastTab of the EDI Setup page.

Resolved issues

The following issues have been resolved in this release.