Docs  /  Solution  /  EDI Interface  /  Tasks

 Working with the App

2026/09/25 • 5 min. to read

In this topic

• Export ORDERS
• Import ORDERS
• Import ORDERSP
• Export ORDRSP
• Import DESADV
• Export DESADV
• Export INVOIC
• Import INVOIC

The process starts with the export of a purchase order.

Export ORDERS

If the "EDI Vendor" flag is enabled on the vendor, an EDI document is created when the purchase order is released. The created EDI document contains the following purchase order information: The document is created with the document type "ORDERS" and the status "Created". Additionally, the line information from the purchase order is added. If the purchase order is reopened, the system checks whether an EDI document with the status "Created" exists. If so, it is deleted and recreated upon release. This ensures the EDI document is always up to date. In the purchase order, two page actions exist to either create a new EDI document or open the existing one. These actions are only visible after releasing: If an EDI document already exists and a new one is to be created, a message with a notice is displayed. After creating an EDI document, the next step is to run a job queue. The codeunit "EDIExportOrdersNVX" must be configured and will export all created EDI documents in the process. This export uses the EDI interface "EDI Export", providing a web service URL as an endpoint. An XML file is then sent to the configured URL. After exporting an EDI document, the status is set to "Success". If a problem occurs, the status is set to "Error". Further details can be found in the transactions on the EDI card: The exported XML file can be downloaded from the transactions and the EDI card:

Import ORDERS

For ORDERS import, inbound files are fetched from the endpoint and processed via job queue. Prerequisites:

• An active EDI import interface using codeunit EDIProcessEndpointDocumentsNVX.
• An active EDI mapping for direction "Incoming" and EDI type "ORDERS".
• A valid data exchange definition configured in the mapping for ORDERS import.

The inbound XML file is imported into Data Exchange and processed by the configured mapping codeunit into intermediate and target data. This enables creation or update of sales orders from imported ORDERS data. For testing, the interface can run in Test Mode so files are not deleted from the endpoint after processing. Alternatively, the import can be started manually using the "Import File" action in the respective incoming EDI mapping.

Import ORDERSP

A separate EDI document is created for each export and import. After a purchase order has been released and the created EDI document was successfully sent, the next step is importing an "ORDERSP". This document type is a purchase order confirmation. A specific codeunit is used for the import of EDI documents, which must be set up in the job queues: This codeunit checks all documents available at the endpoint URL defined in the "EDI Import" interface. When an XML file is found in an import directory, it is processed and converted into an EDI document. Further information is then available on the EDI card for the "ORDERSP": This allows deviations from the sent purchase order to be identified. If a different quantity or price is confirmed, the flag "EDI Confirmation Deviation Present" is set. Once all data has been reviewed or no deviation exists, there are two ways to transfer the data to the purchase order: - The data is manually transferred into the purchase order: - The data is transferred automatically if enabled in the EDI interface setup: o A tolerance can also be configured here. If the imported data is within this tolerance, it is automatically accepted or offered for acceptance. The data (quantity, price, date) is transferred to the associated EDI purchase order. Once the data has been transferred, the fields "EDI Confirmation Checked By" and "EDI Confirmation Checked On" are filled with the current user and date. If positions in the imported document cannot be matched to purchase order lines, the import is stopped with an error.

Export ORDRSP

When a sales order is released, an outgoing ORDRSP EDI document can be created automatically. Prerequisites:

• ORDRSP is enabled on the EDI recipient.
• An active EDI mapping exists for direction "Outgoing" and EDI type "ORDRSP".
• The data exchange definition for ORDRSP export is configured correctly.

In addition, users can trigger processing manually on the sales order using "Create EDI-Document" and "Show EDI-Documents". For automated processing, use job queue codeunit EDIExportORDRSPNVX.

Import DESADV

Another document type is "DESADV", representing the delivery note. The data in this file confirms the actual delivered or used information. This allows Business Central to receive, for example, the vendor delivery number or tracking link. For this import, an EDI document with the document type "DESADV" is created: For imported documents, the direction is set to "Inbound". When importing the DESADV, the sales order is filtered via the purchase order. The following data from the XML file is transferred into the sales order: - Shipping Agent Code - Package Tracking Number Additionally, the field "EDI Delivered Quantity" from the XML file is transferred to the EDI document. Now, the EDI interface setup is checked. If the field "Automatically Take Over Data" is enabled, the field "Quantity Outstanding" is filled with the delivered quantity from the XML file. Furthermore, the vendor delivery number is transferred to the purchase order header. As the last step in the DESADV process, the EDI interface setup is checked again. If the field "Auto Post Shipment" is enabled: The purchase order is posted automatically, and a sales shipment is created. If positions in the imported document cannot be matched to purchase order lines, the import is stopped with an error.

Export DESADV

After posting a sales shipment, an outgoing DESADV EDI document can be created automatically. Prerequisites:

• DESADV is enabled on the EDI recipient.
• An active EDI mapping exists for direction "Outgoing" and EDI type "DESADV".
• The data exchange definition for DESADV export is configured correctly.

Additionally, users can work manually from the posted sales shipment using the actions "Create EDI-Document" and "Show EDI-Documents". For automated processing, use the job queue codeunit EDIExportDESADVNVX.

Export INVOIC

After posting a sales invoice, an outgoing INVOIC EDI document can be created automatically. Prerequisites:

• INVOIC is enabled on the EDI recipient.
• An active EDI mapping exists for direction "Outgoing" and EDI type "INVOIC".
• The data exchange definition for INVOIC export is configured correctly.

Additionally, users can work manually from the posted sales invoice using the actions "Create EDI-Document" and "Show EDI-Documents". For automated processing, use the job queue codeunit EDIExportINVOICNVX.

Import INVOIC

INVOIC import is currently not fully implemented.