1. To-Increase Dynamics 365 for Finance & Operations
  2. EDI studio
  3. General
  4. Set up EDI
  5. Set up document flows

Set up 3PL messages document flows

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


Application Consultant Application Consultant Start Start Set up document flow - Picking list Set up document flow - Picking list Set up a document flow to send a picking list message to a specific 3PL warehouse. On the document flow, set the 'Warehouse - Picking list to XML' message. This message sends the picking list to the 3PL warehouse. 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 'Warehouse - Picking list 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 'Site' or 'Warehouse'. 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 'Picking'. 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 - Picking list registration Set up document flow - Picking list registration Set up a document flow to define how to import a picking list registration that you received from a specific 3PL warehouse. On the document flow, you can set one of these EDI messages to import a picking list registration: 'XML picking list registration to EDI inventory order' (custom message): If you use staging, use this message to receive a picking list registration from a 3PL warehouse. This message imports the received picking list registration into the EDI inventory order journal. When the import is completed, the applicable validations are done automatically. 'Warehouse - XML to Picking list registration': If you do not use staging, use this message to receive a picking list registration from a 3PL warehouse. This message imports the received picking list registration directly into the Picking list registration journal. 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. 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 'Site' or 'Warehouse'. 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 'Picking'. 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 - Receipts list Set up document flow - Receipts list Set up a document flow to send a receipts list message to a specific 3PL warehouse. On the document flow, set the 'Warehouse - Receipts list to XML' message. This message sends the receipts list to the 3PL warehouse. 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 'Warehouse - Receipts list 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 'Site' or 'Warehouse'. 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 'Receipts list'. 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 - Product receipt Set up document flow - Product receipt Set up a document flow to define how to import a product receipt that you received from a specific 3PL warehouse. On the document flow, you can set one of these EDI messages to import a product receipt: 'XML product receipt to EDI inventory order' (custom message): If you use staging, use this message to receive a product receipt from a 3PL warehouse. This message imports the received product receipt into the EDI inventory order journal. When the import is completed, the applicable validations are done automatically. 'Warehouse - XML to Arrival journal': If you do not use staging, use this message to receive a product receipt from a 3PL warehouse. This message imports the received product receipt directly into the Arrival journal. 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. 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 'Site' or 'Warehouse'. 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 'Receipts list'. 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 - Item counting Set up document flow - Item counting Set up a document flow to import an item counting message from a specific 3PL warehouse. On the document flow, set the 'Warehouse - XML to Counting journal' message. This message receives the item counting information from the 3PL warehouse. 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 'Warehouse - XML to Counting journal' 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 'Site' or 'Warehouse'. 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 'Inventory count'. 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). End End

Activities

Name Responsible Description

Set up document flow - Picking list

Application Consultant

Set up a document flow to send a picking list message to a specific 3PL warehouse.

On the document flow, set the 'Warehouse - Picking list to XML' message. This message sends the picking list to the 3PL warehouse.

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 'Warehouse - Picking list to XML' message as request message.

Set up document flow - Picking list registration

Application Consultant

Set up a document flow to define how to import a picking list registration that you received from a specific 3PL warehouse.

On the document flow, you can set one of these EDI messages to import a picking list registration:

  • 'XML picking list registration to EDI inventory order' (custom message): If you use staging, use this message to receive a picking list registration from a 3PL warehouse. This message imports the received picking list registration into the EDI inventory order journal. When the import is completed, the applicable validations are done automatically.
  • 'Warehouse - XML to Picking list registration': If you do not use staging, use this message to receive a picking list registration from a 3PL warehouse. This message imports the received picking list registration directly into the Picking list registration journal.

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.

Set up document flow - Receipts list

Application Consultant

Set up a document flow to send a receipts list message to a specific 3PL warehouse.

On the document flow, set the 'Warehouse - Receipts list to XML' message. This message sends the receipts list to the 3PL warehouse.

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 'Warehouse - Receipts list to XML' message as request message.

Set up document flow - Product receipt

Application Consultant

Set up a document flow to define how to import a product receipt that you received from a specific 3PL warehouse.

On the document flow, you can set one of these EDI messages to import a product receipt:

  • 'XML product receipt to EDI inventory order' (custom message): If you use staging, use this message to receive a product receipt from a 3PL warehouse. This message imports the received product receipt into the EDI inventory order journal. When the import is completed, the applicable validations are done automatically.
  • 'Warehouse - XML to Arrival journal': If you do not use staging, use this message to receive a product receipt from a 3PL warehouse. This message imports the received product receipt directly into the Arrival journal.

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.

Set up document flow - Item counting

Application Consultant

Set up a document flow to import an item counting message from a specific 3PL warehouse.

On the document flow, set the 'Warehouse - XML to Counting journal' message. This message receives the item counting information from the 3PL warehouse.

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 'Warehouse - XML to Counting journal' message as request message.

Provide feedback