What's new in version 2507.0.0.0

Features

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

• The External Shipment No. field value on the EDI Document page is mapped with the ExternalShipmentId text element value while processing through the Aptean EDI 810 message.

• The Amount, TaxedItemAmount, and TaxExemptItemAmount text elements of the Summary section added to the Aptean EDI 810 port are mapped as follows to the following field values in the posted sales invoice.

  Text element in Aptean EDI 810 port	Field in Business Central
  Amount	Total Excl. VAT (GBP)
  TaxedItemAmount	Updated with [Line Amount incl. VAT – Total VAT (GBP)] only if VAT % is greater than 0.
  TaxExemptItemAmount	Updated with Line Amount incl. VAT only if VAT% is equal to 0.

  Similarly, the Amount, NetAmount, ItemAmount, TaxedItemAmount, and TaxExemptItemAmount text elements of the Summary section added to the Aptean EDI 812 and Aptean EDI 812 OUT ports are mapped as follows to the following field values in the credit memo and posted credit memo.

  Text element in Aptean EDI 812/812 OUT ports	Field in Business Central
  Amount	Total Excl. VAT (GBP)
  NetAmount	Total Incl. VAT (GBP)
  ItemAmount	Total Excl. VAT (GBP)
  TaxedItemAmount	Updated with [Line Amount incl. VAT – Total VAT (GBP)] only if VAT % is greater than 0.
  TaxExemptItemAmount	Updated with Line Amount incl. VAT only if VAT% is equal to 0.

  
  The item on the sales line is tax-exempt when the Tax Category field value on the associated VAT Posting Setup page and the Tax Exempt Tax Category field value on the EDI Setup page match.

• When you process the Aptean EDI 812 message, the GTIN text element is mapped with the GTIN field value on the related Item Card page.

• When you process the Aptean EDI 812 OUT and Aptean 812 OUT Posted Cr Memo message,

  • The system adds a line to the Order Bound Packaging page if the Aptean Packaging extension is installed and the Quantity text element in the inbound file has a value. This is applicable only when the associated item is a packaging item.
  • The system adds a line to the Document Weight Lines page if the Aptean Catch Weight extension is installed and the CatchWeightQuantity text element in the inbound file has a value. This is applicable only when the associated item is a catch weight item.

• The system auto processes the sales shipment through job queue when the Disable Sales Shipment toggle on the associated Location Card page is turned off. This automatically turns on the EDI Shipment toggle on the related non-empty sales shipments when created if a related EDI port is configured. If the Disable Sales Shipment toggle is turned on, the EDI Shipment toggle is automatically turned off and the sales shipment is not auto processed.

• The system displays a confirmation message when you delete a warehouse shipment after executing the Send Pick action and the Aptean EDI 940 message is generated. If you select Yes, the warehouse shipment is deleted.

• The system directly maps the reference order number to the PurchaseOrderNumber text element while processing the Aptean EDI 944 and Aptean EDI 944 Level 4 messages instead of using the ShipmentIDNumber and DepositorOrder field values in the .xml inbound file. Similarly, the system displays the reference order number in the PurchaseOrderNumber text element, and the Shipment and DepositorOrderNumber text elements are mapped with the warehouse receipt number while processing the Aptean EDI 943, Aptean EDI 943 Level 3, and Aptean EDI Level 4 messages.

• While processing the Aptean EDI OUT 850 message, you can specify whether the message should be sent to the vendor, the Logistics Service Provider (LSP), or both. You can select the appropriate option on the Purchase Order page if the associated location has recipient GLN defined when sending the purchase order to EDI. However, the VendorGLN can be sent regardless of the location recipient GLN.

  • If Logistics Service Provider option is selected, the RecipientGLN and LocationGLN text elements are updated.
  • If Vendor option is selected, the VendorGLN, RecipientGLN, and LocationGLN text elements are updated.
  • If Both option is selected, two messages are generated:
    • The first message is for vendor and the VendorGLN, RecipientGLN, and LocationGLN text element values are updated.
    • The second message is for LSP and the RecipientGLN and LocationGLN text element values are updated.

  • The option selected on the Purchase Order page is updated in the EDI Prompt LSP BCW field. However, if Logistics Service Provider is selected, it remains empty.
  • Additionally, this field is not visible by default and can be displayed through personalization.

• You can define if you want to automatically release or post the inbound document while processing the EDI message by configuring the Release/Post Inbound field value on the EDI Port Card page. Additionally, you can execute the Release/Post action to post the associated document and the system executes the action based on the Status field value configured on the respective EDI Messages page. If the Status field value conflicts with the action executed, you will receive an error message. Similarly, it works for warehouse shipments and warehouse receipts.

  
  This functionality is available only when the Aptean Mobile Warehouse Registration extension is installed.

• You can view the status of the source document in the Source Status field on the All EDI Messages list and EDI Messages card pages. Additionally, you can view this field value on the FactBox of the EDI Messages card page.

• The entries in the Entry No. field on the EDI Messages page are sorted in descending order.

• View up-to-date information of stock levels, product availability, and movement on the EDI Physical Inventory Journals page by processing the Aptean EDI INVRPT message. To know more, see EDI physical inventory journals.

• Calculate the delivery forecasted quantity and view the latest forecasted quantity on the DELFOR Entries Overview page by processing the Aptean EDI DELFOR message. To know more, see Delivery forecasting.

• If the FB_USE_PCKG_LINES port option is set to Yes, the system maps package line values from the DetailRecord section of the inbound .xml file to the order-bound packaging lines linked to warehouse receipts when processing EDI 944 Level 4 messages. Similarly, for EDI 945 Level 4 messages, the system maps package line values from the ItemDetail section of the inbound .xml file to the order-bound packaging lines linked to warehouse shipments.

• While processing the Aptean EDI 945 message, the system updates the Location Code and Bill-to Customer field values on the Sales Invoice page based on the ReceiptGLN and the Location Code field value based on the LocationGLN text element values from inbound file in the following hierarchy:

  1. The Location Code field value is mapped to the LSP Recipient GLN field value on the Location Card page.
  2. The Bill-to Customer field value is mapped to the customer that has the GLN field value > The EDI translation value with the RecipientGLN value > EDI translation.

  
  Additionally, the system updates the Item No. field value on the sales invoice based on the GTIN text element in the following hierarchy:

  1. The GTIN field value on the Item Card page.
  2. The No. field value for the Barcode and Customer type on the Item Reference page.
  3. The EDI translation value for the item on the EDI Translations page.

  
  The EDI packages are not created if the EDIPackages port option is set to No.

• The system updates the Sell-to Customer field value on the Sales Invoice page using the CustomerNumber, VendorNumber, SenderID, ShipToLocation text elements in the following hierarchy:

  1. The EDI translation value.
  2. The GLN field value on the Customer Card page.
  3. The EDI Vendor No. field value.
  4. The GLN field value on the Ship-to Address Card page.

• While processing the Aptean EDI 812 OUT and Aptean EDI 812 OUT Posted Cr Memo messages the DocumentNo, ReferenceNo, AdjustmentReasonCode, BuyersItemNumber, and UPC text elements are mapped as below:

  Text element	EDI 812 OUT	EDI 812 OUT Posted Cr Memo
  DocumentNo	Sales Credit Memo No.	Posted Sales Credit Memo No.
  ReferenceNo	Posted Sales Invoice No.	Posted Sales Invoice No.
  AdjustmentReasonCode	EDI translation value > Item Charge number	EDI translation value > Item Charge number
  BuyersItemNumber	The SKU field value in EDI Posted Document associated with Posted Sales Shipment > Reference number for the customer type on the Item Reference page.	The SKU field value in EDI Posted Document associated with Posted Sales Shipment > Reference number for the customer type on the Item Reference page.
  UPC	The UPC field value in EDI Posted Document associated with Posted Sales Shipment > Reference number for the barcode type on the Item Reference page.	The UPC field value in EDI Posted Document associated with Posted Sales Shipment > Reference number for the barcode type on the Item Reference page.

  The system updates the EDI Return Shipment No. field value on the Sales Credit Memo page when the EDI Price Correction toggle is turned on and the Applies-to Doc No. field on the Item Charge Assignement (Sales) page has value by executing the Get Shipment Lines action.

• The system updates the same value to the RecipientGLN and ReceiverID text elements if the EDI Prompt LSP field value is set to Vendor on the Purchase Order page while processing the Aptean EDI 850 PO message. Additionally, the VendorGLN text element is mapped as per the following hierarchy:

  1. The GLN field value on the Vendor Card page.
  2. The EDI translation value for the record which has the Related Message Field name field value as VendorGLN.
  3. The EDI translation value with vendor GLN.
  4. The EDI Customer field value on the Vendor Card page.
  5. The Vendor No. on the Purchase Order card page.

• The system displays the LineSequence text element while processing the Aptean EDI 810, Aptean 812 OUT, and Aptean EDI 812 OUT Posted Cr Memo messages. If multiple lines are available in the source documents, mutiple LineSequence text elements are displayed in sequential order.

• The system displays the TPCode and ShipmentNumber text elements while processing the Aptean 812 OUT and Aptean EDI 812 OUT Posted Cr Memo messages. The mapping of the text elements are as follows:

  • The ShipmentNumber text element is mapped to the EDI Return Shipment No. field value on the associated Sales Credit Memo page.
  • When the TPCODE_TRANS_PRIO port option is set to Yes, the translation value for the bill-to customer in the associated posted sales invoice > The TradingPartnerCode field value in the Aptean EDI 850 port > The GLN field value for the bill-to customer in the associated posted sales invoice > The bill-to customer number in the associated posted sales invoice.
  • When the TPCODE_TRANS_PRIO port option is set to No, the TradingPartnerCode field value in the Aptean EDI 850 port > The translation value for the bill-to customer in the associated posted sales invoice > The GLN field value for the bill-to customer in the associated posted sales invoice > The bill-to customer number in the associated posted sales invoice.

Integrations

The Aptean EDI extension has been integrated with the Aptean Mobile Warehouse Registration extension. For more information, see Integrations.

UI/UX changes

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

• The following pages have been added
  • DELFOR Entries
  • DELFOR Entries Overview
  • EDI Physical Inventory Journals
• The Aptean EDI INVRPT and Aptean EDI DELFOR ports have been added.
• The Release/Post action (Actions > Functions) has been added to the All EDI Messages and EDI Messages card pages.
• The Disable Sales Shipment toggle has been added to the Location Card page.
• The Release/Post Inbound field has been added to the Process FastTab of the EDI Port Card page.
• The Source Status field has been added to the All EDI Messages page, EDI Messages card page, and FactBox of the EDI Messages card page.
• The Entry No. field on the EDI Messages page has been displayed in the descending order.
• The Phys. Inv. Jnl. Template INVRPT field has been added to the EDI FastTab of the Location Card page.
• The following fields have been added to the Demand Forecast Entries page.
  • DELFOR Customer No. BCW
  • Init. Del. Fcst Qty BCW
  • Init. Del. Fcst Qty (Base) BCW
  • EDI Message Entry No. BCW
  • Entry Type BCW