Unified Key Mapping 

Purpose

Unified Key Mapping (UKM) provides various interfaces for accessing key mapping.

●     The interface that is closest to the UKM core is the ABAP-OO interface. It provides the entire scope of functions with the greatest granularity. 

●     RFC-enabled function modules wrap parts of the ABAP-OO interface and provide cross-system access to the most important methods.

●     A Java API represents a wrapper for the RFC-enabled function module. This Java API is provided as XI content for SAP Basis. To make it easier to call the Java API from xslt mappings, you can use an xslt include that contains the Java calls.

The following diagram shows the wrapper layers of the UKM:

●     Calls from the same system should be sent directly to the ABAP-OO interface.

●     Calls from external systems must use the RFC modules.

●     You can use the Java API and the xslt includes for key mapping calls from within xslt mappings.

Features

●     UKM offers a simple ABAP-OO interface that supports reading, writing, deleting, and saving mappings as well as their clean-up. There are also wrappers in the form of RFC-enabled function modules for reading, writing and deleting mappings.

●     XI interface mappings (XSLT transformations) can access mappings of the UKM using a Java API. The Java API is stored in SAP Basis as XI content.

●     In the interfaces, a mapping consists of pairs of keys that are stored in the database as a grouped mapping of objects. This means that more than two keys are supported for each mapping group.

●     To identify a key, core component type "Identifier" is fully supported.

●     UKM supports transactional behavior and transaction-dependent buffering.

●     All interfaces are mass-enabled.

●     The UKM does not need any customizing settings.

●     If the are multiple mapping objects in a system, an object can be designated as the client default.

●     UKM can manage multiple independent mapping instances in order to support an intentional separation. For example, you might want a separate instance for each master data object type (business partner, product master). A mapping instance is identified by the mapping context. Each mapping context has its own set of database tables. Approximately 1.5 million different mapping contexts are supported.