Flow | Description |
---|---|
Item counting |
If you want to use EDI to receive item counts from a 3PL warehouse:
|
Monitor EDI Delfor journal |
Use the EDI Delfor journal to monitor the received EDI sales orders (Delfor). The 'Sales (Delfor) - XML to EDI Delfor journal' message imports the received sales orders (Delfor) into the EDI Delfor journal.
These EDI Delfor journals are validated according to the applicable journal validation setup. If the applicable validation rules are:
|
Monitor EDI inventory order journal |
Use the EDI inventory order staging journal to monitor the EDI inventory orders. If you use EDI inventory order staging, custom messages are required. You can, for example, use staging in your EDI process for picking list registrations or product receipts. You can use these messages to import the received information into the EDI inventory order journal:
The EDI inventory orders are validated according to the applicable journal validation setup. If the applicable validation rules are:
|
Monitor EDI purchase order confirmation journal |
Use the EDI purchase order staging journal to monitor the EDI purchase order confirmations. You always use staging in your EDI process for purchase order confirmation. The 'Purchase - XML to EDI confirmation' message is used to import the received purchase order confirmations into the EDI purchase order journal.
These EDI purchase order confirmations are validated according to the applicable journal validation setup. If the applicable validation rules are:
|
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:
|
Picking list |
If you want to use EDI to send picking lists to a 3PL warehouse:
|
Picking list registration |
If you want to use EDI to receive picking list registrations from a 3PL warehouse:
|
Process EDI messages using AS2 - Inbound |
You can use EDI studio to receive EDI message files from the AS2 web app. These EDI message files are stored in a general storage location. From the general storage location, these EDI message files must be distributed to specific storage locations from where the files can be processed by the applicable inbound messages. |
Process EDI messages using AS2 - Outbound |
You can use EDI studio to send EDI messages to the AS2 web app. The AS2 web app processes the data further to the web server of the EDI partner. Set up the Process outbound message queue to process the outbound web service actions as set up for AS2. |
Product receipt |
If you want to use EDI to receive product receipt information from a 3PL warehouse:
|
Purchase acknowledgement |
If you want to use EDI to receive purchase order acknowledgments from a vendor:
|
Purchase ASN |
If you want to use EDI to receive packing slips from a vendor:
|
Purchase confirmation |
If you want to use EDI to receive purchase order confirmations from a vendor:
|
Purchase invoice |
If you want to use EDI to receive purchase invoices from a vendor:
|
Purchase order |
If you want to use EDI to send purchase orders to a vendor:
|
Receipts list |
If you want to use EDI to send receipts lists to a 3PL warehouse:
|
Sales acknowledgement |
If you want to use EDI to send sales order acknowledgments to a customer:
|
Sales ASN |
If you want to use EDI to send sales packing slips to a customer:
|
Sales confirmation |
If you want to use EDI to send sales order confirmations to a customer:
|
Sales invoice |
If you want to use EDI to send sales invoices to a customer:
|
Sales order |
If you want to use EDI to receive sales orders from a customer:
|
Sales order (Delfor) |
If you want to use EDI to receive Delfor sales orders from a customer:
|
Search for document flow: Customer |
To be able to process a message, an applicable document flow and its related setup must exist. The moment the applicable document flow and setup is checked, is defined by inbound messages process and outbound messages process. In the document flow search, the origin of the message plays a key role. The document flow setting on the origin defines which document flows can be searched for.
This diagram shows the document flow search process if the document flow setting of the origin is 'Customer'.
Note: An EDI party can have an EDI group defined. When searching for a document flow, if no document flow exists for the EDI party and origin, a document flow for the EDI group and origin is searched for.
|
Search for document flow: Customer + legal entity |
To be able to process a message, an applicable document flow and its related setup must exist. The moment the applicable document flow and setup is checked, is defined by inbound messages process and outbound messages process. In the document flow search, the origin of the message plays a key role. The document flow setting on the origin defines which document flows can be searched for.
This diagram shows the document flow search process if the document flow setting of the origin is 'Customer + legal entity'.
Note: An EDI party can have an EDI group defined. When searching for a document flow, if no document flow exists for the EDI party and origin, a document flow for the EDI group and origin is searched for.
|
Search for document flow: Vendor |
To be able to process a message, an applicable document flow and its related setup must exist. The moment the applicable document flow and setup is checked, is defined by inbound messages process and outbound messages process. In the document flow search, the origin of the message plays a key role. The document flow setting on the origin defines which document flows can be searched for.
This diagram shows the document flow search process if the document flow setting of the origin is 'Vendor'.
Note: An EDI party can have an EDI group defined. When searching for a document flow, if no document flow exists for the EDI party and origin, a document flow for the EDI group and origin is searched for.
|
Search for document flow: Warehouse |
To be able to process a message, an applicable document flow and its related setup must exist. The moment the applicable document flow and setup is checked, is defined by inbound messages process and outbound messages process. If you exchange EDI messages with 3PL warehouses, in the search for the applicable document flow, the warehouse is the key. The document flow must have the account code 'Warehouse'. So, in this case, the origin is not used. This diagram shows the document flow search process for 3PL warehouse EDI messages. |
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. |
Set up AS2 - Inbound |
You can use EDI studio to receive EDI message files from the AS2 web app. To be able to do so, some specific setup is required. Key in the setup is the inbound definition. To receive EDI messages using the AS2 protocol, first the AS2 web app is run. This app stores the EDI message files in a general storage location. On this general storage location, the inbound definitions are run in recurring mode (Process AS2 inbound queue). During this process, this data is searched for in an EDI message file:
Based on this data, the file is moved to a specific storage location for further processing. From this specific storage location, the file is processed with an inbound message. You can use the AS2 - Inbound process, for example, to import data that must be processed by different messages, based on specific field values. |
Set up AS2 - Outbound |
You can use EDI studio to send EDI messages using the AS2 web app. To be able to do so, some specific setup is required. |
Set up AS2 Key Vault |
When you use the AS2 web app, you need a key vault to set up the secrets and certificates that are required to run the AS2 web app. |
Set up buyer messages document flows |
This flow explains how to set up the document flows for EDI messages that a buyer can send to or receive from a seller. Note: Based on the outbound document flows as defined for a vendor, on the purchase order header, in the EDI section, options are selected. These options indicate which document flows apply to the purchase order. Usually, you do not change these settings. However, if required, you can switch off a document flow for a purchase order. |
Set up document flows |
For each EDI message that you want to send or receive, a document flow must be set up in a specific way. |
Set up EDI for customer |
Before you can exchange EDI messages with a customer, set up:
|
Set up EDI for vendor |
Before you can exchange EDI messages with a vendor, set up:
|
Set up EDI for warehouse |
Before you can exchange EDI messages with a 3PL warehouse, set up:
|
Set up EDI validations |
If you use staging in your EDI process, the received messages are stored in a staging journal. On insert of the message into the staging journal, the applicable journal validations are done.
To define these validations, you set up:
|
Set up seller messages document flows |
This flow explains how to set up the document flows for EDI messages that a seller can send to or receive from a buyer. Note: Based on the outbound document flows as defined for a customer, on the sales order header, in the EDI section, options are selected. These options indicate which document flows apply to the sales order. Usually, you do not change these settings. However, if required, you can switch off a document flow for a sales order. |
Test AS2 inbound definition setup |
If you have set up an inbound definition, you can test it. To test an inbound definition, first make sure a test file is available in the Working folder as defined by the connector of the inbound definition. |
Use EDI tutorial |
To have a quick start with the EDI setup, you can use the EDI tutorials. These tutorials have several pre-defined EDI messages with related setup. The related setup includes, for example: the project, the source and target connectors, and the source and target documents. EDI tutorial projects are available for these purposes:
You can import the EDI tutorials by importing the related projects. |