Value Mapping - Best Strategy

[Former Member]

Hi,

There are several strategies fo Value mapping

1) Fixed values (e.g. constants in Graphical mapping)

2) Value mapping on Jave stack via VM tables

3) SAP tables created in SE11 and RFC the data from calls from the Java stack

Surely the best strategy is 3) even though it is not the most efficient purely for the fact to have easy visibility of your integration data. e.g. via SM30 or custom transaction to view integration value mappings. If anyone has a different view on this I would to hear from them or possibly suggest an alternative.

[Former Member]

The best way always depends upon your requirement, so we can't say strategy 3 is best for everyone.

For example: Fixed value table can be used for small conversion but and every time you add new value to this table you need to transport the mapping.

Creating Value mapping tables in Integration Directory is best option in general and also easy to maintain. If you are going to fetch records from R3 table then strategy 3 is best.

[udo_martens]

Hi,

the best strategy is dependend from your requirements:

- Fixed values could be used if the values never change

- Value Mapping with groups in IB Directory is usually the standard

- If you want to use authorizations of ERP backend you can go for Value Mapping Replication (more efforts).

- You can use as well included textfiles, lookups and what else can store data...

Regards,

Udo