What's new in version 2513.0.0.0

Features

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

• The system updates the Vendor field value in the inbound file using the existing priority order. However, a change has been made in the hierarchy as the system uses the GLN field value on the associated Order Address page instead of the Code field value.

  The updated priority is as follows:

  1. The EDI translation value for the selected vendor.
  2. The EDI Customer No. field value on the associated Vendor page.
  3. The GLN field value on the associated Order Address page.
  4. The Code field value on the associated Vendor page.

  Additionally, the input XSD file associated with the Aptean EDI 810 Purch port has been removed. The schema has been validated to prevent mismatches. The fields that were missing in the inbound port have been added based on the 810 outbound structure and left unmapped.

• The system allows you to delete data from the EDI message header and EDI log entry tables, as their table IDs have been added to the standard Retention Policy page.

• The system does not change any values in the sales order line when processing the Aptean EDI 860 message if the LineItemChangeCode field in the inbound file is set to NC or to any value other than the valid codes defined for this field.

• The system updates the Agent Service Code field value on the associated pages with the translation value of shipping agent services on the EDI Translations page when processing the following messages:

  • Aptean EDI 810
  • Aptean EDI 850
  • Aptean EDI 856 Consolidated
  • Aptean EDI 856 Level 4
  • Aptean EDI 856
  • Aptean EDI 940
  • Aptean EDI 940 Sales Order
  • Aptean EDI 940 Inventory Pick

  If the translation values are not available, then the system updates the system value as per the standard process.

• The system supports nested EDI packages by skipping the carton level packages, the Packaging Item No. field value is updated for the associated EDI package, and the packaging information is updated in the Packaging section when processing the Aptean EDI 856 Consolidated message.

• The system displays the lot details when there are multiple item tracking lines defined for a line in all Aptean EDI 940 messages.

• The system updates the ReceiverID, StoreNumber, and BuyerID text elements when processing the Aptean EDI 826 message based on the following hierarchy:

  ReceiverID

  • If the TPCODE_TRANS_PRIO port option is set to Yes:
    • The translation value of the bill-to customer on the Sales Invoice page (order created via 850 message).
    • The TradingPartnerCode field value in the 850 inbound file (order created via 850 message).
    • The GLN field value of the associated bill-to customer on the Sales Invoice page (order created manually).
    • The bill-to customer field value on the Sales Invoice page (order created manually).
  • If the TPCODE_TRANS_PRIO port option is set to No:
    • The TradingPartnerCode field value in the 850 inbound file (order created via 850 message).
    • The translation value of the bill-to customer on the Sales Invoice page (order created via 850 message).
    • The GLN field value of the associated bill-to customer on the Sales Invoice page (order created manually).
    • The bill-to customer field value on the Sales Invoice page (order created manually).

  StoreNumber

  • If the order is created through the 850 message, the StoreNumber field value from the 850 inbound file.
  • If the order is created manually:
    • The translation value of the ship-to code of the associated sell-to customer on the Sales Invoice page.
    • The Ship-to Code field value on the Sales Invoice page.

  BuyerID

  • If the order is created through the 850 message, the BuyerLocation field value from the 850 inbound file.
  • If the order is created manually:
    • The GLN field value of the associated sell-to customer on the Sales Invoice page.
    • The translation value of the associated sell-to customer on the Sales Invoice page.
    • The sell-to customer field value on the Sales Invoice page.

• The system links allowance codes to the corresponding sales order lines through the EDI Document page. Additionally, the system allows you to identify multiple allowance codes with the same EDI translation and export the correct value in the Aptean EDI 810 messages.

• When Aptean JustFood is installed, the system supports the creation of packages for shipping containers when processing through the Aptean EDI 943 Level 3 messages.

• You can define log connection details on the EDI Log page. To know more, see View connection log.

• When the Aptean EDI Bridge extension is installed, the Over Under Delivery FastTab has been deprecated from the EDI Bridge Food and Beverage page and added to the EDI Setup page.

• The system displays the text elements in the WarehouseRecord section for each lot associated with an item along with the DetailRecord section, including the WarehouseLotNumber and WarehouseExpirationDate text elements, when processing the Aptean EDI 846 message with the INCLUDE_LOT port option set to Yes. Additionally, the QtyAvailable text element in the DetailRecord section displays the sum of the WarehouseQty text element values available for each lot when there are multiple lots associated with an item.

• The system supports item charges associated with items in sales order lines when processing the Aptean EDI 850, 860, and 810 messages.

  • Aptean EDI 850 and Aptean EDI 860 messages – The system displays the Charge (Item) line on the Sales Order page when the following conditions are met:
    • The INSERT_LINE_CHARGE and SAD_ALLOWANCE port options are set to Yes.
    • The text elements in the ServiceAllowanceChargeDetail section are defined.
    • The translation value for the item charge is available.
  • Aptean EDI 810 message – The system updates the text elements on the All EDI Messages page based on the associated values from the inbound file.

• The system uses the Post & Invoice option in the Inbound Post Processing field on the EDI Port Card page to post and invoice the orders and the Post option to only post the shipment documents. This functionality is applicable only for all the inbound ports.

Enhancements/Modifications

With this release of the Aptean EDI extension, the system:

• Allows you to process the ORDERS D96A SalesOrderImp message even when the DetailReference section is not available. This enhancement addresses the issue reported in bug ID #314105.

• Displays an error when posting a sales order with the Location field value as blank only if the Type field value is set to Item. This enhancement addresses the issue reported in bug ID #317951.

UI/UX changes

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

• The View Connection Data action has been added to the EDI Log page.
• The Applicable Document Line No. field has been added to the EDI Document Amounts page.
• The Enable Connection Data Log toggle has been added to the EDI Setup page.
• The Post & Invoice option has been added to the Inbound Post Processing field on the Process FastTab of the EDI Port Card page.
• The TPCODE_TRANS_PRIO port option has been added to the Aptean EDI 826 port.
• The INCLUDE_LOT port option has been added to the Aptean EDI 846 port.
• The Release/Post Inbound field has been renamed to Inbound Post Processing on the Process FastTab of the EDI Port Card page.
• The SenderID text element has been renamed as Receiver ID associated on the All EDI Messages page associated to the Aptean EDI 810 Purch message.
• The Over Under Delivery FastTab has been deprecated from the EDI Bridge Food and Beverage page and added to the EDI Setup page.

  
  This FastTab is visible only when the Aptean EDI Bridge extension is installed.

Resolved issues

The following issues have been resolved in this release.

ID	Description
303826	The system incorrectly includes the item (charge) details along with the main item when processing the Aptean EDI 812 OUT Posted Cr Memo message. This issue occurs when the Aptean Beverage Tax Management extension, Drink-IT Edition, is installed.
305942	The system fails to display all applicable tax lines in the TaxLine and Summary sections when multiple taxes are applied to a document line during processing of the Aptean EDI 812 message. This issue occurs when the Aptean Beverage Tax Management extension, Drink-IT Edition, is installed.
312821	The system incorrectly updates the text elements in the PartnerQualifier section with the associated field values from the Customer Card page instead of the related field values from the Ultimate Consignee FastTab on the Posted Sales Credit Memo and Posted Sales Invoice pages when the Aptean Ultimate Consignee extension is installed and the INVOIC D01B Sales Credit Memo Outbound and INVOIC D01B Sales Invoice Outbound messages are processed.
314105	The system incorrectly displays an error when the DocumentLineIdentifier field value is blank in the DetailReference section when processing the ORDERS D96A SalesOrderImp message.
317951	An error occurs on the Sales Order page when posting an order with the Location field value as blank and the Type field value set to G/L Account.
318867	The system fails to update the Item Reference No. field value in sales order lines with the customer’s item reference number when a matching item reference exists in the setup. This issue occurs when a sales order is created through the Aptean EDI ports.
318861	The system incorrectly updates the Expiration Date field when processing the Aptean EDI 940 message for lines without item tracking. This issue occurs if the associated item is set up with order tracking.
316982	The system incorrectly updates the QuantityShipped text element with a negative value, sets the ExpiryDate text element to blank even though the lot is available, and creates multiple item loops when processing the Aptean EDI 943 message. This issue occurs when the related item is configured with the Order Tracking Policy field value set to Tracking or Tracking & Action Msg.
319827	An error occurs when you generate or process the Aptean EDI 810 or Aptean EDI 812 message from a sales invoice or credit memo in BC versions 20 or earlier, even if the required setups and extensions are available.