The solutinons to value mapping during exchanging

[Former Member]

Howdy!

Here's the general senario:

We got a 3rd party system named KS and a local R3 system called RS. We have a interface that send invoice data from KS to RS. But the customer number from KS is different from RS customer number, so we need not noly the structure/format mapping but also the value mapping during exchanging procedure.

Anyone got a proper solution to this problem?

3Q!

[former_member189558 · Accepted solution]

Hi Kee,

You need to maintain the values in a lookup database.

Fix up ur lookup strategy and a database for that. Maintain the cross reference table there.

Call the lookup from the mapping. You need to achieve this using a UDF and Java Code.

Thanks,

Himadxri

[Former Member]

3Q all!

It's very useful.

[MichalKrawczyk]

hi,

1. 2 problems with value mappings:

- if you don't use value mapping replication you will have to add all of them

(one by one) to a table in directory - very time consuming

- you cannot have two records with the same value pointing to one target value !

(so if in one system two numbers will mean one number in SAP this will not work)

2. so try considering other forms of lookups

- lookups from user functions - message mappings

- lookups from ABAP - abap mappings

- lookups from ABAP - XSLT on ABAP stack

Regards,

michal

[STALANKI]

Sorry Kee ...link z here /people/sravya.talanki2/blog/2006/12/26/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-ii ..is the right one.

[STALANKI]

Check the value mapping and mapping lookups in this blog.

/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi

Iam sure you will enjoy it.