---
title: "Set up document flow - Purchase ASN"
slug: "set-up-document-flow-purchase-asn-edi-parties"
description: "Set up an EDI document flow to import packing slips and purchase arrival info from vendors, ensuring seamless integration and validation."
tags: ["Flow topic"]
updated: 2026-07-28T05:24:12Z
published: 2026-07-28T05:24:12Z
canonical: "docs.staedean.com/set-up-document-flow-purchase-asn-edi-parties"
---

> ## 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 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, you can set these EDI 856 or 945 messages (from the [Tutorial - EDI](/data-management/docs/edi-tutorial-projects#tutorial-edi)) or a custom 856 or 945 message to import purchase arrival information, also known as an advance shipping notice (ASN):

- 'Purchase - XML to EDI purchase arrival': If you use staging, use this message to receive purchase arrival information from your vendor. This message imports the received purchase arrival information into the EDI purchase arrival journal. When the import is completed, the applicable validations are done automatically.
- 'Purchase - XML to Delivery': If you do not use staging, use this message to receive purchase arrival information from your customer. This message imports the received purchase arrival information directly into the Item arrival 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 one of the mentioned messages as request message.

### Steps

1. Click **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]
> **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]
> **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. You can use a number sequence to define the **EDI history record ID**.

In the **Number sequence** field, enter or select a value.
10. You can use a document flow in a testing phase. If you do so, you can indicate this for informational purposes.

Select the **Test** check box.
11. Define the desired message or inbound web service action.

If you define a:

In the **Message** field or in the **Web service action** field, enter or select a value.
  - Message, and you want to:
    - Use staging, use a 'Purchase - XML to EDI purchase arrival' message.
    - Directly insert the purchase arrival information (ASN) into the Item arrival journal, use the 'Purchase - XML to Delivery' message from the 'Tutorial - EDI' project.
  - Web service action, make sure one of these messages is defined as the request message of the web service action.
12. By default, a document flow is active. You can deactivate a document flow. So, it isn't used.

Clear the **Active** check box.
13. Close the page.

> [!NOTE]
> **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).

## Related

- [Purchase ASN](/purchase-asn.md)
- [EDI tutorial projects](/edi-tutorial-projects.md)