---
title: "Set up EDI party setup for warehouse"
slug: "set-up-edi-party-setup-for-warehouse"
description: "Set up EDI party configurations for 3PL warehouses, manage document flows, and define external codes for efficient inventory management."
tags: ["Task topic"]
updated: 2026-07-30T04:40:02Z
published: 2026-07-30T04:40:02Z
canonical: "docs.staedean.com/set-up-edi-party-setup-for-warehouse"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up EDI party setup for warehouse

Before you can exchange EDI messages with a 3PL warehouse or an external warehouse management system (WMS), set up the related EDI party setup.

For each warehouse, you can set up several EDI parties. For example, if a warehouse has several areas, you can set up an EDI party for each area.

This EDI party setup for warehouses applies to EDI messages for 3PL and transfer orders.

### Steps

1. **Go to Inventory management** > **Setup** > **Inventory breakdown** > **Warehouses**.
2. In the list, find and select the desired record.
3. On the **Action Pane**, click **Warehouse**.
4. In the **EDI group**, click **Party setup**.
5. Click **New**.
6. 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.
7. Use the origin to indicate where messages originate from.

In the **Origin** field, enter or select a value.

> [!NOTE]
> **Note**
> 
> For each warehouse 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 warehouse.
> - For each origin, the document flow behavior can be defined. However, the document flow behavior is not applicable to warehouses.
8. 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.
9. You can enter the Global Location Number (GLN code) of the warehouse. This usually is a unique 13-digit identification of the location of the warehouse. However, you can also define your own location number.

In the **GLN code** field, type a value.

> [!NOTE]
> **Note**
> 
> You can use a specific GLN code but once. If you have set it for a warehouse, you cannot set it for another warehouse as well.
10. 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.
11. Select **Yes** in the **Item cross reference** field.
12. Use the item coding to indicate how you usually receive or send an item identification. If you:

In the **Item coding** field, select an option.

> [!NOTE]
> **Note**
> 
> Item cross references are only applicable to customers. So, these are not applied for warehouses.
  - Receive an item identification, the item coding is used to find the matching item number in D365 F&SCM.
  - Send an item identification, the item coding is used to send the appropriate item identification to the warehouse.
13. If the item coding is of type **Bar code**, you also define the applicable bar code setup. So, you can only:

In the **Bar code setup** field, enter or select a value.
  - Receive item bar codes that meet the defined bar code setup.
  - Send item bar codes with the defined bar code setup.
14. Sub-task: Define external code definitions.
  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]
> **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 F&SCM environment.
> - Export, the code in your D365 F&SCM environment is replaced with the related external code.
  2. You can define an external code definition as set up for currencies.

In the **Currency external code** field, enter or select a value.
  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.
  4. You can define an external code definition as set up for charge codes of miscellaneous charges.

In the **Miscellaneous charges external code** field, enter or select a value.
  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.
  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.
  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

- [Set up EDI for warehouse](/set-up-edi-for-warehouse.md)
- [3PL EDI messages](/3pl-edi-message.md)
- [Transfer order messages](/transfer-order-messages.md)