Based on whether your documents agreements direction is Inbound or Outbound will depend on the details and fields presented to you in the next FastTab.

Inbound Message Options

Enabling Auto. Accept will automatically accept the inbound document using the Accept Codeunit No. set against the relevant Inbound Document Type.

There are multiple options for validating the item code within a file, as different partners can send files in different ways.

By default, the new document agreement is set to validate the item codes in the file by the Internal Item No. this refers to the number given to the item in Microsoft Dynamics 365 Business Central. The other options include Common Item No, which looks to the cross reference of the Item which is set to Cross Reference Type = Barcode. If you choose the option Partner Item No. it will again look at the items cross reference setup, but this time look at where Cross Reference Type = Customer.

The next field down is the Apply EDI Unit Price by enabling this you are setting the app up to overwrite the price on the Sales Document with the price in the Inbound file.

Imp Convert to Cross ref UOM if enabled will convert quantity on inbound order to reflect case ordering.  Controlled using the item cross reference record and calculation based on the EDI Qty. Per Sales UOM field found on the Item Cross Reference page of the item.

The final few fields are purely for intercompany use. This will need to be discussed with us here at Technology Management if it is something you are looking to do.

Purchase Acceptance, you can choose to update fields or create a new purchase document for inbound purchase orders.

If you choose to Update Referenced, then you need to adjust the fields below.

  • Update Ref Expected Receipt date: set this to adjust the date when the receipt date in the file is different or validate so that the inbound order fails validation if the dates are different.

  • Update Ref Accept Quantity and Update Ref. Amt/Cost/Disc use the same principle but for their own respective fields on the order.

Outbound Message Options

If your Document Agreement is set to Outbound then the FastTab will show settings relating to outbound message options. Both the heading of the FastTab and the options within it will be different to the Inbound Message Options.

Outbound File Location Code: This field contains a unique code for that customer that corresponds to the Customer Input Location in our EDI system. This code is transmitted in the outbound EDI file, and once processed through the web service retrieves the location from the EDI system and places a copy of the message on the file system for processing.

If Auto. Send is enabled the document will automatically send during posting within Microsoft Dynamics 365 Business Central.

NB: If auto send is disabled you can still send the posted documents out manually, using the Send EDI Document.

By default if you are sending an invoice you send one file at a time this sends the one posted invoice and is received as a single xml and transformed into whatever type of EDI file the partner required to successfully receive it, whereas Batch Process will send multiple invoices in the same message if Group by Supplier ID is enabled will batch outbound documents based on Supplier ID.

If enabled Clever EDI will use the Doc. Agree. Supplier ID on the document agreement (mentioned earlier in the user guide), else use the supplier ID on the incoming document associated if available is used to identify the supplier for the trading partner.

Expt. Convert to Cross Ref UOM is used to convert quantities back on outbound documents when enabled.

The UOM on an EDI message might be converted when the original message comes in, for example if a warehouse uses single picking the UOM could be converted from BOXES on the inbound document to Single items. When the outbound document is then sent out set this flag to convert the UOM to what was there before by checking the inbound document.