Preconfiguring Mapping Programs with Operation Mappings

Configure Mappings with One Mapping Program per Direction

1. Create your operation mapping in the ES Builder.

   Note

   You can also create multiple operation mappings for the same pair of operations.

2. Enter the source and target operations that require a mapping of the request message, the response message, the fault message, or all three, in the table of the same name. The following restrictions apply:

   If you want to use the operation mapping in a transformation step in an integration process, you must only specify abstract service interfaces. Furthermore, all objects (integration process, operation mapping, and all objects referenced by the operation mapping) must be in the same software component version. If you want to reference objects from underlying software component versions, you must access the objects from the Basis Objects branch (in the navigation tree or using input help) ( Underlying Software Component Versions ).

3. To import the properties of the operations, choose Read Operations . The table in the lower area displays tab pages for the request message, response message, and if available, for the fault message, for each mode of the operation (either synchronous or asynchronous).

4. To develop an external mapping program, export the XSD schema of the respective request or response message as a ZIP file after you have imported the operations. The zip file can contain multiple schema files that reference each other, for example in a multi-mapping. In this case, the schema with the global message element has the name MainSchema .

5. You have the following options if you want to reference a mapping program for the respective message:

   • Select an existing mapping program from the ES Repository by using input help. If this is a message mapping, the default setting of the input help only displays those message mappings that are found using the source and target message in the ES Repository (in the case of multi-mappings, the first source and target messages are used as the search criteria). However, you can also display any number of message mappings, for example, because you are constructing a mapping from several mapping programs with intermediate instances which have no message types.

   • You can create message mappings directly from the operation mapping. To do this, select the mapping type Message Mapping in the Type column. Position the cursor in the Name column and choose the function Create New Message Mapping in the Mapping Program frame. The ES Builder copies the details of the messages and their occurrence directly from the operation mapping.

     Note

     An operation mapping can only reference mapping programs that belong to the same software component version as the operation mapping, or an underlying software component version. This ensures that the mapping program can be shipped together with the operation mapping (more information: Organizing ESR Content ).

6. Use the following checkboxes to define the basis settings for your mapping programs: Use SAP XML Toolkit , Do Not Resolve XOP Includes , and Read Attachments .

   More information: Operation Mapping Basic Settings

7. Save your operation mapping.

Configure Mappings with Multiple Mapping Programs per Direction

By using an operation mapping, you can also execute multiple mapping programs consecutively for the transformation of a request or response message (this is not possible in the case of mappings for fault messages). In these cases, an operation mapping consists of several steps.

To execute multiple mapping programs for one request or one response sequentially, enter the mapping programs in the table on the corresponding tab page. The steps are executed in the sequence specified (from top to bottom). The result of the mapping program from the previous step is forwarded to the mapping program of the subsequent step.

You do not strictly need to divide up one direction of the whole mapping into different steps. However, this enables all the message formats in one system landscape to be mapped to a central message format, for example. This results in less mapping programs being required because you no longer need to be able to map all the different message formats to each other.