1. Data Management
  2. EDI Studio
  3. Activities

Set up EDI party setup for customer
Business Integration Solutions task

Before you can exchange EDI messages with a customer, set up the related EDI party setup.

For each customer, you can set up several EDI parties. For example, if a customer has several shops, you can set up an EDI party for each shop.


Standard procedure

1. Go to Accounts receivable > Customers > All customers.
2. In the list, find and select the desired record.
3. On the Action pane, on the Customer tab, in the EDI group, click Party setup.
4. Click New.
5. You can make the party setup the default setup for manually created orders. So, for example, on manual creation of an order, the origin is defaulted from the party setup.
  Select Yes in the Default field.
6. Use the origin to indicate where messages originate from. For each origin, the document flow behavior can be defined.
  In the Origin field, enter or select a value.
 

Note: For each customer you can only set up:
- One EDI party for each origin.
- One EDI party without the origin defined. You can use this, for example, if you only define one EDI party for a customer.
7. If the GLN code is a bar code, you must define the relevant bar code setup.
Usually, the GLN code is a 13-digit number. However, you can also define your own location number. And accordingly, define the related bar code setup.
  In the Bar code setup field, enter or select a value.
8. You can enter the Global Location Number (GLN code) of the customer. This usually is a unique 13-digit identification of the location of the customer. However, you can also define your own location number.
  In the GLN code field, type a value.
 

Note: You can use a specific GLN code but once. If you have set it for a customer, you cannot set it for another customer as well.
9. You can use EDI groups to group several EDI parties for which the same document flow setup is required.
To an EDI party, you can assign a different EDI group for each origin.
When you set up a document flow, you can link it to an EDI group. As a result, the document flow is applied to all EDI parties with the EDI group assigned.
  In the EDI group field, enter or select a value.
10. An EDI party can be part of another organization that does send and receive their EDI messages. We refer to this as an EDI partner. For example, the head quarter of your customer does send and receive all EDI messages instead of your customer.
In this case:
- Define the EDI partner for your EDI party.
- Only set up document flows and journal validations for the EDI partner of your EDI party. These are automatically applied if you exchange EDI messages with your EDI party.
  In the EDI partner field, enter or select a value.
11. You can receive EDI orders with customer specific item codes. To prevent messing up your data with customer specific codes, you can use an item cross reference. If you use this, the EDI sales journal validation searches for the item in this sequence:
1. Defined item coding for the party. If an item is found that matches the defined item coding, this item number is used.
2. Item cross reference table. If no matching item is found for the defined item coding, a matching item is searched for in the item cross references. If found, the item from the item cross reference is used. If not found, an error message is given, and the EDI message cannot be processed.
  Select Yes in the Item cross reference field.
 

Note: If you want to use an item cross reference, you must also set up the item cross reference from the EDI sales order journal line.
12. Use the item coding to indicate how you usually receive or send an item identification.
If you:
- Receive an item identification, the item coding is used to find the matching item number in Microsoft Dynamics 365 for Finance and Operations.
- Send an item identification, the item coding is used to send the appropriate item identification to the customer.
  In the Item coding field, select an option.
13. If the item coding is of type Bar code, you also define the applicable bar code setup. So, you can only:
- Receive item bar codes that meet the defined bar code setup.
- Send item bar codes with the defined bar code setup.
  In the Bar code setup field, enter or select a value.
14. Sub-task: Define external code definitions.
  14.1 For each party setup, you can define several external code definitions. These external code definitions are used to search for party-specific values.
  Expand the External code section.
 

Note:
To use the external codes functionality, additional setup is required in Connectivity studio. For the applicable message, in the field mapping, apply an external code as defined for the related entity.
As a result, on:
- Import, the external code is replaced with the related code in your D365 FO environment.
- Export, the code in your D365 FO environment is replaced with the related external code.
  14.2 You can define an external code definition as set up for currencies.
  In the Currency external code field, enter or select a value.
  14.3 You can define an external code definition as set up for released products.
  In the Item external code field, enter or select a value.
  14.4 You can define an external code definition as set up for charge codes of miscellaneous charges.
  In the Misc. charges external code field, enter or select a value.
  14.5 You can define an external code definition as set up for modes of delivery.
  In the Mode of delivery external code field, enter or select a value.
  14.6 You can define an external code definition as set up for terms of delivery.
  In the Terms of delivery external code field, enter or select a value.
  14.7 You can define an external code definition as set up for units.
  In the Unit external code field, enter or select a value.
15. Close the page.
Related to Notes

Set up EDI for customer

 		 

Provide feedback