Unified Key Mapping ServiceLocate this document in the navigation structure

Purpose

The Unified Key Mapping Service (UKMS) provides a number of interfaces for accessing key mapping.

  • The interface that is closest to the UKMS core is the ABAP-OO interface. It offers the entire scope of functions and 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 to SAP Basis as XI content. 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 figure shows the wrapper layers of the UKMS:

  • Calls from the same system should be sent directly to the ABAP-OO interface.
  • Calls from external systems must use the RFC modules.
  • The Java API can be used for key mapping calls made from within XSLT mappings. Accesses to them should be wrapped with XSLT includes.
Features
  • UKMS 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 UKMS 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.
  • UKMS fully supports core component type "Identifier" for identifying keys.
  • UKMS supports transactional behavior and transaction-dependent buffering.
  • All interfaces are mass-enabled.
  • UKMS does not need any settings in Customizing.
  • If there are multiple mapping objects in a system, you can designate one object as the client default.
  • UKMS can manage multiple independent mapping instances in order to support an intentional separation. For example, you 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.