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

Process EDI messages using AS2 - Inbound
Activity Flow

You can use EDI studio to receive EDI message files from the AS2 web app. These EDI message files are stored in a general storage location. From the general storage location, these EDI message files must be distributed to specific storage locations from where the files can be processed by the applicable inbound messages.

Application Consultant Application Consultant External web server  sends data to  AS2 web app External web server  sends data to  AS2 web app Run AS2 web app - Inbound Run AS2 web app - Inbound If you use the AS2 protocol to receive EDI messages from 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 the web server of the EDI partner sends data to the AS2 web app, it: Decompresses the received data, if the received data is compressed. Decrypts the data. Checks the signature. Stores the data in an EDI message file in the general storage location. Sends an MDN reply to the web server of the EDI partner. The MDN reply can be that the data is: Processed successfully. Not processed because something went wrong. For example, the data cannot be decrypted, or the signature is invalid. AS2 inbound  message file AS2 inbound  message file AS2 inbound message  files stored in general  storage location AS2 inbound message  files stored in general  storage location Distribute AS2 inbound message files Distribute AS2 inbound message files You can use EDI studio to receive EDI message files from the AS2 web app. These EDI message files are stored in a general storage location. From the general storage location, these EDI message files must be distributed to specific storage locations from where the files can be processed by the applicable inbound messages. To distribute the EDI message files from the general storage location, run the project inbound definitions. Usually, you run the inbound definitions in recurring mode. Always, all inbound definitions of the selected project are run. The inbound definitions are run in the defined sequence. When an inbound definition is run: It connects to the general storage location as defined by the connector. The EDI message files that match the read filter are opened to search for this data: Type: The EDI message type of the data in the file. For example, 'Order' or 'Invoice'. Recipient: The data in the file that indicates to which company in D365 FO the data must be imported. For example, the GLN. Based on this data, the applicable file distribution definition is determined. The message, as defined for the applicable file distribution definition is used to: Rename the EDI message file: If renaming is applicable, the source document of the message defines how the EDI message file is renamed. Move the EDI message file: The source connector of the message defines to which specific storage location the EDI message file is moved for further processing. If the inbound definition is mandatory, and an EDI message file cannot be processed, the EDI message file is moved to the error location as defined for the connector. Procedure 1. Click Connectivity studio EDI integration design. 2. Click Projects. 3. On the Action Pane, click Design. 4. Click Inbound definition. 5. On the Action Pane, click Inbound definition. 6. Click Process AS2 Inbound Queue. 7. In the Project field, enter or select the desired project. 8. Sub-task: Set batch job recurrence. 9. Expand the Run in the background section. 10. Select Yes in the Batch processing field and fill in the fields as desired. 11. Click Recurrence and define the recurrence settings. 12. Click OK. 13. Click OK. AS2 inbound  message file AS2 inbound  message file AS2 inbound message  files stored in specific  locations AS2 inbound message  files stored in specific  locations 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. End End MDN reply

Activities

Name Responsible Description

Run AS2 web app - Inbound

Application Consultant

If you use the AS2 protocol to receive EDI messages from 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 the web server of the EDI partner sends data to the AS2 web app, it:

  1. Decompresses the received data, if the received data is compressed.
  2. Decrypts the data.
  3. Checks the signature.
  4. Stores the data in an EDI message file in the general storage location.
  5. Sends an MDN reply to the web server of the EDI partner. The MDN reply can be that the data is:
    • Processed successfully.
    • Not processed because something went wrong. For example, the data cannot be decrypted, or the signature is invalid.

AS2 inbound message file

Application Consultant

When the:

  • AS2 web app is run on the inbound side, EDI message files are stored in a general storage location.
  • Inbound definitions are run, the EDI message files are distributed to the specific storage locations.

Distribute AS2 inbound message files

Application Consultant

You can use EDI studio to receive EDI message files from the AS2 web app. These EDI message files are stored in a general storage location. From the general storage location, these EDI message files must be distributed to specific storage locations from where the files can be processed by the applicable inbound messages.

To distribute the EDI message files from the general storage location, run the project inbound definitions. Usually, you run the inbound definitions in recurring mode. Always, all inbound definitions of the selected project are run. The inbound definitions are run in the defined sequence.

When an inbound definition is run:

  1. It connects to the general storage location as defined by the connector.
  2. The EDI message files that match the read filter are opened to search for this data:
    • Type: The EDI message type of the data in the file. For example, 'Order' or 'Invoice'.
    • Recipient: The data in the file that indicates to which company in D365 FO the data must be imported. For example, the GLN.
  3. Based on this data, the applicable file distribution definition is determined.
  4. The message, as defined for the applicable file distribution definition is used to:
    • Rename the EDI message file: If renaming is applicable, the source document of the message defines how the EDI message file is renamed.
    • Move the EDI message file: The source connector of the message defines to which specific storage location the EDI message file is moved for further processing.
  5. If the inbound definition is mandatory, and an EDI message file cannot be processed, the EDI message file is moved to the error location as defined for the connector.

AS2 inbound message file

Application Consultant

When the:

  • AS2 web app is run on the inbound side, EDI message files are stored in a general storage location.
  • Inbound definitions are run, the EDI message files are distributed to the specific storage locations.

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.

Activities

Name Responsible Description

Run AS2 web app - Inbound

Application Consultant

If you use the AS2 protocol to receive EDI messages from 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 the web server of the EDI partner sends data to the AS2 web app, it:

  1. Decompresses the received data, if the received data is compressed.
  2. Decrypts the data.
  3. Checks the signature.
  4. Stores the data in an EDI message file in the general storage location.
  5. Sends an MDN reply to the web server of the EDI partner. The MDN reply can be that the data is:
    • Processed successfully.
    • Not processed because something went wrong. For example, the data cannot be decrypted, or the signature is invalid.

AS2 inbound message file

Application Consultant

When the:

  • AS2 web app is run on the inbound side, EDI message files are stored in a general storage location.
  • Inbound definitions are run, the EDI message files are distributed to the specific storage locations.

Distribute AS2 inbound message files

Application Consultant

You can use EDI studio to receive EDI message files from the AS2 web app. These EDI message files are stored in a general storage location. From the general storage location, these EDI message files must be distributed to specific storage locations from where the files can be processed by the applicable inbound messages.

To distribute the EDI message files from the general storage location, run the project inbound definitions. Usually, you run the inbound definitions in recurring mode. Always, all inbound definitions of the selected project are run. The inbound definitions are run in the defined sequence.

When an inbound definition is run:

  1. It connects to the general storage location as defined by the connector.
  2. The EDI message files that match the read filter are opened to search for this data:
    • Type: The EDI message type of the data in the file. For example, 'Order' or 'Invoice'.
    • Recipient: The data in the file that indicates to which company in D365 FO the data must be imported. For example, the GLN.
  3. Based on this data, the applicable file distribution definition is determined.
  4. The message, as defined for the applicable file distribution definition is used to:
    • Rename the EDI message file: If renaming is applicable, the source document of the message defines how the EDI message file is renamed.
    • Move the EDI message file: The source connector of the message defines to which specific storage location the EDI message file is moved for further processing.
  5. If the inbound definition is mandatory, and an EDI message file cannot be processed, the EDI message file is moved to the error location as defined for the connector.

AS2 inbound message file

Application Consultant

When the:

  • AS2 web app is run on the inbound side, EDI message files are stored in a general storage location.
  • Inbound definitions are run, the EDI message files are distributed to the specific storage locations.

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.
Related to Notes

Set up AS2 - Inbound

 		 

Process EDI messages using AS2 - Inbound

 		 

Provide feedback