Data Integration mappings for EDI X12 and EDIFACT messages
Data Integration
mappings for EDI X12 and EDIFACT messages
B2B Gateway
uses pre-packaged, EDI processing mappings to handle inbound and outbound EDI X12 and EDIFACT messages based on the flows that you assign to the partner. The EDI processing mappings handle the connectivity between the partner and the
B2B Gateway
document store.
You can define the following flows:
Inbound flow
You can use custom mappings to process the interface file that the
B2B Gateway
EDI processing mapping generates and places on the
B2B Gateway
document store to the backend system.
You can define a single process-to-backend mapping to process all interface files, a mapping for each type of file that you want to process, or both mapping types. When an inbound process runs,
B2B Gateway
first runs the process-to-backend mappings that are defined for specific message types, and then it runs the process-to-backend mapping that is defined for the inbound flow of the partner.
Outbound flow
You can define custom backend processing mappings to extract and process the data to send to the partner from the backend system to an interface file on the
B2B Gateway
document store. You can define a single process-from-backend mapping to process all the messages to the interface file, a mapping for each type of file that you want to process, or both mapping types.
When an outbound process runs,
B2B Gateway
first runs the process-from-backend mappings that are defined for specific message types, and then it runs the process-from-backend mapping that is defined for the outbound flow of the partner. The
B2B Gateway
EDI processing mapping reads the messages from the
B2B Gateway
document store.
For both inbound and outbound flows, define each message type in one mapping only. If you define the same message type in both a message-specific backend processing mapping and in the flow's backend processing mapping,
B2B Gateway
might run messages of that message type twice. For example, if you define a process-from-backend mapping for the
810 Invoice
message type for a customer, and
810 Invoice
is also defined in the process-from-backend mapping that is defined for the outbound flow of the customer,