1. To-Increase Dynamics 365 for Finance & Operations
  2. EDI studio
  3. General

Process EDI messages

If you use EDI, you process these types of messages:

  • Outbound messages
  • Inbound messages
  • EDI staging journal message


Application Consultant Application Consultant Start Start What must be  processed? What must be  processed? Process inbound messages Process inbound messages To process received EDI message files, run the Process inbound EDI documents batch job. Usually, you run this batch job in a recurring pattern.You run the Process inbound EDI documents batch job for a specific document flow type, and optionally for a specific message.Each time the batch job is run, all document flows of the defined document flow type are processed. So, all messages, as defined for these document flows, are run.Each message that is run, picks up the relevant received EDI message files (if any) from the location as defined for the message connector and processes the data. Procedure 1. Go to EDI > Periodic > Process inbound documents. 2. In the Document flow field, select the document flow type to be processed. 3. Optionally, in the Message field, enter or select a specific message to be run. 4. Sub-task: Set batch job recurrence. 5. Expand the Run in the background section. 6. Select Yes in the Batch processing field. 7. Click Recurrence and define the recurrence settings. 8. Click OK. 9. Click OK. Notes To process received EDI message files, you can also run a message itself in batch. Process staging journal messages Process staging journal messages If you use a staging journal in your EDI process, run the relevant messages to process the staging journals.The message processes all relevant staging journals with status 'Approved' and message status 'To be processed'.If processing the journal goes:Fine, the EDI staging journal message status is set to 'Processed'.Wrong, the EDI staging journal message status is set to 'Error'.For more information on how to solve EDI staging journal processing errors, refer to:"Monitor EDI sales order journal""Monitor EDI purchase order confirmation journal""Monitor EDI inventory order journal" Procedure 1. Go to Connectivity studio > Common > Connectivity > Message. 2. In the list, find and select the desired staging journal message. 3. On the Action Pane, click Operation. 4. Click Run. 5. Sub-task: Set batch job recurrence. 6. Expand the Run in the background section. 7. Select Yes in the Batch processing field. 8. Click Recurrence and define the recurrence settings. 9. Click OK. 10. Click OK. Notes To process EDI staging journals, no document flows are used.You can also run messages in a project where you can use tasks to define the dependencies between messages. Process outbound messages Process outbound messages If you use EDI messages and post one of the following journals, also a record is added to the Outbound message queue: Confirm sales order Post packing slip Post sales invoice Confirm purchase order Generate picking list Generate receipts list Also, a record can be added to the Outbound message queue for sales acknowledgements. When a received sales order message is processed, it is added to the EDI history (with direction 'Inbound' and type 'Order'). If a document flow of type 'Acknowledge' exists for the customer, also a record is created in the Outbound message queue. An outbound message queue record indicates which message must be run for which journal (or EDI history record in case of a sales acknowledgement). The message to be run is defined by the applicable document flow. When the record is added to the Outbound message queue, the applicable document flow is searched for, and the related message is linked to the Outbound message queue record. To process the outbound message queue, run the Process outbound message queue batch job. Usually, you run this batch job in a recurring pattern. You process the outbound message queue for a specific message. Optionally you can run a message for a specific company. If you use a web service, as defined on the applicable document flow, also define the applicable web service action here. Procedure 1. Go to EDI > Periodic > Process outbound message queue. 2. In the Message field, enter or select the message to be processed. 3. Optionally, in the Company field, enter or select the legal entity for which you want to run the message. 4. In the Web service action field, enter or select a value. 5. Sub-task: Set batch job recurrence. 6. Expand the Run in the background section. 7. Select Yes in the Batch processing field. 8. Click Recurrence and define the recurrence settings. 9. Click OK. 10. Click OK. Notes You can monitor the Outbound message queue. To do so, go to EDI > Inquiries > Outbound message queue. End End Inbound  messages Outbound  messages Staging  journal  messages

Activities

Name Responsible Description

Process inbound messages

Application Consultant

 		To process received EDI message files, run the Process inbound EDI documents batch job. Usually, you run this batch job in a recurring pattern.
You run the Process inbound EDI documents batch job for a specific document flow type, and optionally for a specific message.
Each time the batch job is run, all document flows of the defined document flow type are processed. So, all messages, as defined for these document flows, are run.
Each message that is run, picks up the relevant received EDI message files (if any) from the location as defined for the message connector and processes the data.

Process staging journal messages

Application Consultant

 		If you use a staging journal in your EDI process, run the relevant messages to process the staging journals.
The message processes all relevant staging journals with status 'Approved' and message status 'To be processed'.
If processing the journal goes:
  • Fine, the EDI staging journal message status is set to 'Processed'.
  • Wrong, the EDI staging journal message status is set to 'Error'.
For more information on how to solve EDI staging journal processing errors, refer to:
  • "Monitor EDI sales order journal"
  • "Monitor EDI purchase order confirmation journal"
  • "Monitor EDI inventory order journal"

Process outbound messages

Application Consultant
If you use EDI messages and post one of the following journals, also a record is added to the Outbound message queue:
  • Confirm sales order
  • Post packing slip
  • Post sales invoice
  • Confirm purchase order
  • Generate picking list
  • Generate receipts list
Also, a record can be added to the Outbound message queue for sales acknowledgements. When a received sales order message is processed, it is added to the EDI history (with direction 'Inbound' and type 'Order'). If a document flow of type 'Acknowledge' exists for the customer, also a record is created in the Outbound message queue.
An outbound message queue record indicates which message must be run for which journal (or EDI history record in case of a sales acknowledgement). The message to be run is defined by the applicable document flow. When the record is added to the Outbound message queue, the applicable document flow is searched for, and the related message is linked to the Outbound message queue record.
To process the outbound message queue, run the Process outbound message queue batch job. Usually, you run this batch job in a recurring pattern.
You process the outbound message queue for a specific message. Optionally you can run a message for a specific company.

If you use a web service, as defined on the applicable document flow, also define the applicable web service action here.

Process EDI messages using AS2

You can use EDI studio to exchange EDI messages using the AS2 web app. In this case, the process differs from standard EDI message processing.

Search for document flow

Provide feedback