B2B Gateway

Back Next

Custom mappings for EDI message exchange

To send EDI messages to partners, you must create custom mappings for outbound flows. To receive EDI messages from partners, you can optionally create custom mappings for inbound flows.

Custom mappings for inbound EDI messages: You can use custom mappings in inbound EDI message flows to process the interface file from the
B2B Gateway
document store to the backend system. The source of the mappings is the interface file and the target is the backend system. The mappings use a Hierarchy Parser transformation to convert the XML interface file to relational database format and places the data in the backend system.
If you use custom mappings to process the interface file to the backend system,
B2B Gateway
provides end-to-end tracking of inbound messages, from the partner to the backend system. If you use a different method to process the interface file to the backend system,
B2B Gateway
tracks the messages from the partner to
B2B Gateway
and does not track the messages to the backend system.
Custom mappings for outbound EDI messages: Use custom mappings in outbound EDI message flows to process outgoing messages from the backend system to an interface file on the
B2B Gateway
document store. The source of the mappings is the backend system and the target is the
B2B Gateway
connection to the location of the interface file. The mappings use a Hierarchy Builder transformation to convert the data to XML format and places the data on the document store.