1. Data Management
  2. EDI Studio
  3. General
  4. Set up EDI
  5. Set up document flows

Set up buyer messages document flows

This flow explains how to set up the document flows for EDI messages that a buyer can send to or receive from a seller.

Note: Based on the outbound document flows as defined for a vendor, on the purchase order header, in the EDI section, options are selected. These options indicate which document flows apply to the purchase order. Usually, you do not change these settings. However, if required, you can switch off a document flow for a purchase order.


Application Consultant Application Consultant Start Start Set up document flow - Purchase order Set up document flow - Purchase order 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. 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. In the Number sequence field, enter or select a value. 10. Select the Test check box. 11. 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. 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. 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). Set up document flow - Purchase acknowledgement Set up document flow - Purchase acknowledgement Set up a document flow to define how to import an order acknowledgement message from a specific vendor. On the document flow, set the 'Purchase - XML to Acknowledgement' message. This message updates the acknowledgement status in the EDI history. You can choose to exchange this EDI message using a web service. In this case, instead of the message, use an inbound web service action with the 'Purchase - XML to Acknowledgement' message as request message. 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 'Acknowledge'. 8. In the Direction field, select 'Inbound'. 9. In the Number sequence field, enter or select a value. 10. Select the Test check box. 11. In the Message field or in the Web service action field, enter or select a value. 12. 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). Set up document flow - Purchase order confirmation Set up document flow - Purchase order confirmation Set up a document flow to define how to import an order confirmation message from a specific vendor. On the document flow, set the 'Purchase - XML to EDI confirmation' message. This message imports the order confirmation into the EDI purchase order journal. When the import is completed, the applicable validations are done automatically. You can choose to exchange this EDI message using a web service. In this case, instead of the message, use an inbound web service action with the 'Purchase - XML to EDI confirmation' message as request message. 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 'Confirmation'. 8. In the Direction field, select 'Inbound'. 9. In the Number sequence field, enter or select a value. 10. Select the Test check box. 11. In the Message field or in the Web service action field, enter or select a value. 12. 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).Make sure, the appropriate journal validations are set up. Set up document flow - Purchase ASN Set up document flow - Purchase ASN Set up a document flow to define how to import a packing slip message from a specific vendor. On the document flow, set the 'Purchase - XML to Delivery' message. This message imports the packing slip from your vendor into the arrival journal. This message is also known as an advance shipping notice (ASN). You can choose to exchange this EDI message using a web service. In this case, instead of the message, use an inbound web service action with the 'Purchase - XML to Delivery' message as request message. 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 'Advance Ship Notice'. 8. In the Direction field, select 'Inbound'. 9. In the Number sequence field, enter or select a value. 10. Select the Test check box. 11. In the Message field or in the Web service action field, enter or select a value. 12. 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). Set up document flow - Purchase invoice Set up document flow - Purchase invoice Set up a document flow to define how to import an invoice message from a specific vendor. On the document flow, set the 'Purchase - XML to Invoice' message. This message imports the invoice from your vendor into the invoice register journal. You can choose to exchange this EDI message using a web service. In this case, instead of the message, use an inbound web service action with the 'Purchase - XML to Invoice' message as request message. 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 code field, select 'Vendor'. 7. In the Account selection field, enter or select a value. 8. In the Document flow field, select 'Invoice'. 9. In the Direction field, select 'Inbound'. 10. In the Number sequence field, enter or select a value. 11. Select the Test check box. 12. In the Message field or in the Web service action field, enter or select a value. 13. Clear the Active check box. 14. 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). End End

Activities

Name Responsible Description

Set up document flow - Purchase order

Application Consultant

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.

Set up document flow - Purchase acknowledgement

Application Consultant

Set up a document flow to define how to import an order acknowledgement message from a specific vendor.

On the document flow, set the 'Purchase - XML to Acknowledgement' message. This message updates the acknowledgement status in the EDI history.

You can choose to exchange this EDI message using a web service. In this case, instead of the message, use an inbound web service action with the 'Purchase - XML to Acknowledgement' message as request message.

Set up document flow - Purchase order confirmation

Application Consultant

Set up a document flow to define how to import an order confirmation message from a specific vendor.

On the document flow, set the 'Purchase - XML to EDI confirmation' message. This message imports the order confirmation into the EDI purchase order journal. When the import is completed, the applicable validations are done automatically.

You can choose to exchange this EDI message using a web service. In this case, instead of the message, use an inbound web service action with the 'Purchase - XML to EDI confirmation' message as request message.

Set up document flow - Purchase ASN

Application Consultant

Set up a document flow to define how to import a packing slip message from a specific vendor.

On the document flow, set the 'Purchase - XML to Delivery' message. This message imports the packing slip from your vendor into the arrival journal. This message is also known as an advance shipping notice (ASN).

You can choose to exchange this EDI message using a web service. In this case, instead of the message, use an inbound web service action with the 'Purchase - XML to Delivery' message as request message.

Set up document flow - Purchase invoice

Application Consultant

Set up a document flow to define how to import an invoice message from a specific vendor.

On the document flow, set the 'Purchase - XML to Invoice' message. This message imports the invoice from your vendor into the invoice register journal.

You can choose to exchange this EDI message using a web service. In this case, instead of the message, use an inbound web service action with the 'Purchase - XML to Invoice' message as request message.

Provide feedback