Start of Content Area

Component documentation Mapping Messages to Each Other Using Mapping Objects  Locate the document in its SAP Library structure

Purpose

Mapping maps a source structure to a target structure. There are various reasons why this may be necessary:

      A business partner expects other technical field names or another structure for transferring data.

      For technical reasons. For example, a receiver RFC adapter connected to the PCK expects messages from the PCK in the format that it can understand, RFC XML. It then creates an RFC call in a system assigned to it.

Integration

The mappings created in the PCK are specified during configuration as part of the receiver agreement. The PCK transforms your message at runtime, in accordance with the saved mappings. Ideally, a mapping is not necessary because the source and target structure of a message match.

For more information: Receiver Agreement

For more information about mapping objects in the Enterprise Services Repository, see: Mapping Objects.

Features

      The PCK supports the development of message mappings using an integrated graphical editor. Java classes are generated for use at runtime from the graphical description. You also have the option of enhancing the standard functions with user-defined functions.

For more information: Message Mappings

      The PCK supports the import of XSLT or Java mapping as an archive. If, for example, XSLT mappings already exist or are to be developed using third-party tools, you can use the import function to import such mapping programs to the PCK.

These mapping programs are executed on AS Java.

For more information: Importing XSLT or Java Mappings

       XSLT (eXtensible Stylesheet Language Transformations)

You use XSLT to convert an XML document to another document. This is achieved by using XSLT commands to search for tags in the source document and replacing them with other tags or values in the target document. You can also call a Java method in an XSLT program.

       Java program

The message is transferred to a Java program as an inbound stream and can be imported using any parser (for example, SAX or DOM). The modified message is then transferred to an outbound stream.

A Java program can also be a help program that in turn is used in another Java program or in self-defined functions of a message mapping.

If, for example, XSLT mappings already exist or are to be developed using third-party tools, you can import the mapping programs for use in your A2A or B2B scenario.

 

End of Content Area