1. To-Increase Dynamics 365 for Finance & Operations
  2. EDI studio
  3. General
  4. Process EDI messages
  5. Process EDI messages using AS2

Process EDI messages using AS2 - Outbound

You can use EDI studio to send EDI messages to the AS2 web app. The AS2 web app processes the data further to the web server of the EDI partner.

Set up the Process outbound message queue to process the outbound web service actions as set up for AS2.


Application Consultant Application Consultant Start Start 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. Run AS2 web app - Outbound Run AS2 web app - Outbound If you use the AS2 protocol to send EDI messages to an EDI partner, use the AS2 web app to manage the interaction with the EDI partner. The AS2 web app runs in the Azure cloud. When you run a web service action using the AS2 protocol, an EDI message is sent to the AS2 web app. The web service action calls the send method of the AS2 web app to send the data to the EDI partner. The AS2 web app send method: Encrypts the data. Signs the data. Compresses the data, if applicable. Sends the data to the web server of the EDI partner. Receives an MDN reply from the web server of the EDI partner. Sends the MDN reply from the EDI partner to EDI history of the web service action in EDI studio that originally sent the data. Notes The EDI message body, as sent to the AS2 web app, for example, looks like: {     "encoding": "Binary",     "documentContent":"PHJvb3Q+dGVzdCAyPC9yb290Pg==",     "filename": "test.xml",     "documentContentFormat": "Base64String" } Explanation of the body elements: Body element Required Description Default value encoding Yes The encoding is parsed into Mimekit enum ContentEncoding. Binary documentContent Yes The content of the message. - filename Yes The filename is forwarded to the EDI partner. - documentContentFormat No The content format is set by an optional attribute on the web service action. If the attribute exists and no value is set, the default value PlainText is applied. If the attribute value is set to Base64String, the content is first decoded, and then processed. PlainText Data sent to  external web server Data sent to  external web server MDN reply MDN reply

Activities

Name Responsible Description

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.

Run AS2 web app - Outbound

Application Consultant

If you use the AS2 protocol to send EDI messages to an EDI partner, use the AS2 web app to manage the interaction with the EDI partner.

The AS2 web app runs in the Azure cloud.

When you run a web service action using the AS2 protocol, an EDI message is sent to the AS2 web app.

The web service action calls the send method of the AS2 web app to send the data to the EDI partner.

The AS2 web app send method:

  • Encrypts the data.
  • Signs the data.
  • Compresses the data, if applicable.
  • Sends the data to the web server of the EDI partner.
  • Receives an MDN reply from the web server of the EDI partner.
  • Sends the MDN reply from the EDI partner to EDI history of the web service action in EDI studio that originally sent the data.

See also

Provide feedback