Can ValueMapping Table return multiple Values in Mapping

[sridharreddy_kondam]

Hi All,

We are analysing which Lookup to be used. Either Value Mapping Table Replication from ECC or RFC LookUp to ECC.

We need to get list of stores from the ECC table to PI, and then compare these stores with data sent from source file and then process within PI for the stores that are missing.

Our Onshore team suggested to use Value Mapping Table Replication .

But if we use Value mapping Table replication, Can The Value mapping table return Multiple stores at a time?

And from the source we will not be passing any data to value mappping table, we only need no of stores from the ECC table.

Is using Value mapping Table Replica currectfor the above scenario?

Can any one suggest?

Thanks and Regards,

Sridhar

[former_member854360 · Accepted solution]

Value mapping will always have a Key and value pair.

Key Value

1 A

2 C

4 J

So if you pass Key to valueMapping then it will return the value for that key

Suppose you pass 1 to valuemapping then it will return A

if 2 then C

If 4 then J

--->But if we use Value mapping Table replication, Can The Value mapping table return Multiple stores at a time?

Value mapping only can return a single value for every input.

If your requirement is to have multiple output for a single input

Suppiose: input is one region output you need all the stores of that region.

Then its not possible with value mappunig . Then you can consider RFC lookup.

[sridharreddy_kondam · Accepted solution]

Hi Debhashish,

The one you said is the same opinion i had in my mind(RFC Lookup only works). Will relook once again and update, so that i can confirm to the onshore team.

Thanks and Regards,

Sridhar

[Former Member]

Hi Sridhar,

in value mapping to allow to have two same entries, you should add a prefix, in both column (like source/target)... because Value Mapping works in both sides: source -> target AND target -> source.

and then in your mapping, you could add a prefix before to call the value mapping and you should move it after the call.

Constrainct: your prefix has to have a predefined numbers of characters (like ZTOTO_)

Example:

A <-> 123

B <-> 456

C <-> 456 => same value => issue with a Value Mapping

with prefix (solution 1):

A <-> z001_123

B <-> z001_456

C <-> z002_456 => not the same value => Value Mapping happy !

with prefix (solution 2):

z001_A <-> z001_123

z002_B <-> z001_456

z002_C <-> z002_456 => not the same value => Value Mapping happy !

This tips is interesting in some case, like to externalise a constant, to avoid to write in it in MM, but to have it a Value Mapping, like for instance an email address. And with a prefix equals to your unique DevID for instance.

But in the case of an conversion table, maybe this tips is too limited.

Regards

Mickael

[Former Member]

Hi Sridhar,

The concept of Value mapping has been described clearly by Debashish. In addition to what Debashish has written above, i would like to add a few points.

You can create a value mapping table like the following:

KEY -

---

> VALUE

A -

---

> VALUE1#VALUE2#VALUE3

So when you query for A, you will get the multiple values seperated by a delimiter "#". Now, through a simple java code, you can seperate these values and use each value as is required in your scenario.

Hope this helps.

Regards, Gaurav.