What's new in version 2511.0.0.0
Features
With the features added in this release of the Aptean EDI extension,
- The system supports importing inbound files for warehouse receipts generated from sales return orders while processing the Aptean EDI 944 or Aptean EDI 944 Level 4 message.
-
The system maps the ProductionDate text element when processing the Aptean EDI 944 and Aptean EDI 944 Level messages as follows:
- If the Aptean Lot Management extension is installed,
The system maps the value to the Vendor Production Date field on the item tracking lines of the Warehouse Receipt page linked to the purchase order. This value is inherited from the Production Date field on the Lot Origin FastTab of the related Lot No. Information Card page. - If the Aptean JustFood and the Aptean Lot Management extension are not installed,
The system maps the value to the Production Date field on the item tracking lines of the Warehouse Receipt page linked to the purchase order. This value is inherited from the associated field value on the related Item Ledger Entries page.
- If the Aptean Lot Management extension is installed,
-
The system validates the RecipientGLN and LocationGLN text elements when processing the following messages. The values in the inbound file must match the corresponding fields on the Location Card page:
- Aptean EDI 945 Level 4
- Aptean EDI 945 SO
- Aptean EDI 945
- Aptean EDI 944 Level 4
- Aptean EDI 944
Additionally, the system validates the CustomerGLN and VendorGLN text elements as follows:
- For warehouse shipment-related messages:
The system checks if the customer GLN value in the inbound file matches the value on the Customer Card page. - For warehouse receipt-related messages:
The system checks if the vendor GLN value in the inbound file matches the translation value on the EDI Translations page.
If any of these values do not match, the system displays an error.
- The system calculates the FreightAmount text element using the related posted sales invoice document for G/L and item charge lines when processing the Aptean EDI 856 Consolidated and Aptean EDI 856 Level 4 messages. This change ensures that freight charges not included in the warehouse shipment are included from the invoice.
-
When the Aptean Beverage Sales Purchase Conditions extension, Drink-IT Edition, is installed:
-
The system validates posted sales invoice lines of type G/L Account or Charge (Item) that are linked to an item through the Attached to Line No. field when executing the Send Invoice action on the Posted Sales Invoice page. Lines with a value in this field are displayed on the associated Posted Document Lines page.
The system maps the AllowanceCode, AllowanceCode1, and AllowanceCode2 text elements to the translation value of the No. field. If no translation is found, it maps the No. field value from the posted sales invoice line. Only the first three lines on the posted sales lines associated to the item are considered. If any of these lines doesn’t have a value in the Attached to Line No. field, the corresponding AllowanceCode text element is left blank. Similarly, the AllowanceAmount, AllowanceAmount1, and AllowanceAmount2 text elements are updated with the amount field values from the posted sales invoice lines for which the Attached to Line No. field value is available. This is always a positive value. -
The system validates posted sales credit memo or sales credit memo lines of type G/L Account or Charge (Item) that are linked to an item through the Attached to Line No. field when executing the Send Posted Credit Memo or Send credit/debit adjustment action on the Posted Sales Credit Memo or Sales Credit Memo page, respectively. Lines with a value in this field are displayed on the associated Posted Document Lines or Document Lines page.
The system maps the service allowance charge detail (SAD) text elements to the translation value of the No. field. If no translation is found, it maps the No. field value from the posted sales credit memo or sales credit memo line. If any of these lines didn’t have a value in the Attached to Line No. field, the corresponding SAD text element is left blank.The mapping details of the SAD text elements are as follows:
Text element Mapped value SAD01 D (Default when SPC is installed) SAD02 Translation value of charge item or G/L Account in the sales credit memo line (Posted Sales Credit Memo) or sales line (Sales Credit Memo) SAD05 The Amount field value in the sales credit memo line (Posted Sales Credit Memo) or sales line (Sales Credit Memo) SAD13 The amount or quantity value in the sales credit memo line (Posted Sales Credit Memo) or sales line (Sales Credit Memo) SAD15 The Description field value in the sales credit memo line (Posted Sales Credit Memo) or sales line (Sales Credit Memo)
-
-
When the Aptean Beverage Tax Management extension, Drink-IT Edition, is installed, the system maps the TaxAmount2 text element to the Amount field value on the Posted Document Tax Lines page associated with the Posted Sales Invoice or Posted Sales Credit Memo page when processing the Aptean EDI 810 or Aptean EDI 812 message, respectively.
- For EDI 810 messages:
If there are multiple lines on the Posted Document Tax Lines page, the system sums the Amount field values and updates the TaxAmount2 text element for each item in the source document line. The TaxD2 text element is updated with Excise. Additionally, the system updates the TaxAmount4 text element with the sum of all TaxAmount2 field values. - For EDI 812 messages:
The system calculates excise taxes and includes them both in the Tax Lines section and the Tax Summary section of the message when the TaxD2 text element is set to Excise.
- For EDI 810 messages:
-
The TaxClassification, TaxClassificationType, and TaxID text elements are mapped as follows while processing the Aptean EDI 940 SO message:
- The TaxClassification text element is mapped in the following hierarchy:
- The translation value of the Default Tax Classification field value on the Ship-to Address page linked to the sales order.
- The Default Tax Classification field value on the Ship-to Address page linked to the sales order.
- The translation value of the Default Tax Classification field value on the Customer Card page.
- The Default Tax Classification field value on the Customer Card page.
- The TaxClassificationType text element is mapped in the following hierarchy:
- The translation value of the Excise Type field value on the General Tax Classifications page linked to the Ship-to Address page
- The Excise Type field value on the General Tax Classifications page linked to the Ship-to Address page
This happens only when the Aptean Beverage Tax Management extension, Drink-IT Edition, is installed.-
The TaxID text element is mapped to the Tax Registration No. field value on the Document Tax Lines page linked to the sales order line.
This happens only when the Aptean Beverage Customs Document Management extension, Drink-IT Edition, is installed. - The TaxClassification text element is mapped in the following hierarchy:
-
The TaxClassification, TaxClassificationType, and TaxID text elements are mapped as follows while processing the Aptean EDI 940 message:
- When the shipment type is associated with sales, the system follows the mapping logic same as the Aptean EDI 940 SO message.
- When the shipment type is associated with a purchase return order:
- The TaxClassification text element is mapped in the following hierarchy:
- The translation value of the Default Tax Classification field value on the Order Address page linked to the purchase order
- The Default Tax Classification field value on the Order Address page linked to the purchase order
- The translation value of the Default Tax Classification field value on the Vendor Card page
- The Default Tax Classification field value on the Vendor Card page
- The TaxClassificationType text element is mapped in the following hierarchy:
-
The translation value of the Excise Type field value on the General Tax Classifications page linked to the Order Address page
-
The Excise Type field value on the General Tax Classifications page linked to the Order Address page
-
- The TaxClassification text element is mapped in the following hierarchy:
This happens only when the Aptean Beverage Tax Management extension, Drink-IT Edition, is installed. -
The TaxClassification and TaxClassificationType text elements are added to the Aptean EDI 940 Inv. Pick message and the text elements are not mapped.
-
When the Aptean Beverage Empty Goods and Deposit Management extension, Drink-IT Edition, is installed, the system maps the service allowance charge details (SAD) text elements linked to the G/L Account type lines of the empty goods items as follows while processing the Aptean EDI 810 and Aptean EDI 812 messages.
Text element Mapped value SAD01 E (When Aptean Beverage Empty Goods and Deposit Management extension is installed) SAD02 Translation value of charge item or G/L Account in the sales credit memo line (Posted Sales Credit Memo) or sales line (Sales Credit Memo)
- When the Aptean Beverage Advanced Warehouse Management extension, Drink-IT Edition, is installed, the system automatically creates EDI packages when you post sales orders. Additionally, the package-related information on the EDI Package page is inherited from the corresponding values on the License Plate Reservation Entry page. The license plate defines the pallet level of the EDI package, and the items are grouped within that pallet level.
Enhancements/Modifications
With this release of the Aptean EDI extension,
- The system updates the price values as 0 for packaging items included in the Service Allowance Charge (SAC) details while processing the Aptean EDI 810 message. This enhancement addresses the issue reported in bug ID #297553.
- The system automates the generation of Aptean EDI 204 message based on the value of the EDI Carrier Load toggle along with the other configurations on the EDI Port and EDI Setup pages. Additionally, the sent date and time are updated in the EDI Carrier Sent Date/Time field. This enhancement addresses the issue reported in bug ID #275816.
- The OnBeforeProcessKitSerialLot integration event has been added to the SPSCommerce810PortEventBCW codeunit to enhance customization.
Integrations
The Aptean EDI extension has been integrated with the following extensions:
- Aptean Beverage Tax Management, Drink-IT Edition
- Aptean Beverage Empty Goods and Deposit Management, Drink-IT Edition
- Aptean Beverage Sales Purchase Conditions, Drink-IT Edition
- Aptean Beverage Customs Document Management, Drink-IT Edition
To know more, see Integrations.
UI/UX changes
The EDI Carrier Load toggle and EDI Carrier Sent Date/Time field have been added to the EDI FastTab of the Warehouse Shipment page.
Resolved issues
The following issues have been resolved in this release.
ID | Description |
---|---|
297553 | The system incorrectly includes the prices of packaging items that are already specified in the Service Allowance Charge (SAC) details when processing the Aptean EDI 810 message. |
297273 | The system incorrectly displays an error message when processing the Aptean EDI 810 message if the Invoice Taxes EDI Port Code field value is empty on the associated Customer Card page. |
291136 | The system incorrectly updates the Source No. field value on the EDI Packages page when processing the Aptean EDI 945 Level 4 messages associated with purchase return orders or transfer orders. |
297978 | An error occurs on the Purchase Order page when executing the Release action, even if the Send EDI PO on Release toggle on the EDI Setup page is turned on and the Purch. Order Port Code field is empty on the associated Vendor Card page. |
275816 | The system incorrectly automates the generation of Aptean EDI 204 and Aptean EDI 940 messages based on the value of the EDI Document toggle on the Warehouse Shipment page, even though the two messages serve different functionalities. |