on 09-15-2014 2:48 PM
Hello,
There is a query from my customer about the language support that SAP Screen Personas provide.
I tried to test the scenario by creating a demo flavor in English and then Creating OTR objects from Personas Administration Tcode.
I then maintained the translations in chinese to the new concepts that are created on SOTR_EDIT.
Now, when I again reload the Personas Flavor and select the chinese language, the particular text is still displayed in english.
I even tried adding and removing the optional parameter Sap.Language from the SPRO configurations but that too didnt help.
Am I missing something or is there some other way to maintain the translations?
Thanks,
Best Regards,
Mahip Singh Saluja.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Those alias names don't seem to be longer than 50 characters in the above screen shot, so my guess would be that the OTR object creation doesn't like some characters in the aliases. I checked the admin transaction code and there is some pattern matching performed when the alias name is determined, but I'm not sure what's the reason behind it. This happens in program /PERSOS/ADMIN_UI_F01, subroutine PREPARE_OTR_ALIAS_DATA.
I wasn't aware of a restriction regarding this so I'm afraid I cannot offer a quick solution to the problem. I think an OSS incident would be the way to go here...
One thing though: it appears the aliases are related to some Z fields in IW21? Are these a part of a custom enhancement? If yes, any way to change those field names so they don't cause issues in Personas translation?
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.