When an outbound process starts,

B2B Gateway

first runs the custom process from the backend mapping that you defined in the partner definition. The output of the mapping should be interface files that include the messages to send to your partners. The mapping places the files on

B2B Gateway

.

B2B Gateway

uses the pre-packaged, EDI processing mapping to read the interface files, and then enriches the data in the interface file with the partner metadata and creates valid EDI messages.

If you assigned values to mapping parameters during partner configuration,

B2B Gateway

uses the values in the mapping flow.

The mapping source and target details are based on the partner definition metadata. The source of the mapping is the interface files, and the target of the mapping is the location where to send the messages.