Mapping Objects (Enhanced) 

Use

General

●      Parameterized Mapping Programs

You can now work with parameters - whose values are not defined until configuration time - in message mappings, Java mapping programs, and XSLT mapping programs. In mapping lookups, to define the communication channel to be used in the Integration Directory you can now use the new parameter type Channel.

More information: Parameterized Mapping Programs

●      Test Environment

In lower releases, you were able to test mapping programs if you had the authorization to display mapping objects in the Enterprise Services Repository. This authorization is now no longer sufficient.

More information: Test Environment for Interface Mappings, Test Environment

Message Mappings

●      Function Libraries

In lower releases, you were able to save and manage user-defined functions as part of one message mapping only. You can now create function libraries independently of specific message mappings, and can use the functions you define in them in multiple message mappings.

More information: Function Libraries

●      Standard Functions for Mapping Lookups

In lower releases, you could only use mapping lookups in message mappings if you used the mapping-lookup-API in Java within a user-defined function. The mapping editor now has the standard functions JDBC Lookup and RFC Lookup for lookups involving the JDBC or RFC adapter.

More information: Defining JDBC Lookups Graphically, Defining RFC Lookups Graphically.

●      Variables

In the target structure in the mapping editor, you can now define a graphical variable that you assign a value to at runtime by using a normal target-field mapping. You can then use this value in the scope of the variable when you apply the variable in other target-field mappings; doing so will help to simplify the target-field mappings concerned.

More information: Variables in the Target Structure.

●      Filter (Usability)

A filter is now available in both the structure overview and the test environment in the mapping editor. The filter enables you to display only those fields in the respective structure that you require for your work on the message mapping.

More information: Structure Overview.

●      Precision of Standard Functions

The arithmetic standard functions of a message mapping perform calculations with the precision of the Java data type float. The Java runtime converts values of type float to dyadic format before the calculation, calculates the result, and converts this result back to decimal format. The conversion may result in decimal places in the dyadic format that are periodically repeated and then automatically cut off. In the decimal system, this can result in inaccurate results (example: 2.11 + 22.11 = 24.220001).

Until now you could not change the precision of the calculations. To prevent the above-mentioned inaccuracies in the calculations, you can now perform the calculation for a selection of standard functions in the decimal system.

For more information: Standard Functions or SAP Note 958486.

XSLT Mappings

SAP will only support the SAP XML Toolkit for SAP NetWeaver Process Integration 7.1 and the next release of SAP NetWeaver. In SAP NetWeaver Process Integration 7.1 and higher you can work with the Java Development Kit (JDK) 5, which is a functionally superior tool to the SAP XML Toolkit. Both runtimes will be available during the transition phase.

From SAP NetWeaver Process Integration 7.1. you can only use the Java Development Kit in the PCK.

More information: XSLT Mapping

Java Mappings

A new API is available for Java mappings. The previous mapping API still exists but will not be developed further (parameterized Java mapping programs are only possible with the new mapping API, for example).

More information: Java Mapping