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

Set up document flow - Purchase order
Business Integration Solutions task

Set up a document flow to define how to send a purchase order message to a specific vendor.

On the document flow, set the 'Purchase - Order to XML' message. This message sends the purchase order to your vendor.

You can choose to exchange this EDI message using a web service. In this case, instead of the message, use an outbound web service action with the 'Purchase - Order to XML' message 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 'Vendor'.
 

Note: 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 'Outbound'.
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 outbound web service action.

If you define a:

  • Message, you can use the 'Purchase - Order to XML' message from the 'Tutorial - EDI' project.
  • Web service action, make sure the 'Purchase - Order to XML' message 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. In the outbound queue, several entries can exist for a unique message or web service action. For an outbound document flow, you can bundle the entries for the applicable message or web service action. The outbound queue entries are bundled by the applicable EDI party. On processing the outbound queue, the entries are bundled in one message run or web service action run, which results in one file.
  Select the Bundle outbound queue by message check box.
 

Note:
- If, for the document flow, the account code is EDI group, the outbound queue entries are bundled by each EDI party as set up for the EDI group.
- You can also apply bundling to the Additional setup of an outbound document flow.
13. In some cases, for outbound, you only want to run a message or web service action for records that fit a defined range. You can have the range of the source document checked before the message or web service action is run. If the record doesn't meet the range, the Outbound queue status is set to 'No data exported' instead of 'Error'.
Example: You run an EDI message on sales orders. However, you also receive return orders. For these return orders, no invoice amount is filled in. So, you only want to run the EDI message for sales orders with an invoice amount filled in. On the source document, you can define a range to check this.
  Select the Flow condition check box.
14. You can define a target connector for a document flow. This target connector overrules the target connector of the document flow message. In this way, you can use one message to send an EDI message to several EDI parties. So, no separate message is required for each of the EDI parties.
  In the Connector field, enter or select a value.
 

Note:

To apply a document flow target connector:

  • For each target, enter a document flow with the same message but a different target connector.
  • The target connector you define for the document flow must match the type of the target connector of the message. If the message connector type is:
    • D365 FO -> D365 FO
    • Database -> Database
    • Staging journal -> Staging journal
    • Azure file storage, Azure Blob Storage, and SharePoint are interchangeable.
    • Connectors of type 'Web service' or 'Upload and download' are not supported.
  • The data structure of the different targets must be the same.
15. By default, a document flow is active. You can deactivate a document flow. So, it isn't used.
  Clear the Active check box.
16. Close the page.

Notes

To be able to send an EDI message based on this document flow, the GLN code must be set for the current company (legal entity).

Related to Notes

Purchase order

 		 

Set up buyer messages document flows

 		 

See also

Provide feedback