What's new in version 2514.0.0.0
Features
With the features added in this release of the Aptean EDI extension,
-
The system maps the InvoiceType text element based on the value of the EDI Price Correction toggle on the Sales Credit Memo page.
- If the toggle is turned on, the InvoiceType text element is set to Corrected Invoice. Additionally, the system sends the credit document with the assigned item from the related item charge assignment in the ID section.
- If the toggle is turned off, the InvoiceType text element is set to Credit Note.
-
The system updates the DocumentRelease text element based on the value selected in the EDIFACT_RELEASE port option when processing the INVOIC D01B Sales Credit Memo Outbound and INVOIC D01B Sales Invoice Outbound messages.
The available options are D96a and D01b, with D96a set as the default.
- If D96a is selected, the DocumentRelease text element is updated with 96a.
- If D01b is selected, the DocumentRelease text element is updated with 01b.
-
You can configure the system to generate a message after the sales order is released by using the AUTO_ORDRSP port option in the ORDRSP D01B Outbound port.
- If no changes are made to the related sales order, the system updates the ORDRSPFunctionCode text element as Accepted Without Amendment.
- If any of the following changes are made, the system updates the ORDRSPFunctionCode text element as Accepted With Amendment.
- The Quantity field value
- The Requested Delivery Date field value
- The Sell-to Customer No. field value
- Addition or deletion of a sales line
-
The system updates the WarehouseLot2 and WarehouseProductionDate text elements when processing the Aptean EDI 846 message, based on the integration with Aptean JustFood or the Aptean Lot Management extension:
- When Aptean JustFood is installed:
- The WarehouseLot2 text element inherits the value from the Alternate Lot No. field value on the Lot No. Information List page.
- The WarehouseProductionDate text element is updated with the Production Date field value on the Item Ledger Entries page.
- When the Aptean Lot Management extension is installed:
- The WarehouseLot2 text element inherits the value from the Vendor Lot No. field (visible only when the Aptean Lot Management extension is installed) value on the Lot No. Information List page.
- The WarehouseProductionDate text element is updated with the Vendor Production Date field value on the Lot No. Information Card page. If the Vendor Production Date field value is left blank, it is updated with the Posting Date field value on the Item Ledger Entries page.
- When Aptean JustFood is installed:
- The system assigns the item charges defined in the Service Allowance Details section to the related item when processing the Aptean EDI 850 or Aptean EDI 860 message.
-
You can define the processing of the Aptean EDI 943, 943 Level 3, and 943 Level 4 messages after updating the warehouse receipt and resending it, and the system updates the OrderStatusCode text element accordingly. The available options are: Original, Replace, and Delete. The system updates the OrderStatusCode text element as follows:
Option selected Value updated Original N Replace R Delete D The default value is N.
-
The system updates the ShipmentDetail and ItemDetail text elements when processing the Aptean EDI 945 and Aptean EDI 945 Sales Order messages:
- ShipmentDetail
- If the FB_USE_PACKAGING port option is set to Yes, the system adds order-bound packaging using the PalletGTIN and QtyOrdered text element values.
- If the FB_CREATE_SSCCS port option is also set to Yes, the system creates an SSCC (Serial Shipping Container Code). Otherwise, it adds an EDI package.
- The system cannot create both an SSCC and an EDI package at the same time.
- ItemDetail
- If the LineNumber text element is blank and the FB_USE_PCKG_LINES port option is set to Yes, the system adds order-bound packaging using the GTIN and ShippedQty text element values.
- If the FB_CREATE_SSCCS port option is also set to Yes, the system inserts an SSCC detail. Otherwise, it adds an EDI package detail.
- The system can perform only one of these actions at a time.
- When processing the Aptean EDI 945 Sales Order message, the system does not support SSCC creation.
Additionally, the Aptean EDI 945 and 945SO ports support item tracking, license plate information, and catch weight, similar to the Aptean EDI 945 Level 4 port.
- ShipmentDetail
-
When the Aptean Beverage Empty Goods and Deposit Management extension, Drink-IT Edition, is installed, the system maps the RateIdentification, CodeTypeOfAllowance, AllowanceAmount, and TaxFree text elements linked to the related line added by empty goods (G/L Account, Item Charge) in the tax details. This applies while processing the Aptean EDI 810 (Invoice), Aptean EDI 812 (Credit Memo), and EMEA ports invoice and credit memo messages. The mapping details of the text elements are as follows:
Text element Mapped value RateIdentification BeverageEmptyGoods (default when the Aptean Beverage Empty Goods and Deposit Management extension, Drink-IT Edition is installed). CodeTypeOfAllowance The Description field value in the associated sales credit memo or sales invoice line. AllowanceAmount The Amount field value in the sales credit memo or sales invoice line. TaxFree True (default when the Aptean Beverage Empty Goods and Deposit Management extension, Drink-IT Edition is installed).
-
The Aptean Beverage Sales Purchase Conditions extension, Drink-IT Edition, already supports validation and mapping of lines of type G/L Account or Charge (Item) that are attached to an item through the Attached to Line No. field in posted sales invoices and credit memos. The system extends this functionality to the Aptean INVOIC D01B Sales Invoice Outbound and INVOIC D01B Sales Credit Memo Outbound messages. The following text elements are added in the EDI messages if the Aptean Beverage Sales Purchase Conditions extension, Drink-IT Edition is installed.
- RateIdentification
- CodeTypeOfAllowance
- AllowanceAmount (always positive)
- TaxFree
If a line does not have a value in the Attached to Line No. field, the corresponding text element is left blank.
The mapping details of the text elements are as follows:
Text element Mapped value RateIdentification Beverage Discounts (default when the Aptean Beverage Sales Purchase Conditions extension, Drink-IT Edition, is installed). CodeTypeOfAllowance The Description field value in the associated sales credit memo or sales invoice line. AllowanceAmount The Amount field value in the sales credit memo or sales invoice line. TaxFree True (default when the Aptean Beverage Sales Purchase Conditions extension, Drink-IT Edition, is installed)
- When the Aptean Beverage Tax Management extension, Drink-IT Edition, is installed, the system maps the TotalTaxAmount text element to the Amount field on the Posted Document Tax Lines page associated with the Posted Sales Invoice or Posted Sales Credit Memo page when processing the INVOICD01B SalesInvExpBCW and INVOICD01B SalesCrMemoExpBCW messages.
- If multiple lines exist on the Posted Document Tax Lines page, the system sums the Amount field values and updates the Taxes/TaxLine/TotalTaxAmount text element for each item in the source document line.
- The RateIdentification text element is updated with Excise.
- The system updates the TotalTaxAmount text element in the Trailer/Taxes section with the sum of all TotalTaxAmount field values.
-
When the Aptean Beverage Tax Management extension, Drink-IT Edition, is installed, the system maps the Type and Text text elements in the Free Text section as follows while processing the INSDES D01b Warehouse Shipment Outbound message.
Text element Mapped value Type Duty declaration (default value) Text The Excise Type field value on the related Ship-to Address page > The Excise Type field value on the related Customer Card page. If both the fields are empty, it is left blank.
-
When the Aptean Beverage Customs Document Management extension, Drink-IT Edition, is installed, the system maps the Type and Number text elements in the Reference section as follows while processing the INSDES D01B Warehouse Shipment Outbound message.
Text element Mapped value Type Declarant’s customs identity number (default value) Text The Tax Registration No. field value on the related Ship-to Address page > The Tax Registration No. field value on the related Customer Card page > The Tax Registration No. field value in the related document tax line. If the fields are empty, it is left blank.
- When Aptean JustFood is installed, the EDI action on the Warehouse Receipt page has been moved from Actions > Print > EDI to Actions > EDI.
-
The system maps the following text elements in the ShipmentDetail section when processing the Aptean EDI 940 messages.
Text element Mapped value TotalWeight The Gross Weight field value on the Item Card page multiplied by the QtyOrdered text element value in the respective ShipmentDetail section. WeightUOM LB (default value) TotalVolume The Unit Volume field value on the Item Card page multiplied by the QtyOrdered text element value in the respective ShipmentDetail section. VolumeUOM CU (default value) Additionally, the system maps the TotalVolume text element to the value obtained by multiplying the Gross Weight and Quantity field values on the related sales order line when processing the Aptean EDI 940 Sales Order message.
- The system updates the shipping details with the Shipping Agent Code and Shipping Agent Service Code field values from the inbound file when a translation value for ShippingService field value is available while processing the Aptean EDI 850 message. This occurs when the ShipviaRoute field value does not have a translation value.
-
The system updates the shipping information in the following hierarchy when processing the outbound messages as follows:
Message type Type of document Mapped field Hierarchy Aptean EDI 940 Sales Order Sales Order ShipmentMethodofPay The EDI translation value of the shipping Method field value > The shipping Method field value on the sales header. Sales Order TransportType The EDI translation value of the shipping Agent field value with the Related Message Field Name field value set as TRANSPORTTYPE > The EDI translation value of the shipping Transport Method field value > M (default value) Aptean EDI 940 and Aptean EDI 940 Inventory Pick Sales Order and Transfer Order ShipmentMethodofPay Same as Aptean EDI 940 Sales Order Sales Order and Transfer Order TransportType Same as Aptean EDI 940 Sales Order Aptean EDI 856, Aptean EDI 856 Consolidated, and Aptean EDI 856 Level 4 Sales Shipment TransportMethod The EDI translation value of the shipping Agent field value with the Related Message Field Name field value set as TRANSPORTTYPE > The EDI translation value of the shipping Transport Method field value > M (default value) Aptean EDI 810 Sales Invoice FOBCode The InformationRecord/ShipMethodOfPay field value in the 850 inbound message> The EDI translation value of the shipping Method field value> The shipping Method field value on the invoice header. Sales Invoice TransportMethodCode The EDI translation value of the shipping Agent field value with the Related Message Field Name field value set as TRANSPORTTYPE > The EDI translation value of the shipping Transport Method field value > M (default value)
Enhancements/Modifications
With this release of the Aptean EDI extension,
- The USE_NAV_BILLTO port option defines how bill-to customer details are updated. When set to Yes, the system updates the sales header bill-to section with the bill-to customer details from the Customer Card page, and no confirmation message appears. When set to No, the bill-to details are updated from the inbound file, and the bill-to customer is set from the associated customer card. This enhancement addresses the issue reported in bug ID #320376.
-
The system maps the QtyOrdered text element to the Qty. to Ship field value in the warehouse shipment line when processing the Aptean EDI 940 and Aptean EDI 940 Sales Order messages. If the Qty. to Ship field value is blank, the system inherits the value from the Outstanding Quantity field.
If multiple warehouse shipment lines exist, the TotalQtyToBeShipped text element is updated with the sum of the QtyOrdered text element values.
-
The system updates the HeaderAllowances and TrailerAllowances sections when the item type is G/L Account or Charge (Item) based on the discounts (with or without) as follows while processing the INVOIC D01B Sales Credit Memo Outbound message. Additionally, the mapping of manually added item charges for DetailAllowances has been updated. The assignment is taken from the value entries of the posted document.
- Item with single G/L Account: Updates the HeaderAllowances and TrailerAllowances sections in the invoice and credit memo.
- Item with single Charge (Item): Updates the HeaderAllowances and TrailerAllowances sections in the invoice and credit memo.
- Item with multiple G/L Account: Updates multiple HeaderAllowances sections and sums them to update the TrailerAllowances section.
- Item with multiple Charge (Item): Updates multiple HeaderAllowances sections and sums them to update the TrailerAllowances section.
- Multiple Items with G/L Account and Charge (Item): Updates multiple HeaderAllowances based on the number of G/L Account and sums them to update a DetailsAllowances section for all available Charge (Item). The system also updates the TrailerAllowances section separately for both G/L Account and Charge (Item) types.
This enhancement addresses the issue reported in bug ID #320512.
UI/UX changes
The following UI/UX changes have been made in this release.
-
The ORDRSP D01B Outbound port has been added.
-
The EDIFACT_RELEASE port option has been added to the INVOIC D01B Sales Credit Memo Outbound and INVOIC D01B Sales Invoice Outbound ports.
-
The EDI action on the Warehouse Receipt page has been moved from Actions > Print > EDI to Actions > EDI.
This change is already available in the Aptean EDI extension and applies when Aptean JustFood is installed. -
The confirmation message has been removed when processing the Aptean EDI 850 message with the USE_NAV_BILLTO port option set to Yes.
Resolved issues
The following issues have been resolved in this release.
ID | Description |
---|---|
318863 | An error occurs on the EDI Messages page when processing the Aptean EDI 810 message that has multiple NoteRecord text elements associated with it. |
320376 | The system incorrectly updates the bill-to customer details on the Sales Order page from the inbound file instead of using the details from the Customer Card page. This occurs even when No is selected in the confirmation message while processing the Aptean EDI 850 message with the USE_NAV_BILLTO port option set to Yes. |
318870 | The system fails to calculate the Shipment Date field value in the sales header based on the value from the inbound file even though the Requested Delivery Date field value is defined when processing the Aptean EDI 850 message. |
318256 | The system incorrectly calculates the Shipment Date field value on the Sales Order page based on the value from the inbound file even though the Requested Delivery Date field value is defined in the sales header when processing the Aptean EDI 850 message. |
323232 | The system incorrectly displays an error message when processing the Aptean EDI 850, 860, or ORDERS D96A SalesOrderImp message if the GLN-related text elements for the customer or ultimate consignee exceed 13 characters. However, the system should ignore the GLN when its length is greater than 13 characters. |
323897 | The system fails to update the Description field in the sales order line from the associated description field of the item charge when processing the Aptean EDI 850 and Aptean EDI 860 messages. |
326198 | The system incorrectly displays an error on the Posted Sales Shipment page when the Ship-to Code field value is left blank on the Shipping FastTab while sending the shipment through Aptean EDI 856 Consolidated port. |
323246 | The system fails to apply the correct EDI translation value for units of measure while processing the Aptean EDI 940 message, using only the first translation value instead of the value that matches the associated sales or shipment line. |
324541 | The system fails to update the Unit of Measure Code field value on the Sales Order page from the associated item reference record when processing the ORDERS D96A SalesOrderImp message. |
324397 | The system fails to update the Expiration Date field value on the Item Tracking Lines page for the lot number of an item when processing the RECADV D01B L4 WhseRcptImpBCW message. |
321859 | The system displays an incorrect notification message while processing the inbound messages when the Inbound Post Processing field value is set to Release on the EDI Port Card page. |
320512 | The system fails to update the HeaderAllowances, DetailAllowances, and TrailerAllowances sections for related invoices and credit memos while processing the INVOIC D01B Sales Credit Memo Outbound and INVOIC D01B Sales Invoice Outbound messages. |
326514 | The system incorrectly generates multiple detail segments for an item from the reservation entry table, creating reservation entries even when no item tracking lines are defined while processing the Aptean EDI 940 message in a sales order. This issue occurs when the Order Tracking Policy field value on the Item Card page is set to Tracking. |
322710 | The system fails to process inbound messages in the job queue if a message triggers a popup, such as Document was released, when the Auto Release option is defined on the EDI Port Card page. |