Operation Mapping

Use

You use an operation mapping to relate an outbound service interface operation with an inbound service interface operation. You can also relate IDoc and RFC interfaces with entities of the same type or with service interface operations. This is illustrated in the following figure:

Figure 1: Assigning Service Interface Operations with an Operation Mapping

You define the assignment of the operations related to each other in an operation mapping, whereas in a mapping program you define the detailed transformation rules for the transformation of a source structure (representing the message sent by the outbound operation) into a target structure (representing the message received by the inbound operation).

The number of mapping programs or transformation rules you need to define for an operation mapping depends on the communication mode:

Synchronous communication

A synchronous operation (see section Defining Interface Objects) refers to a request, a response, and in some cases a fault message. Therefore, in general you have to define a mapping program for both request and response messages. If fault messages are used, you have to define an additional mapping program for the fault message.
Asynchronous communication

You only need one mapping program.

An operation mapping encapsulates the used mapping program (either defined graphically by a message mapping or contained in an imported archive).