1. Data Management
  2. EDI Studio
  3. Activities

Set up document flow - Sales order
Business Integration Solutions task

Set up a document flow to define how to import a received order from a specific customer.
On the document flow, you can set these EDI messages to import a sales order:
  • 'Sales - XML to EDI order': If you use staging, use this message to receive an order from your customer. This message imports the received sales order into the EDI sales order journal. When the import is completed, the applicable validations are done automatically.
  • 'Sales - XML order to Order': If you do not use staging, use this message to receive an order from your customer. This message imports the received sales order directly into the Sales orders table.

You can choose to exchange this EDI message using a web service. In this case, instead of a message, use an inbound web service action with one of the above messages as request message.


Standard procedure

1. Click Connectivity studio EDI Party setup.
2. Click the Document flow tab.
3. Click New.
4. You can use origins to indicate where messages originate from. For example, a message can originate from EDI, a web shop, or a customer self-service portal.
You can set the origin to indicate that the document flow only applies to messages with the same origin.
  In the Origin field, enter or select a value.
 

Note: If you do not define an origin, the document flow only applies to messages that also don't have the origin defined.
5. In the Account code field, select 'Customer'.
 

Note:
- For a sales order document flow, you can also select 'Legal entity'. You can use a legal entity document flow to receive sales order messages from a customer which, for example, does not exist in Microsoft Dynamics 365 for Finance and Operations or has no EDI party setup.
If you receive a sales order message from such a customer, it can be received with the document flow for your legal entity.
If the Account code is 'Legal entity', make sure an origin is filled in which Customer document flow is set to 'Customer + legal entity'.
- You can also select 'EDI group' to link the document flow to an EDI group. As a result, the document flow is applied to all EDI parties with the EDI group assigned.
6. In the Account selection field, enter or select a value.
7. In the Document flow field, select 'Order'.
8. In the Direction field, select 'Inbound'.
9. You can use a number sequence to define the EDI history record ID.
  In the Number sequence field, enter or select a value.
10. You can use a document flow in a testing phase. If you do so, you can indicate this for informational purposes.
  Select the Test check box.
11.

Define the desired message or inbound web service action.

If you define a:

  • Message, you can use one of these messages from the 'Tutorial - EDI' project. If you want to:
    • Use staging, select the 'Sales - XML to EDI order' message.
    • Directly insert the sales order, select the Sales - XML order to Order' message.
  • Web service action, make sure one of these messages is defined as the request message of the web service action.
  In the Message field or in the Web service action field, enter or select a value.
12. By default, a document flow is active. You can deactivate a document flow. So, it isn't used.
  Clear the Active check box.
13. Close the page.

Notes

  • To be able to receive an EDI message based on this document flow, the GLN code must be set for the current company (legal entity).
  • If you use staging, make sure the appropriate journal validations are set up.

Related to Notes

Sales order

 		 

Set up seller messages document flows

 		 

Provide feedback