Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

From MDMP to Unicode. Text input and language confguration changes?

Former Member
0 Kudos

Hi!

We just Upgraded from 4.7 MDMP to ECC6 Unicode system.

As we know in MDMP system the rules are very strict how to enter non-english language data. (Logon language, SAPgui codepage and frontend all have to support the desired language.)

Now with out new Unicode ECC6 system we have a couple of loose ends we would like to close:

1. Can we now just logon with EN and input/edit Asian or Cyrillic characters in any field safely? Or do we still need to login with for example ZH to input Chinese?

2. If we use SAPgui 7.10 we assume everyone must have I18N functionalities enabled?

3. What actions are needed if we want to add a language for a) description translations but NOT as a logon language? b) as a logon language?

4. Is system restart still needed if we want to add a new language with SMLT + RSCPINST?

5. If we still use a logon check user-exit what things are worthwhile to check there in regards of avoiding data corruption?

6. Do we still need to maintain address versions ("Address Layout Key" in transaction OY01) for each country and have the coding in the user-exit ZXSADU01 as described in the Note 316331?

Thank you so much in advance!

br,

OM

1 ACCEPTED SOLUTION

nils_buerckel
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

1. Technically you can logon in EN and maintain Chinese - there is no technical restriction. However in some application areas (for example the SE63) the system behaves as before - it tells you to use chinese in order to translate it.

2. The recommendation is to enable the I18N flag globally for all frontends. However if it is not set, then the system activates it automatically once logging on to a Unicode system.

3.

a) Minimum would be to add the language via RSCPINST

b) Please have a look at the language installation docu - the steps are basically the same as in Non-Unicode (+ RSCPINST)

4. Yes - for a logon language you still have to maintain zcsa/installed_languages - and you have to restart the system before it is active.

5. I have not heard of any customer who is using the user exit in a Unicode system.

6. Address versions are mainly used for printing. In this sense, the usage is independent of Unicode - so yes, you will likely still need to use address versions.

Best regards,

Nils Buerckel

SAP AG

3 REPLIES 3

nils_buerckel
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

1. Technically you can logon in EN and maintain Chinese - there is no technical restriction. However in some application areas (for example the SE63) the system behaves as before - it tells you to use chinese in order to translate it.

2. The recommendation is to enable the I18N flag globally for all frontends. However if it is not set, then the system activates it automatically once logging on to a Unicode system.

3.

a) Minimum would be to add the language via RSCPINST

b) Please have a look at the language installation docu - the steps are basically the same as in Non-Unicode (+ RSCPINST)

4. Yes - for a logon language you still have to maintain zcsa/installed_languages - and you have to restart the system before it is active.

5. I have not heard of any customer who is using the user exit in a Unicode system.

6. Address versions are mainly used for printing. In this sense, the usage is independent of Unicode - so yes, you will likely still need to use address versions.

Best regards,

Nils Buerckel

SAP AG

0 Kudos

Thank you Nils!

These have helped a lot already.

Just one bit more about the question 5...

I understand that the technical checks are no longer needed in the logon user-exit, like the language vs. codepage check since every language now uses the same codepage.

But how can we otherwise block users from logging in with for example DE which is installed by default in all SAP systems? I guess for this we could still use the authorization roles for our supported languages and check them in the user-exit.

nils_buerckel
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

if you want to deactivate the logon in DE completely, I would recommend to delete D from zcsa/installed_languages parameter.

However if you want to allow the logon for some users and block it for others, the logon user exit is still a possibility to do it.

Best regards,

Nils