Value Mapping Replication

Posted on Apr 7, 2010 at 06.30 PM - Kuala Lumpur, Malaysia

To replicate value mapping data from other applications in the runtime cache in the Integration server, you can use server interface "value mapping replication interfaces", which came as standard SAP interfaces. The interfaces enable us to realize both synchronous and asynchronous replication scenarios. There 4 interface in total: two synchronous and two asynchronous, or two outbound and two inbound. There are inbound proxies in the Java stack and outbound proxies in the ABAP stack.

The value mapping replication interfaces are included by SAP, since component version SAP BASIS 6.40, under namespace http//sap.com/xi/XI/System.

Configuration for Value Mapping Replication

1. Create communication component to represent PI as receiver. Don't forget to add in the receiver interface as mentioned above.

2. Create communication channel (XI Receiver) with URL points to http://<pi-host>:<java-port>/MessagingSystem/receiver/JPR/XI

3. Register Java Inbound Proxy. Check SAP help link below: http://help.sap.com/saphelp_nw04/helpdata/en/2a/9d2891cc976549a9ad9f81e9b8db25/content.htm

4. Create necessary routing configuration

5. If the sender is an ABAP system, we can use the ABAP outbound interfaces which are already implemented as ABAP proxies to transfer the data. We just have to create an ABAP program to pick up necessary values and populate the proxy structure of ValueMappingReplication interface, and call this proxy method as in any other outbound ABAP proxy interface.

Notes: We can also use the same communication component created in step 1 to represent the sender if necessary.

You can check the value mapping cache from runtime workbench as depicted below:

To improve is maintainability, we can:

1) Create a custom table in ABAP stack of the backend system which match with the message type of ValueMappingReplication interface

2) Create a table maintenance screen and transaction if necessary

3) Create an ABAP program to pick any new or changed values from the custom table,

4) Populate the value to the related proxy parameters

5) Execute the proxy and update the runtime cache of the integration

If you still don't get the idea, you can go through these articles in SDN which show you step by step implementation of mass value mapping replication: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e07dd2ae-f783-2c10-9aa6-ca69f67dd20f?QuickLink=index&overridelayout=true or http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00ee347e-aabb-2a10-b298-d15a1ebf43c5?QuickLink=index&overridelayout=true

Life is beautiful! Let's make it meaningful and colorful!