1. Data Management
  2. EDI Studio
  3. EDI messages
  4. Seller messages

Sales order

If you want to use EDI to receive sales orders from a customer:

  • Set up the related document flow for the customer with the 'Sales - XML to EDI order' message or the 'Sales - XML order to Order' message from the desired tutorial project.
  • Use this setup to receive sales orders through EDI messages.


Application Consultant Application Consultant Seller Seller Start Start Set up document flow - Sales order Set up document flow - Sales order 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. 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. 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).If you use staging, make sure the appropriate journal validations are set up. End End EDI order message  file received from  customer EDI order message  file received from  customer Staging? Staging? Sales -  XML to EDI order  (850) Sales -  XML to EDI order  (850) Monitor EDI sales order journal

Monitor EDI sales order journal

Use the EDI sales order staging journal to monitor the EDI sales orders.

If you use staging in your EDI process for sales orders, the 'Sales - XML to EDI order' message imports the received sales orders into the EDI sales order journal.
These EDI sales orders are validated according to the applicable journal validation setup. If the applicable validation rules are:
  • Met, the EDI sales order is automatically approved. The approved EDI sales orders are processed by the 'Sales - EDI order to Order' message batch.
  • Not met, an error or warning is given. Before the EDI sales order can be processed further, review the errors and warnings, and take appropriate actions.

 Sales -  EDI order to Order Sales -  EDI order to Order Sales -  XML order to Order  (850) Sales -  XML order to Order  (850) Created or updated  sales order Created or updated  sales order Yes No

Activities

Name Responsible Description

Set up document flow - Sales order

Application Consultant
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.

Sales -  XML to EDI order  (850)

Seller

If you use staging, you receive an order from your customer with the 'Sales - XML to EDI order' message. This message imports the received order into the EDI sales order journal. When the import is completed, the applicable validations are done automatically.

Monitor EDI sales order journal

Seller

Use the EDI sales order staging journal to monitor the EDI sales orders.

If you use staging in your EDI process for sales orders, the 'Sales - XML to EDI order' message imports the received sales orders into the EDI sales order journal.
These EDI sales orders are validated according to the applicable journal validation setup. If the applicable validation rules are:
  • Met, the EDI sales order is automatically approved. The approved EDI sales orders are processed by the 'Sales - EDI order to Order' message batch.
  • Not met, an error or warning is given. Before the EDI sales order can be processed further, review the errors and warnings, and take appropriate actions.

Sales -  EDI order to Order

Seller

 		If EDI sales orders are validated and approved in the EDI sales order journal, these can be imported into the Sales orders table with the 'Sales - EDI order to Order' message.

Sales -  XML order to Order  (850)

Seller

 		If you do not use staging, you receive an order from your customer with the 'Sales - XML order to Order' message. This message imports the received order directly into the Sales orders table.

See also

Provide feedback