2EETW000 some text was mutilated during conversion from unicode to ascii.

[Former Member]

Hi Expert,

We are doing an CU & UC from ECC 5.0 MDMP to ERP 6.0 EHP4 SR1 Unicode.

The SPUMG preconversion phase has been completed, and the language list is assigned with

DE: 8300, EN:8300, ZF:8300, HE=1800, JA=8000

The Global Fallback Code Page set to 8300.

When we run into the Upgrade, and in phase PREPARE/TR_CMDIMPORT_PREAPARE,

we got the error message:

-

---

3 ETW677 "R3TRTABUT5BVJ" not imported in this step.

4 ETW000 ... ignoring such differences.

4 ETW000 ... ignoring such differences.

3 ETW677 "R3TRTABUT5DPBS03" not imported in this step.

4 ETW000 ... ignoring such differences.

2EETW000 some text was mutilated during conversion from unicode to ascii. This is the result: 'MINDERUNG ## 4A ABS.'

2EETW000 some text was mutilated during conversion from unicode to ascii. This is the result: 'MINDERUNG ## 4A ABS.'

3 ETW677 "R3TRTABUT5DPBS0C" not imported in this step.

4 ETW000 different nametabs for table T5ET2 (field SRTF2).

4 ETW000 Existing Field Imported Field

4 ETW000 keypart: 'X' 'X'

4 ETW000 format : 'I' 'I'

4 ETW000 len : 004 004 (bytes)

4 ETW000 offset : 048 092 (bytes)

-

---

We have search all SAP notes, and SDN message, but no any clues of this error.

We are neither able to locate the actual table for that specific conversion error record.

Appreciate you can provide and hint or solution for me to move on...

Best regards,

Eddie

[nils_buerckel]

Hi Eddie,

I recommend to assign DE to code page 1100 (via tables tcp0c / Tcpdb). In addition I would also change DE --> 1100 in spumg.

Best regards,

Nils Buerckel

SAP AG

[Former Member]

Hi Nils,

Thanks in advance for your quick reply!

Actually we just resolved the issue by change the latest 701 (target relase) kernel in the upgrade folder.

I would still like to clarify below things...

1. We have the DE:8300 in SPUMG langauage list setting, and the global fallback code page = 8300 (most used codepage).

What would be the impact to the upgare and unicode conversion?

From the CU&UC guide and relevant notes this settings seems right!

Please advise should we manually change to DE:1100 from SPUMG language list setting?

2. for the DE:1100 entry in the TCP0C and TCPDB table,

We have 8300:8300, 1800:1800, and 8000:8000 already existed in the TCPDB, which was actiavted from RSCPINST

with MDMP lanagauge assignment of DE, EN, ZF, JA, HE. when the issue happened, we have tried to add 1100:1100

to the TCPDB table, but as I remembered this is not correct, TCPDB should be maintained through RSCPINST activation.

Please advise do I need to add 1100:1100 manually to TCPDB, or just follow the RSCPINST to actiavte?

Thanks and best regards,

Eddie LIn

[nils_buerckel]

Hi Eddie,

1. I assume you do not use DE actively in your vocab and you do not have customer entries with language key DE based on code page 8300 (?). In this case if you set DE to 8300, the SAP standard entries will be converted based on that code page and hence all those entries containing German special chars (üöäß) will be destroyed (see SAP note 1021586 - Section: Reason and Prerequisites - Note that the solution of this note does not fit in your case, since you have an MDMP system). You can repair part of that with the import of the German language (see SAP note 922783). However in order to avoid this, I would recommend to set DE to 1100 in SPUMG.

2. If you do not have a problem in the upgrade (e.g. the error mentioned initially), then leave the settings in TCPDB as it is now.

Best regards,

Nils Buerckel

SAP AG

[Former Member]

Hi Nils,

Thanks for your reply!

We update the Kernel to latest one and passed the TR_CMDIMPORT_PHASE phase,

But unfortunately, We hit the same bomb at SHADOW_IMPORT_INC phase, and

we have tried to update R3trans all the version, but still failed with the same error message at

SAPup.ECO, SHDALLIMP.ELG and SAPK-604DRINSAPHR.RH1:

-

---

This is D:\usr\sap\RH1\upg\abap\exenew\tp.exe version 372.04.88 (release 701)

This is D:\usr\sap\RH1\upg\abap\exenew\R3trans.exe version 6.14 (release 701 - 08.03.10 - 09:05:00).

2EETW000 some text was mutilated during conversion from unicode to ascii in language 'J'. This is the result: '###p#### &1 ###l################## #e#[#u## t77tnm_ca #####`############ '

2EETW000 some text was mutilated during conversion from unicode to ascii in language 'J'. This is the result: '###p#### &1 ################ #e#[#u## t77tnm_cc ###J#e#S#######A######## '

2EETW000 some text was mutilated during conversion from unicode to ascii in language 'J'. This is the result: '###p#### &1 ###e#[#u## t77tnm_cg ###J#e#S###O###[#v#####A######## (molga '

2EETW000 some text was mutilated during conversion from unicode to ascii in language 'J'. This is the result: '###p#### &1 ###l################## #e#[#u## t77tnm_ca #####`############ '

2EETW000 some text was mutilated during conversion from unicode to ascii in language 'J'. This is the result: '###p#### &1 ################ #e#[#u## t77tnm_cc ###J#e#S#######A######## '

2EETW000 some text was mutilated during conversion from unicode to ascii in language 'J'. This is the result: '###p#### &1 ###e#[#u## t77tnm_cg ###J#e#S###O###[#v#####A######## (molga '

D:\usr\sap\RH1\upg\abap\exenew\R3trans.exe finished (0008).

Warning: Parameter INTERRUPT is no longer used.

Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.

Warning: Parameter WITH_TACOB is no longer used.

Warning: Parameter IMPDP_BY_EVENT is no longer used.

Warning: Parameter INTERRUPT is no longer used.

Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.

Warning: Parameter WITH_TACOB is no longer used.

Warning: Parameter IMPDP_BY_EVENT is no longer used.

stopping on error 8 during SHADOW IMPORT

tp returncode summary:

TOOLS: Highest return code of single steps was: 8

WARNS: Highest tp internal warning was: 0118

tp finished with return code: 8

meaning:

A tool used by tp produced errors

sapparam: sapargv( argc, argv) has not been called.

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

ERROR: stopping on error 8 during SHADOW IMPORT

Process with ID 3080 terminated with status 8

Deleting file D:\usr\sap\RH1\upg\abap\log\SHDALLIMP.ELG

Moving file D:\usr\sap\RH1\upg\abap\log\PROT.TMP to D:\usr\sap\RH1\upg\abap\log\SAPK-604DRINSAPHR.RH1

Moving file D:\usr\sap\RH1\upg\abap\log\SHDALLIMP.ELG to D:\usr\sap\RH1\upg\abap\tmp\SHDALLIMP.ELG

Deleting file D:\usr\sap\RH1\upg\abap\tmp\MSGIN.LST

Deleting file D:\usr\sap\RH1\upg\abap\tmp\MSGOUT.LST

Deleting file D:\usr\sap\RH1\upg\abap\tmp\MSGOUT.LOG

Deleting file D:\usr\sap\RH1\upg\abap\tmp\SHDALLIMP.ELG

Deleting file D:\usr\sap\RH1\upg\abap\log\TP.ECO

Copying file D:\usr\sap\RH1\upg\abap\buffer\RH1 to D:\usr\sap\RH1\upg\abap\buffer\INCIMP.BUF

-

---

We tried every way of switch kernel and R3trans, but still the same..

We suspect very strongly that is the EHP4 & it's SP's error...

Since in this stage SAPup rxtract the Add-on SPs and import into Shadow,

And very strange is the 'J' is not in out system langauges at all.... very starange.

Now we have open SAP customer message "Error in phase MAIN_SHDIMP/SHADOW_IMPORT_INC ( 403186 / 2010 ) "

Still waiting for reply... (but slow )

Do you have any idea or suggestion for me?

Thanks and best regards,

Eddie

[nils_buerckel]

Hi Eddie,

what is your settings for DE in table TCP0C ?

PLATFORM = <your platform>

LANGU = <DE>

COUNTRY = <entry in field TCP0D-COUNTRY - should be EMPTY in MDMP systems>

MODIFIER = <EMPTY>

?

Best regards,

Nils Buerckel

SAP AG

[Former Member]

Hi Nils,

We have below entries for the UC & upgarde:

1. TCP0C

PLATFORM LANGU COUNTRY MODIFIER CHARCO CHARCOMNLS

========== ====== ======== ======== ======== ============

Windows NT D 8300 8300

Windows NT D DE 1100 1100

Windows NT D TW 8300 8300

We have opened customer message for the issue, and got reply that the above 3 entries in TCP0C

must all be maintained as 1100:1100, then the upgrade stuck problem is resolved.

But now we are running the 2nd upgrade rehearsal now, and if we change the TCP0C as above, we will

fail to maintain I18N (RSCPINST) to configure the correct langauge setting at TCPDB.

so what we decide to do is keep the above setting (8300:8300) during RSCPINST activation,

and maintain the TCP0C right before we start the Upgrade Tool.

Is this is correct procedure for maintaining the TCP0C for DE entries??? Kindly advise!

2. TCP0D

COUNTRY DBLANGU

======== ========

E

3. TCPDB

CPTRANSFLD CPPOOLCLUS

=========== ===========

1800 1800

8000 8000

8300 8300

Above TCP0D & TCPDB is configured entries after activation of RSCPINST with

MDMP setting with DE, EN, ZF, JA, HE.

Are above TCP0D & TCPDB entries correctly setup???

4. SPUMG language list setting

HE 1800 X

DE 1100 X

EN 8300 X

JA 8000 X

ZF 8300 X

Thanks and best regards,

Eddie

[nils_buerckel]

Hi Eddie,

1. The change of TCP0C is simply to resolve the upgrade error. If you are able to resolve it by just changing the entries right before the upgrade, then this should be ok. By the way, you only need to change one entry - in your case it is the one with COUNTRY = <EMPTY> (the first one listed by you).

2. Your TCP* settings are not as recommended in a standard MDMP setup (there, EN is assigned to 1100), but technically this is ok.

Best regards,

Nils Buerckel

SAP AG