What's new in version 2601.2.0.0

Enhancements/Modifications

With this release of the Aptean Beverage Customs Document Management extension, Drink-IT Edition,

• You can turn on the Full Customer/Vendor Return toggle, and the Return Location and Sales/Purchase Return document fields are visible and editable on the Customs Document page. If the toggle is turned off, the Return Location and Sales/Purchase Return document fields are not visible.

• Goods are returned in EMCS when the consignee refuses delivery, and the shipment is sent back to the original consignor without generating an EMCS notification. You can turn on the Full Customer/Vendor Return toggle and specify the return document in the Sales/Purchase Return document field and then send an IE813 message. The system creates an XML file with a filled NewConsigneeTrader for the consignor and DeliverPlaceTrader for the POD trader ID.

• The system updates the IE818 message generation logic in Business Central to support accurate trader determination in full customer/vendor return scenarios. When the Full Customer/Vendor Return toggle is turned on,

  • The system adjusts how trader information is populated in the IE818 message.
  • The correct consignee, consignor, and delivery place trader details are selected based on return logic.
  • If goods are returned to a different destination, an alternative return location can be used.

  • If the option is not selected, the system continues to use the existing IE818 message logic without any changes.

• The system assigns the Body Record Unique Reference Number field values on customs document lines starting from 1. For a single line, the value is 1 and for multiple lines, the system assigns sequential values (for example, 1, 2, 3). When the system receives the IE801 message, it creates the XML and populates the Body Record Unique Reference Number field value based on the customs document lines.

• You can create customs document for an incoming/outgoing (sales order, purchase order or sales return order). After executing the Process IE815 message action, the BodyRecordUniqueReference element is generated as a unique numeric identifier for each article line. This value is assigned sequentially starting from 1 up to 999, where 1 represents the first article line, 2 represents the second article line, ect.

• The system supports sending and receiving the IE818 message and correctly handles the _BodyRecordUniqueReference_text element value to identify and update customs document lines during processing. The behavior of the system differs depending on the direction of movement (inbound or outbound).

  • The system updates the following fields in the customs document.
    • Date of Analysis
    • Time of Analysis
    • Date of Arrival Excise Goods
    • Global Conclusion of Receipt
    • Complementary Information
  • The system updates the following fields on the customs document line.
    • Indicator Shortage/Excess
    • Observed Quantity Shortage/Excess
    • Refused Quantity
    • Unsatisfactory Reason
    • Complementary Information

  • When an IE818 message is received for inbound transactions:

    • No updates should be made to the customs document lines

    • Only update the EMCS Status field in the customs document header

• The system supports sending the IE871 message and correctly handles the BodyRecordUniqueReference field to identify and update customs document lines during processing.

• The IE813 Change of Destination action on the Customs Document page is now disabled when the document type is not a sales order, as this functionality only applies to sales order documents.

UI/UX changes

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

• The Full Customer/Vendor Return toggle has been added to the Receipt FastTab of the Customs Document page.
• The Return Location & Sales/Purchase Return document fields have been added to the Receipt FastTab of the Customs Document page.
• The BodyRecordUniqueReference field has been added to the customs document line and added to the XML file.