Report UMG_ADD_PREP_STEPS Does not exists Non-Unicode to Unicode Conversion

[Former Member]

Dear All,

We are in the process of converting a Non-Unicode system to Unicode system.

We have a ECC 5.0 Non-Unicode System (Release 640 Patch 21) with Orcale 10g.

We have a Single Code Page System and we have performed the necessary preparation steps under the guidence of "SINGLE CODE PAGE SYSTEM CONVERSION to UNICODE NW 2004" - An SAP Guide downloaded from SAP Note.

We are in the phase of Unicode Preconversion Phase.

In "Additional Preparation Steps" we have to run the Report UMG_ADD_PREP_STEPS.

When we went to run this report from SE38, it says report does not exists.

We checked the Note 1275254 and downloaded the correction and run the report RUTDD07TLA.

But still nothing is happening.

When running SPUMG t-code and clicked on the "Additional Preperation Steps" it is giving MESSAGE TYPE X dump.

From the Guide we learnt that unless and untill the report UMG_ADD_PREP_STEPS has run in the background further steps can not be execueted.

Please help.

Regards,

Souren

[Former Member]

thanks

[sunny_pahuja2]

Hi,

Report is UMG_ADD_PREP_STEP not this UMG_ADD_PREP_STEPS

Thanks

Sunny

[Former Member]

Thanx Sunny.....

Still I am getting the dump of 'Message Type X' when executing the report UMG_ADD_PREP_STEP.

-

---

Line SourceCde

1 method get_system_type.

2

3 data: tcpdb_itab type standard table of tcpdb,

4 cp_num type i,

5 l_hybrid type abap_bool value abap_false.

6

7 select * from tcpdb into table tcpdb_itab order by primary key.

8 describe table tcpdb_itab lines cp_num.

9

10 * Determine system type: MDMP, Ambig. Blended or Single Codepage System

11 case cp_num.

12 when 0.

13 if cl_abap_char_utilities=>charsize > 1.

14 ex_system_type = cl_umg_pre_stock=>c_uc_system.

15 else.

>>>>> message x268(umg).

17 endif.

18 when 1.

19 read table tcpdb_itab into ex_fb_codepage index 1.

20 case ex_fb_codepage.

21 when '6100' or '6500'.

22 ex_system_type = cl_umg_pre_stock=>c_ambig_system.

23 ex_fb_codepage = '1100'.

24 when '6200'.

25 ex_system_type = cl_umg_pre_stock=>c_ambig_system.

26 ex_fb_codepage = '8000'.

27 when '6300'.

28 ex_system_type = cl_umg_pre_stock=>c_scp_system.

29 ex_fb_codepage = '6301'.

30 when others.

31 ex_system_type = cl_umg_pre_stock=>c_scp_system.

32 endcase.

33 when others.

34 loop at tcpdb_itab transporting no fields

35 where cptransfld = '6100' or

-

---

We are using SAPGUI 710 patch 13

Please help

Regards,

Souren

[Former Member]

Dear All,

One more thing..In the dump it says if the TCBDB table is empty it is a unicode system.

-

---

Error analysis

Short text of error message:

Table TCPDB is empty. Please configure your system with RSCPINST.

Technical information about the message:

Diagnosis

In order to ensure the correct conversion procedure, SPUMG reads

the table TCPDB to determine the system type (Single Codepage

System, Blended Codepage System or MDMP System). In non Unicode

systems it is essential that table TCPDB contains all codepages

which are used in the system. In Unicode systems table TCPDB is

empty.

System response

Procedure

Please use the report RSCPINST to configured your system properly.

Procedure for System Administration

Message classe...... "UMG"

Number.............. 268

Variable 1.......... " "

Variable 2.......... " "

Variable 3.......... " "

Variable 4.......... " "

Variable 3.......... " "

Variable 4.......... " "

-

---

Table TCBDB is empty in our system and in the system-->status we are getting the system as Non-Unicode system.

Can anyone clarify this thing.

Regards,

Souren