Interface
Mappings 
Interface mappings register your mapping program for an interface pair in the Integration Repository.
The interfaces that you want to connect using a mapping must already be saved in the Integration Repository.

If the interface cannot be imported or cannot be created in the Integration Repository (in the case of an external adapter, for example), you must enter the interface names manually. However, it is not possible to check the technical name.
Furthermore, all the mappings that you want to use must already be saved in the Integration Repository.
...
1. Create an interface mapping on the design maintenance screen of the Integration Builder (also see: Creating a New Object).

You can also create multiple interface mappings for the same interface pair.
2. Enter the outbound and inbound interfaces that require a mapping of the request message, the response message, the fault message, or all three.
3. To import the properties of the interfaces, choose Read Interfaces. The Mapping Program table displays the lines for the request message, response message, and if available, for the fault message, for each mode of the interfaces (either synchronous or asynchronous).
4.
In the Mapping Program column, select a
mapping category (message mapping, XSL or Java) using the search help
(
). In the subsequent window, select the
mapping program for the respective message type (request, response, or
fault).

You can select mapping programs for an interface mapping that have the same namespace and the same software component version as the interface mapping.This ensures that the mapping program can be shipped together with the interface mapping (see:Software Logistics).
5. It is possible to execute multiple mapping programs in succession for requests and responses.
¡
To insert an
additional line for a mapping program, choose
.
¡
To delete the
registration for a mapping program, choose
.

At runtime, the mapping programs are executed from top to bottom.
6. Save the interface mapping.