Value Mapping

[Former Member]

Any one explain regarding value mapping

thanking you

[GabrielSagaya · Accepted solution]

Value Mapping

*****************

An object can have different representations, depending on the context in which it is used.

Example

**********

For example, the person Mr. Smith has a particular customer number as a customer of mail order company A and has a particular employee number as an employee of company B. Both numbers refer to the same person.

We can use the value mapping function to map different representations of an object to each other. We can save the mapping rules for different objects in a value mapping table.

We can use value mapping in the following areas of SAP Exchange Infrastructure:

· Java mapping

· Message mapping (see Standard Functions)

ValueMapping using the Graphical Mapping Tool

/people/community.user/blog/2007/01/08/valuemapping-using-the-graphical-mapping-tool

Accessing Value Mapping defined in Directory using Java functions

/people/sukumar.natarajan/blog/2006/10/23/accessing-value-mapping-defined-in-directory-using-java-functions

Value Mapping replication

/people/sreekanth.babu2/blog/2005/02/23/value-mapping-replication

[aashish_sinha]

Hi,

Value Mapping

An object can have different representations, depending on the context in which it is used.

For example, the person Mr. Smith has a particular customer number as a customer of mail order company A and has a particular employee number as an employee of company B. Both numbers refer to the same person.

You use the value mapping function to map different representations of an object to each other. You save the mapping rules for different objects in a value mapping table.

You use value mapping in the following areas of SAP Exchange Infrastructure:

• Java mapping

• Message mapping

In SAP Exchange Infrastructure, the representation of an object is defined by an issuing agency and an identification scheme (see Identifiers). The representation of an object is not complete until the agency, identification scheme, and value are known.

You can define value mappings in different value mapping contexts, for example, the Integration Directory or the SAP Solution Manager. Different value mapping contexts are of use when you want to transfer value mappings from another context

You save object representations in a value mapping table.

You have the following options for editing the content of value mapping tables:

· Manual Input using the user interface of the Integration Directory

· Replication from external data sources using a specialist interface

The Value mapping function provides a more specific value transformation.

1. Use the standard function Conversions -> Value mapping to link source and target element

2. Double click to define properties

3. Define access keys for table entries:

a)Value Mapping Context stores information on the origin of data. eg http://sap.com/xi/XI

b)Agency & Schema for sender and receiver messages. Any arbitrary string value can be used

Value Mapping Replication for Mass Data

If you have stored value mappings in external tables, you can replicate this data in the runtime cache (on the Integration Server). To do this, you can use special message interfaces (value-mapping replication interfaces) that allow you to implement both synchronous and asynchronous replication scenarios.

The replication of value mappings is particularly suitable for mass data that you manage in separate tables (such as Excel files or SAP database tables) independent of the Integration Server.

In a replication scenario, the contents of the external value mapping table are read and sent to the Integration Server as an XML message. An inbound interface allows the external data and the data that you previously created using the user interface of the Integration Directory to be stored together in a uniform format.

To avoid overwriting existing value mappings during the replication process, you assign the external data a value mapping context. This needs to be a unique name that identifies that system or application from which the value mappings are taken.

The value mapping context appears in an additional column in the value mapping table. This allows you to differentiate between identical representations of the same object that come from different external data sources.

You cannot display the replicated value mapping data in the Integration Directory user interface since the original runtime data is stored in the application from which the data is copied. The value mappings created in this way using the user interface of the Integration Directory are just one of many possible sources of data.

SAP provides the following objects for the replication of value mappings:

· Value-Mapping Replication Interfaces

They are located in the Integration Repository in the software component SAP BASIS, software component version SAP BASIS 6.40 in the namespace http//sap.com/xi/XI/System.

· Proxy Objects

For the inbound message interfaces, there are inbound proxies on the Integration Server and ABAP outbound proxies in the SAP system in ABAP proxy generation under the software component version SAP Basis 6.40.

Activities

To implement a value-mapping replication scenario, proceed as follows:

1. Register the Java (inbound) proxies.

To do so, call the following URLs in the following order in your Internet browser:

http://

:

/ProxyServer/register?ns=http://sap.com/xi/XI/System&interface=ValueMappingReplication&bean=localejbs/sap.com/com.sap.xi.services/ValueMappingApplication&method=valueMappingReplication (for the asynchronous replication scenario)

http://

:

/ProxyServer/register?ns=http://sap.com/xi/XI/System&interface=ValueMappingReplicationSynchronous&bean=localejbs/sap.com/com.sap.xi.services/ValueMappingApplicationSynchronous&method=valueMappingReplicationSynchronous (for the synchronous replication scenario)

You only need to perform this step once (for each installation).

2. Application programming

The ABAP program must perform the following tasks:

Read the value mapping data from the external table

Call the outbound proxy used to transfer the data to a message, which is then sent to the Integration Server

3. Configuration of the replication scenario in the Integration Directory

This involves creating all the configuration objects you need to execute the scenario successfully. One special aspect of the value-mapping replication scenario is that the receiver is predefined (it must be on the Integration Server). The sender, however, is not predefined in the replication scenario and can be defined to meet your individual requirements.

For example, you can use the shipped ABAP proxies.

In the case of the receiver communication channel, choose the adapter type XI. Ensure that you configure a channel for the Java proxy receiver in this case.

Enter the path prefix /MessagingSystem/receive/JPR/XI for this purpose.

Regards

Aashish Sinha

PS : reward points if helpful