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: 

Wrong text in ADRC and LFA1 table after Unicode conversion

Former Member
0 Kudos

Hello,

We are doing MDMP to Unicode on SAP 4.7 system.

In post unicode activities,we had corrected the garbage characters in

table ADRC

by converting to target langauage ZH using SUMG t-code.

Condition used for addind table ADRC in SUMG is LANGU ='1' and

LANGU_CREA = 'EN'

But after converting and saving the data,most of the records have

incorrect character in word.

and text field of search term/company name/city in table LFA1 are also

wrong in correspond field in table ADRC.

Thanks

Harshavardhan

1 ACCEPTED SOLUTION

nils_buerckel
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Harshavardhan,

problem is caused by fool-the-system behaviour in an MDMP system - logon in EN and insert Chinese texts - this violates fundamental MDMP rules !

1) LFA1 texts are treated via SPUMG / SPUM4 - you should assign the correct language to the words in the vocab.

2) Search help fields in ADRC and LFA1 are probably already corrupted in Non-Unicode (and do not work in the MDMP system anyhow). If you logon in EN and create a Chinese address in an MDMP system, then the search help field will be created on basis of Latin-1 locale, which is wrong (lower-to-upper conversion).

Those entries need to be generated again - e.g. if you do a dummy change on the address.

Best regards,

Nils Buerckel

SAP AG

3 REPLIES 3

nils_buerckel
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Harshavardhan,

problem is caused by fool-the-system behaviour in an MDMP system - logon in EN and insert Chinese texts - this violates fundamental MDMP rules !

1) LFA1 texts are treated via SPUMG / SPUM4 - you should assign the correct language to the words in the vocab.

2) Search help fields in ADRC and LFA1 are probably already corrupted in Non-Unicode (and do not work in the MDMP system anyhow). If you logon in EN and create a Chinese address in an MDMP system, then the search help field will be created on basis of Latin-1 locale, which is wrong (lower-to-upper conversion).

Those entries need to be generated again - e.g. if you do a dummy change on the address.

Best regards,

Nils Buerckel

SAP AG

0 Kudos

Helli Nils

Thanks for the information.

further information to the proble.

Our SAP system is on basis support package level 63 and i have not applied correction from note 673941.

Will applying note for next MDMP preparation solve this problem?

ADRC table has 1 or 2 wrong tables wrong chinese characters in word after assigning ZH language in SUMG.

Is it can be corrected by applying notes or manual correction required.

thanks

Harshavardhan

nils_buerckel
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Harshavardhan,

Assumption: You have Chinese entries in table ADRC with ADRC-LANGU_CREA = EN

Now you have to distinguish two problems:

1) Chinese texts are stored in ADRC fields, which are NOT used for search help texts (most of the fields - e.g. ADRC-NAME1):

These texts can be handled in two ways:

a) Change LANGU_CREA = EN to LANGU_CREA = ZH for these entries (e.g. where ADRC-COUNTRY = CN) before the Unicode conversion (by the way, I would not use ADRC-LANGU, since this is the communication language, which does not necessarily comply with the code page of the entry).

This needs to be done in a similar way as shown in z-reports described in SAP Note 634839 ( although this specific fool-the-system case is not covered there - you have to adapt those examples)

b) Use SUMG to repair the entries using language ZH (as you already did)

My favourite would be a), as this can be done before the conversion (Note that SUMG ineeds to be executed during downtime !)

2) Chinese texts are stored in ADRC fields, which are used for search help texts (e.g. ADRC-MC_NAME1):

a) If these entries were inserted / changed with logon language ZH, then point 1) applies

b) If users logged on with logon language EN and created the entries, then most of these texts are destroyed already in Non-Unicode system. Then there is no automatic repair possible (at least point 1 does not work). Here my statement from before is valid:

Those entries need to be generated again - e.g. if you do a dummy change on the name.

According to my knowledge, this is a manual effort (either before or after the conversion) - but maybe it can be automized ...

Best regards,

Nils Buerckel

SAP AG