Show TOC

Procedure documentationCreating Operation Mapping Locate this document in the navigation structure

 

You use this procedure to create operation mapping, which specifies the corresponding mapping programs for request, response, or fault messages for a selected pair of operations. An operation mapping establishes the connection between source and target operation from service interfaces of sender and receiver systems, respectively. Selecting the appropriate operation mapping at configuration time helps you to execute the corresponding mapping program at runtime.

Prerequisites

  • You have opened the Enterprise Services Browser view in SAP NetWeaver Developer Studio.

  • You have identified the operations for mapping.

Procedure

1. Define Basic Data

  1. From the context menu of software component version, namespace, or folder, choose   New   Operation Mapping  .

  2. In the Create Operation Mapping window, enter a name for the operation mapping object.

  3. Choose Browse to select the required namespace or folder.

  4. Choose Finish.

  5. Select an existing change list or choose New to create a new change list.

  6. Choose OK.

2. Define Operation

  1. To add source operation to this operation mapping, in the Operation Definition section, choose Browse to select the source software component version.

  2. In the Source Operations section, choose Add.

  3. In the Select Operation Type window, select the required operation type, external definition, RFC or IDOC.

  4. Choose OK.

  5. In the table, select the required value from the Occurrence dropdown list box.

  6. If you want to use the multi-mapping functionality, add more operations by repeating steps 3 through 5.

    Note Note

    By using multi-mapping in an operation mapping, you can perform several mapping programs for the transformation of a request or response message in a series. For more information, see Multi-Mappings.

    End of the note.

  7. To add the target operations to this operation mapping, in the Target Operation section, choose

    Add.

  8. Repeat steps 3 through 6, in the Target Operation section.

3. Define Parameters

  1. In the Parameters section, choose Add.

    Note Note

    Using parameters to transfer values increases scope of reusability for a mapping program.

    You define parameters in operation mapping in order to connect with the parameters defined in message mapping.

    End of the note.

  2. If you want to change the default values, then click the individual column cells to change the values.

    1. If you want, change the default name by manually entering a name for the parameter.

    2. Choose a category based on the explanation below:

      Category

      Use

      Simple Type

      Transfer a scalable value.

      Adapter

      Select an adapter type for programming a mapping lookup.

    3. In the Type column, select from the drop down options depending on category chosen in the above step.

    4. In the Parameter column, select the type from the drop down option:

      Category

      Use

      Import

      Transfer values to mapping program before its execution. If you want, you can specify constants beforehand during binding.

      Export

      Transfer values of the mapping program after its execution.

    Note Note

    • If you have not declared parameters in message mapping, then it is not necessary to declare parameters in operation mapping.

    • You can assign values directly to certain type of message mapping parameters during binding of message mapping parameters (Procedure for binding of parameters is explained in the next section of Defining Operation for Mappings).

    • For more information on usage of parameters in mapping programs, see Parameterized Mapping Programs .

    End of the note.
4. Define Operation for Mappings

  1. To map input messages, proceed as follows:

    1. In the Definition tab page, double-click the target input node.

    2. In the Mapping Programs window, choose Add.

    3. In the Type column, select the desired type of message mapping program from the drop down list.

    4. In the Name column, click the button at the right.

    5. In the Select mapping program window select the message mapping program.

      Note Note

      • You can use the filters to match mapping programs with selected source and target message type.

      • In case of multi-mapping, the first source and target are used as search criteria

      End of the note.

    6. Click OK.

    Note Note

    Output and Fault are visible depending on the mode and number of selected operations at source and target.

    End of the note.

  2. To map output messages, proceed as follows:

    1. Double-click the target Output node.

    2. In the Mapping Programs window, choose Add.

    3. In the Type column, select the desired type of message mapping program from the drop down list.

    4. Click on the button at the right, in the Name column.

    5. In the Select mapping program window, select the message mapping program.

      Note Note

      • You can use the filters to match mapping programs with selected source and target message type.

      • In case of multi-mapping, the first source and target are used as search criteria

      End of the note.

    6. Click OK.

  3. To map fault messages, proceed as follows:

    1. Drag and drop fault message type from source to the fault message type under the Fault node to do the mapping.

    2. Double-click on the target Fault node.

    3. In the Mapping Programs window, choose Add.

    4. In the Type column, select the desired type of message mapping program from the drop down list.

    5. Click on the button at the right, in the Name column.

    6. In the Select mapping program window, select the message mapping program.

      Note Note

      • You can use the filters to match mapping programs with selected source and target message type.

      • In case of multi-mapping, the first source and target are used as search criteria

      End of the note.

    7. Click OK.

  4. To bind the message mapping parameters with the operation mapping parameters, proceed as follows:

    1. In the Mapping Programs window select the mapping program for which the parameter binding needs to be done.

    2. Click Binding button.

    3. In the Binding for Mapping Program window, in the Binding column, select the parameters defined in operation mapping from the drop down list.

      Note Note

      You can also enter values manually for parameters that are of Category String and Integer type.

      End of the note.
5. Assign Documentation to Operation Mapping

  1. If you want to add internal documentation, in the Documentation section, choose Edit Documentation link.

    Note Note

    • This field is not available if you have selected the Use External Documentation check box while defining the software component version.

    • In case, you have selected the Use External Documentation check box, you can view the external document by selecting View. This option is useful if documentation about the object exists in SAP Solution Composer.

    End of the note.

  2. In the Internal Documentation window, choose the Edit Documentation tab page.

  3. Enter the content.

  4. Choose OK.

    Note Note

    In case internal documentation is assigned to the object, you can view it in Web browser, by selecting View Documentation.

    End of the note.
6. Setting the advance options to define an initialization for an operation mapping

  1. In the Advanced Options section, select the appropriate option in accordance with the use given below:

    Option

    Use

    Use SAP XML Toolkit

    Specifies whether the SAP XML Toolkit is to be used for executing pre-configured XSLT programs. Only select Use SAP XML Toolkit if you reference an existing XSLT mapping program that does not run with JDK 5. SAP recommends that you no longer use the SAP XML Toolkit for new XSLT mapping programs.

    Do Not Resolve XOP Includes

    If the data structure of a message to be processed in an operation mapping contains modeled binary data, the Web service runtime may extract this binary data and create a MIME attachment (MTOM optimization) before the message is sent. The binary data encoded in xsd:base64Binary is then replaced by a <xop:include> statement.

    Note Note

    • If you select this option, the mapping runtime assumes that the pre-configured mapping programs in the operation mapping are still executable despite this replacement.

    • If you do not select this option, the mapping runtime reinserts the binary data in the message payload before the mapping program is executed (the reference set by <xop:include> is resolved).

    End of the note.

    Read Attachments

    Mapping programs are executed in the Java part of SAP Application Server. Since the Integration Server is in the ABAP part of SAP Application Server, before a mapping program can access a message the message must first be sent to the Java part.

    If you do not select this option, the mapping runtime only transfers the message payload to the Java part (without any attachments). If you select this option, the attachments are transferred to the Java part in addition to the payload.