Using the ID Mapping Framework with an Integration Server 

Purpose

You want to exchange messages between un-harmonized systems, via an integration server. You have saved identical customizing in different systems, under different IDs, in your system landscape. You want to exchange messages which refer to customizing with different IDs, but which identify the same entity, between systems, in an Integration Server. You require ID Mapping for this.

ID Mapping allows you to exchange messages between un-harmonized systems, without having to reconcile the IDs in customizing and all applications in master data.

How the integration server uses the ID Mapping Framework information to exchange data, is described below. For further information about setting-up the ID Mapping Framework, see Setting-Up the Customizing ID Mapping Framework.

Process Flow

Data exchange via the integration server with ID mapping

...

       1.      System A sends a message which refers to customizing, to the integration server to pass on to system B. The message contains customizing IDs, which refer to entities in customizing.

       2.      The integration server translates the message into an appropriate format for the receiving system B. At the same time, the Integration Server converts the customizing IDs for the receiving system, with the ID mapping.

       3.      The integration server forwards the message to system B.

       4.      System B receives and processes the message further. As the customizing ID has been converted correctly by the integration server, system B can also read and interpret the customizing reference in the message correctly.

Example

...

       1.      An SAP R/3 development system sends a request, which refers to customizing for marital status, to the integration server, for forwarding to an SAP CRM development system.

       2.      The integration server converts the request into a suitable format for the receiving SAP CRM system. At the same time, the integration server converts the customizing IDs for marital status into suitable IDs for the SAP CRM system, with the ID mapping.

       3.      The integration server forwards the message to the SAP CRM system.

       4.      The SAP CRM system receives and processes the message further. As the marital status customizing ID has been converted correctly by the integration server, the SAP CRM system can also read and interpret the marital status reference in the request correctly.