A mapping can process a single message type or multiple message types. When you create a partner, you can select a mapping that contains a single message type when you add the message type for the partner. You can select a mapping that includes multiple message types when you define the outbound flow for the partner. To use mappings that contain a single message type you must also create a message discovery mapping and assign it to the outbound flow of the partner. For more information, see Creating a message discovery mapping for outbound EDI message flows.

When you create the mapping in

Data Integration

you select your backend system as the source. You add two source transformations to the mapping, a transformation for the master source and a transformation for the source that contains the message details. For example, add a source that contain the order as the master source and a details source that contains the order details.

If you define multiple interchange IDs of the same type for the partner that uses the mapping, define the interchange IDs to use in outbound flows in the source that contains the message details and map it to the interchange ID fields in the target transformations. You can map one interchange production ID and one interchange test ID. You must map at lease one interchange ID in the mapping.

If information on multiple message types appears in the same table, you add a filter for each message type. You then add and configure a Hierarchy Builder transformation for each message type, and, for each message type, add the

B2B Gateway

interface file as the target.

After you add all the required elements to the mapping save and validate the mapping.