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.
Inbound messages process
For inbound messages, the process that triggers the document flow search, has these steps:
A message is run.
The message checks if an EDI message file exists in the specified location.
If a file exists, the mapping for the BisEdiHistory table is triggered.
The BisEdiHistory table gets and analyzes the data from the file.
With this data, the BisEdiHistory table checks if applicable setup with a document flow exists to be able to process the data.
If so, the message is processed. If not, an error is given.
Outbound messages processes
For outbound messages, the document flow is searched for twice.
When a record is to be added to the Outbound message queue, the document flow is searched for. The process has these steps:
A record is to be added to the Outbound message queue (due to a journal posting or sales acknowledgement).
The mapping for the BisEdiHistory table is triggered.
The BisEdiHistory table gets and analyzes the record data.
With this data, the BisEdiHistory table checks if a relevant document flow exists.
If so, the related message is linked to the Outbound message queue record. If not, an error is given.
When a message is run by the Outbound message queue, the applicable document flow is searched for. The process has these steps:
A message is run by the outbound message queue.
The message triggers the mapping for the BisEdiHistory table.
The BisEdiHistory table gets and analyzes the data from the related record.
With this data, the BisEdiHistory table checks if applicable setup with a document flow exists to be able to process the data.
If so, the message is processed. If not, an error is given.
Document flow and origin
For EDI exchange with customers or vendors, the document flow setting on the origin defines which document flows can be searched for:
Customer document flows.
Customer and legal entity document flows.
Vendor document flows.
For EDI exchange with 3PL warehouse, the warehouse is the key to search the applicable document flow. So, in this case, the origin is not used.
The origin plays a role in several key elements in the process of checking the relevant setup:
In each message, the origin is set.
In each record in the BisEdiHistory table.
In each EDI staging journal.
In each purchase order and sales order.
For each EDI party, you can define the applicable origin.
For each document flow, you can define the applicable origin.
Note: The origin can also be set as empty in the message. Accordingly, the search for a document flow only considers party setups and document flows with origin empty as well.
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.
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.
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.
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.
