on 09-11-2007 11:44 AM
Hi All,
I Want to Know the Limitations in Value Mapping.
Please Let me Know .
Regards
Vamsi
Hello Vamsi
Limitations.
1. It can be a ongoing process.
for example
suppose application1 represents tax code 1 as TX1 and application2 represents tax code 1 as TAX1 and we had used value mapping in this case.
This can be a ongoing process suppose if you need to add new tax code or change the tax code.
2.suppose you have a huge number of value mapping shifting from quality to production is a pain. (i am not sure about other easy method)
3.Identification of fields for value mapping in big implementation is also difficult.
4.It consumes certain time
Regards
Ramesh P
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For problems with value mapping, see
SAP Note 1061811
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Value mapping is cumbersome and difficult to maintain for any person not used to XI and this is one area we have avoided and found easier, more user-friendly ways of doing it.
If a business related person wants to control this, then they are more likely to be more familiar with SAP GUI than XI so I would recommend storing any mapping requirements in the relevant application and translate before sending to XI.
This also has the advantage of cutting down on the value mapping overhead in XI although this is likely to be negligable.
Cheers
Colin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.