topic Re: Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE, in Application Development and Automation Discussions

Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE,

Former Member — Mon, 20 Feb 2012 09:18:41 GMT

Hallo All,

We perform CU&UC of R/3 4.6C sandbox system to the ERP 6.0 EHP5.

Currently the upgrade phase is completed and Unicode conversion should

be started (we are in the step "Additional Preparation Steps in NW 7.02

non-UC" in the CU&UC guide).

In various transactions (PFCG - Generating of profiles, SPAM/SAINT ) we

received an error "SAP characters 00367 and 00065 are not unique in

character set 1180". As a workaround we temporarily deleted Polish

language (PL) in program RSCPINST and activated (so only codepage 1100

was active). Currently we have activated the Polish language again.

In the source 4.6C system TMB (created by System Copy from productive

system PMB) there was also the configuration in RSCPINST of more than 1

codepage (1100, 1401) and in TCPDB table 1180 codepage was configured

(see attached pictures).

Our question :

How is it possible to avoid this situation in upgrades of following

system (IMB, QMB, PMB)? Could this configuration cause any

problems/inconsistencies during/after Unicode conversion export &

import ?

Regards Peter Gauer

Re: Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE,

nils_buerckel — Mon, 20 Feb 2012 09:35:33 GMT

Hello,

unfortunately I cannot find the attached picture you referred to ...

In SAP R/3 4.6c, the supported language configuration for Western and Eastern European languages would be 1100 and 1401.

As you can see in SAP notes 576772 and 452762, code page 1180 was released for BW / APO systems only.

If you set up 1180 in your 4.6c system, I would highly recommend to change this to a supported configuration (e.g. 1100 and 1401) and redo the CU&UC procedure!

Best regards,

Nils Buerckel

Re: Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE,

Former Member — Mon, 20 Feb 2012 13:02:40 GMT

Thanks Nils for reply !

Sorry I have not found a possibility to upload the mentioned pictures. Anyway!

In Tabel TCPDB is only one entry 1180, should we change this one to 1100 ?

We need following languages in our System, German, Polish, Spain and France.

T-Systems guys changed that already and we got no more error in TC, SAINT, PFCG , but they

changed it back, because they where not sure that this is the right way and now same error appears again.

And additional question in with step we should change the codepage for the next System

Development, Quality and Productive. if the codepage change is the solution.

Regards Peter

Re: Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE,

nils_buerckel — Mon, 20 Feb 2012 13:24:48 GMT

Hi Peter,

this highly depends on the fact whether you have special polish characters (which are not included in Latin-1 like e.g. ł ) stored on your system (e.g. in forms and/or master data).

If such characters do exist in your database, then you need to switch the system to MDMP and you need to execute SPUM4 including all scans.

Otherwise (if you switch TCPDB entry to 1100) all these characters will be converted based on Latin-1 (SAP code page 1100). E.g. the "ł" will be converted to "³".

If you do not know, then one option is to change the SBX to an MDMP system and execute SPUM4. All language independent data will be added to the vocab and you should be able to see the Polish words ...

However you need to analyze the language dependent data also (e.g. MAKT with language key PL) ...

Best regards,

Nils

Re: Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE,

Former Member — Mon, 20 Feb 2012 14:38:46 GMT

Hello Nils, here additional infomations in der Source System of the Sandbox,

we find with Program RSCPINST following information.

Step 1 languages

DE Deutsch

EN Englisch

FR Französisch

PL Polnisch

ES Spanisch

__ ____________________

Step 2 Countries

Latin1 oder MDMP

0EU SAP Unification

4EU EuropTranslit

8EU SAP Unification

Derived information

Neccessary codepages

1100 SAP internal, like ISO 8859-1 (00697/00819)

1401 SAP internal, like ISO 8859-2

What should we enter in Upgrade Sandbox, currently we can see this informations

Step 1

DE Deutsch

EN Englisch

ES Spanisch

FR Französisch

PL Polnisch

Step 2 ______________________________________________________________________

4EU EuropTranslit

Latin-1

PL Polen

8EU SAP Unification

0EU SAP Unification

4EU EuropTranslit__

The field TCP0D country code page Latin 1 or MDMP is in both systems not filled _______________________________________________________________________

Thanks for advice

Regards Peter

Re: Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE,

nils_buerckel — Mon, 20 Feb 2012 14:59:34 GMT

Hello Peter,

if you want to switch the system to MDMP, you need to select the <empty> field with the description "Latin-1 or MDMP" in the "enter country" section of rscpinst. As a result after hitting the "Activate"- Button, you should see 1100 and 1401 in table TCPDB and the country field in table TCP0D should be empty. After that you need to restart the system.

Best regards,

Nils

Re: Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE,

Former Member — Mon, 20 Feb 2012 15:48:09 GMT

Nils,

this is exactly what we have in the Productiv System.

But in the Upgrade Sandbox we have options

4EU EuropTranslit

Latin-1

PL Polen

8EU SAP Unification

0EU SAP Unification

4EU EuropTranslit

and TCP0D is blank and next filed is Latin-1

And in TCPDB is codepage 1180 shown, does that fit together.

Is it possible to have a short call regarding this topic tomorrow ?

Regards Peter

Re: Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE,

nils_buerckel — Tue, 21 Feb 2012 08:00:26 GMT

Peter,

please check / compare entries in table TCP0C. I guess you have customer specific entries in that table.

Regarding a call please contact me via mail (according to my contact details).

Best regards,

Nils

Re: Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE,

Former Member — Tue, 21 Feb 2012 08:17:17 GMT

Hi Nils,

there is only one entry in the System

Land der DB Sys. Sprache

4EU EN

Regards Peter

Re: Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE,

nils_buerckel — Tue, 21 Feb 2012 10:13:48 GMT

Hi Peter,

did you try to select the "empty" option for the country and then simulate this one ?

The preselection in rscpinst does not necessarily correspond to the actual I18n status of the system.

Maybe the entry 1180 in TCPDB was entered manually ?

Best regards,

Nils

Re: Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE,

Former Member — Tue, 21 Feb 2012 13:55:41 GMT

Nils,

if I do a simulation I got the note:

The needed language combination will be only in Unicode System supported

See SAP Note 73606

Regards Peter

Re: Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE,

nils_buerckel — Tue, 21 Feb 2012 14:36:59 GMT

Peter,

I assume the used system is still based on 4.6c ... ? Correct ?

Normally the statement is as follows:

"The required language combination is supported without restrictions

only in Unicode systems."

However this sounds like rscpinst uses the MDMP configuration for the simulation.

And this is exactly the needed Non-Unicode-Setup if you have special Eastern and Western European characters in your database (not supported on SAP ERP 6.0).

Best regards,

Nils

Re: Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE,

Former Member — Tue, 21 Feb 2012 15:06:47 GMT

Hello Nils,

After upgrade, before unicode conversion we got the following error message in PFCG, SAINT,..

"SAP characters 00367 and 00065 are not unique in character set 1180"

I got the information from T-Systems that they excluded polish languages out of RSCINST,

then codepage 1100 was used, than T-Systems added polish language again to have the original situation.

First message I got with the simulation (choose blank latin-1)

The required language combination is supported

only in Unicode systems

Please refer to SAP Note 73606.

Now I Choose: 4EU, EuropTranslit

and simulation showed no message above, but went to the next page.

see below

S e l e c t e d S e t t i n g s :

Language(s):

EN (E) English

FR (F) French

DE (D) German

PL (L) Polish

ES (S) Spanish

Country code:

4EU EuropTranslit

R e s u l t s :

Code page configuration type:

Non-Unicode - Single Code Page configuration

Processed language entry:

DEFLS

Language(s) and Corresponding Code Page(s):

EN (E) 1180 Transliteration from Latin-2 (...) to Latin-1

FR (F) 1180 Transliteration from Latin-2 (...) to Latin-1

DE (D) 1180 Transliteration from Latin-2 (...) to Latin-1

PL (L) 1180 Transliteration from Latin-2 (...) to Latin-1

ES (S) 1180 Transliteration from Latin-2 (...) to Latin-1

T a s k s :

Required OS locales and their current status:

Locale installed = the locale is installed correctly

Set locale failed = the locale needs to be corrected on the app server

citmb07_TMB_07 de_DE.ISO-8859-1 Locale installed

en_US.ISO-8859-1 Locale installed

fr_FR.ISO-8859-1 Locale installed

de_DE.ISO-8859-1 Locale installed

es_ES.ISO-8859-1 Locale installed

Required profile parameter modifications:

RSCPINST does NOT change the value of profile parameter.

Please check the value of below parameter(s) after activation.

1) Please update zcsa/installed_languages.

e.g. Copy the new value and paste it into a field in transaction RZ10

New: DEFLS

Current (sorted):

citmb07_TMB_07 DEFLS

2) Please proceed with Check result for below parameter(s):

OK Checked and no inconsistency found.

Regards Peter

Re: Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE,

Former Member — Tue, 21 Feb 2012 15:19:16 GMT

Hi Nils,

T-System just told me that the System is

already an ERP 6.0 EHP5 System (non Unicode).

Regards Peter

Re: Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE,

nils_buerckel — Tue, 21 Feb 2012 15:32:57 GMT

Hello Peter,

ok, according to your initial description you are already on SAP ERP 6.0 (I forgot this in my last reply).

However if you want to do a proper CU&UC conversion with an MDMP 4.6c system I do not an alternative other than

- rebuild the 4.6C system

- make sure that it is based on MDMP (1100 and 1401) and

- run SPUM4 before the upgrade.

You could now manipulate the TCPDB table and force the MDMP setup (rscpinst does not allow an MDMP setup on SAP ERP 6.0) ... but this does not really help since I think you need to convert the SBX system the same way as the other systems - and there you need to run spum4 (and not SPUMG) ...

If you are only interested in the conversion runtime you can also go on with a Unicode conversion based on 1180 ... but this does not give you experiences on the important area of the Unicode conversion of an MDMP system.

Best regards,

Nils

Re: Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE,

Former Member — Wed, 22 Feb 2012 12:35:29 GMT

Hi Nils,

we made a check in 4.6C version and we do not found any polish specific characters, it seems not possible to enter,

In this case a latin-1 conversion should be enough, do you agree ?

Any Idea why we got 1180 as default codepage ?

Current situation in Sandbox

tab TCPDB, 1180 only is filled.

Report RSCPINST, with latin-1 we get the mentioned error and with 4EU I do not know

tab TCP0C currently 4ÉU , EN is filled

what do you think make it sence to go ahead with the current unicode conversion with 4EU

For next upgrade following questionS

how we should maintain tab TCPDB...........

how we should maintain Report RSCPINST............

how we should maintain tab TCP0C .........................

Thanks for advice

Regards Peter

Re: Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE,

nils_buerckel — Thu, 23 Feb 2012 10:19:36 GMT

Hi Peter,

technically as far as I know you can go on with source code page 1180 (although the configuration is not supported anymore).

On the other hand you can also do a single code page conversion using 1100 (you have to "delete" PL entry in rscpinst right before doing the upgrade - then it will add 1100 to TCPDB).

However in any case you need to be aware that Polish special characters need to be repaired in SUMG in both cases.

Hence the savest would be to do an MDMP conversion (as stated before).

Best regards,

Nils

Re: Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE,

Former Member — Tue, 26 Feb 2013 14:49:31 GMT

Hi Peter,

We have the same scenario here, where the R/3 4.6c system has code page as 1180. In our case we have Romanian language for which the code page is 1401, whereas English, Latin, German and Spanish are with 1100 code page.

Could you please guide me what method you choose for the Upgrade and Unicode for your system which also had the same issue.

Waiting for your reply.

Thanks,

Manas