SCP700

Single Code Page

System Conversion

to Unicode NW 7.0

SAPNetWeaver 7.0 SP 17 and higher Last update:

© Copyright 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner,

WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

Typographic Conventions

Icons

Single Code Page System Conversion to Unicode...

Restrictions...

Requirements...

General Description...

Chronological Order of the Conversion Steps...

1. Preparation...

1.1 Consistency Check for Cluster Tables

10

1.2 Conversion of customer-defined code pages

11

1.3 Make ABAP programs Unicode-compliant

11

1.4 Delete Matchcode IDs

13

1.5 Reducing Data Volume

13

1.5.1 Pre-Conversion Correction of Table Data

14

1.6 Language Flag Maintenance

16

1.7 Printing Old Spool Requests after the Unicode Conversion

17

1.8 OTF Documents after the Unicode Conversion

17

1.9 Translation Environment

17

2. Unicode Preconversion Phase...

2.1 SPUMG...17

2.1.1 Restart SPUMG

17

2.1.2 Welcome to SPUMG

17

2.1.3 Exception List

18

2.1.4 Additional Preparation Steps

18

2.1.5 Language List

22

2.1.6 SPUMG Settings

22

2.1.7 Initializing the Worklist

23

2.1.8 Consistency Check

23

2.2 Final Preparation Steps...25

2.2.1 SPUMG Updates

25

2.2.2 Check Matchcode IDs

26

2.2.3 Nametab handling

26

2.2.4 Tables with obsolete data

27

2.2.5 Additional Downtime Steps

28

3. Unicode Conversion Phase...

3.1 Database Export and Import...30

3.1.2 Transfer Files to Target Host

34

3.1.3 Database Import

34

3.2 Follow-Up Activities...36

4. Unicode Conversion Completion Phase...

Additional Post Conversion Steps

37

5. Appendix...40

5.1 Reports/Programs

40

Single Code Page System Conversion

to Unicode

SAP NetWeaver 7.0

Purpose

This document details the steps necessary to convert an existing non-Unicode SAP System with one standard non-Unicode system code page to Unicode.

Validity

This document is valid for SAP NetWeaver 7.0 Support Package 17 and higher. All Single Code Page Conversion Guides can be downloaded from SAP Note 1051576. Make sure you have downloaded the most current version of the Single Code Page Conversion to Unicode Guide.

Statement on Data Consistency in Unicode Conversions

Information about data consistency and SOX-compliance are available on SAP Service Marketplace Quick Link /unicode  Unicode Media Library  Unicode Information on Specific Topics  SAP Statement: Data consistency in a Unicode Conversion.

Documentation

In addition to the “Single Code Page Conversion to Unicode Guide” you need the System Copy Guide for your release. The System Copy Guide is required for the Unicode Conversion Phase which is in fact a System Copy procedure with special code page settings. You can download all valid System Copy Guides from the SAP Service Marketplace at:

http://www.service.sap.com/instguidesNW70

How to check if the system is a Single Code Page System

If you are not sure whether your system is a Single Code Page system or not, open database table TCPDB in transaction SE16. If this table contains only one entry, it is a Single Code Page system.

If TCPDB contains more than one entry, the system is an MDMP system.

Constraints

This documentation does not contain information about the preconversion and

postconversion steps that are required for MDMP systems. SAP assumes no responsibility or liability of any or all problems that may arise.

Ambiguous Blended Code Pages

6100 SAP Unification

6200 SAP Asian Unification

6500 SAP Diocletian

Systems which have one of those code pages installed must be converted like MDMP systems. Download the Unicode Conversion Guide for MDMP systems from SAP Note 551344.

Important SAP Notes

SAP Notes mentioned in this document contain reports or corrections for download, or additional information which is subject to changes. If you cannot open the hyperlinks, open a browser window first and then click on the link again.

548016 “Conversion to Unicode”: Application-specific information

540911 “Unicode restrictions for R/3 Enterprise, ECC 5.0, ECC 6.0”: Component-specific restrictions

79991 “Multi-Language and Unicode support of mySAP solutions”: Recent information about Unicode-enabled mySAP solutions 765475 “Unicode Conversion: Troubleshooting”:

Troubleshooting Guide for Unicode Conversions

Restrictions

1. The conversion of systems using code page 8340 (Hong Kong Supplementary Character Set) are only available as on a project basis with SAP involvement. See 2.1.5

Language List [page 22] for details. Download the supplementary documentation “Conversion of HKSCS Systems to Unicode” from SAP Note 551344.

2. You can not install a Unicode system with a non-Unicode system in one database (MCOD).

DB2-z/OS: Read SAP Note 1068215 for information about MCOD with Unicode and non-Unicode systems on DB2-z/OS.

3. SAP Unicode systems are not released for Informix. See chapter 3. Unicode Conversion Phase [page 26]for details about database change and simultaneous Unicode

conversion.

4. Conversion from Unicode to non-Unicode is not possible.

5. Third Party products: If you are using software from other vendors, check whether it is Unicode-compliant. Note that “SAP certified” does not imply “Unicode compliance”. 6. Note the restrictions for Unicode Solution Manager monitoring non-Unicode systems with

7. BW systems: Follow SAP Note 673533 before starting Unicode conversion of BW systems. Otherwise problems during data extraction can occur after the conversion.

Requirements

Software Requirements

Make sure that all required DVDs for the system copy are available. For details, refer to the System Copy Guide, sections Planning and Database Independent System Copy.

Frontend Requirements

Requirements: SAP recommends that you install SAP GUI 7.10 with the latest Patch Level.

Documentation: “SAPGUI for Windows: I18N User Guide”: You can download this documentation from SAP Note 508854

Status: required.

Note

For full support of languages with multi-byte system locales (Japanese, Traditional Chinese, Simplified Chinese and Korean) SAP GUI for Windows 6.40 or higher is required.

Component-specific Requirements

1. If you use HR functionality in your SAP system, you have to process additional steps which are described in SAP Note 573044.

Caution

If you perform the standard procedure without the additional steps, data loss will be the result. SAP does not take any responsibility in this case!

2. If you use SAP Office functionality in your SAP system, read SAP Note 691407 for further information on Unicode conversion.

3. If you use the SAP liveCache tool, read SAP Notes 632357 (SCM 4.0 and higher) for information about backing up the liveCache data before the system conversion.

4. If you use the Credit Card Encryption function, note that all encrypted card numbers are decrypted before the Unicode Conversion. Follow the instructions in SAP Note 766703. 5. If you use SAP Easy Document Management (EasyDMS), follow the instructions in SAP

Note 1056170.

6. Conversion of CRM systems: Note that Business Transaction duration data must be saved before the Unicode Conversion. Follow SAP Note 1122968.

7. If you use Automatic Payment Transactions (Payment Program/Payment Transfer), read SAP Note 1390229.

8. If you use a Content Server (Document Management Services), follow the instructions in SAP Note 1612108.

Private Use Area in Unicode Systems

Customers with Asian system code pages (Japanese, Korean, Simplified Chinese, and Traditional Chinese) that have been using the user definable areas are advised to read SAP Note 726954 to check the mapping of the user defined characters to Unicode.

General Description

To convert a Unicode system to Unicode, all character data (i.e. text data) in the non-Unicode database must be converted to non-Unicode. The overall conversion procedure is a System Copy with special code page settings. The actual data conversion to Unicode is done during the export. For further information about system copy optimization, go to

www.service.sap.com/systemcopy optimization.

Chronological Order of the Conversion

Steps

Phase Action Section Purpose When

Preparation Code pages

and programs Consistency Check for Cluster Tables [page 11] Check and analyze inconsistencies in Cluster Tables Planning Phase (weeks before preconversion) Conversion of customer-defined Code Pages [page 11] Required if own code pages exist (ex.: printer code pages)

Make ABAP Programs

Unicode-compliant [page 12]

Check that all customer programs are Unicode-enabled.

Tables and

Table entries Reducing Data Volume [page 14] Language Flag Maintenance [page 16] Additional Preparation Steps [page 19] Ensure that obsolete table entries are deleted and that the Text Lang. flag is correctly set for all tables.

Database

Check Data Analysis SPUMG [page 18] Run transaction SPUMG to check the consistency of the database. Preconversion (uptime) Updates Nametab Handling Additional Preparation Steps Final Preparation

Steps [page 26] SPUMG and Statistics Update Generate nametabs

Database

Conversion Export (incl. Conversion) and Import

Unicode

Conversion Phase [page 26]

Create the

Unicode database System Copy_(downtime)

Conversion Completion

Finalization First Steps in the Unicode System [page 37]

Run final reports and maintain tables Post-Processing Steps (downtime) Note:

The authorization profile required for the entire system conversion process is SAP_ALL.

1. Preparation

1.1 Consistency Check for Cluster Tables

Programs: Report SDBI_CLUSTER_CHECK Documentation: SAP Notes 1348055; 1077403 Status: mandatory.

You use report SDBI_CLUSTER_CHECK to search for initial cluster records in cluster tables. Initial cluster records must be removed before the database export; otherwise the export might cancel. SAP Note 1348055 provides a description of the report and explains how to proceed when initial cluster records are found. For information about the latest version of the report, read SAP Note 1077403.

SDBI_CLUSTER_CHECK is not restricted to systems which will be converted to Unicode afterwards. You can use it as a regular maintenance task in all systems. You can execute the report anytime and as often as needed independent from SPUMG.

The runtime of SDBI_CLUSTER_CHECK is dependent on the size of the table clusters. Note that for very large table clusters it might take up to several days. Therefore you should execute this check at a very early stage of the Unicode Conversion Project.

Execute report SDBI_CLUSTER_CHECK in transaction SE38. On the selection screen choose Execute Cluster Check and press . On the next screen select Program  Execute in Background from the menu bar. If the overall status of the last check run contains errors, follow the instructions in SAP Note 1348055.

1.2 Conversion of customer-defined code pages

Customer code pages which begin with "9" must be converted to comply with the new, Unicode-based code page structures. In most cases such code pages are printer code pages.

Programs: RSCP0126

Documentation: SAP Notes 485455 and 511732; 534720; online documentation in transaction SCP

Status: mandatory (only if code pages 9xxx exist)..

Remote Code Page Check

Programs: UMG_CHECK_RFC

Documentation: online documentation in transaction SE38 Status: recommended.

Before the Unicode Conversion it is useful to check your own TCP/IP-connections and adjust the code page information if required. Run report UMG_CHECK_RFC in SE38 as described in the online documentation to check if the connection between the local system where you run UMG_RFC_CHECK and a remote TCP/IP destination is consistent regarding the involved local and remote code pages.

In a connection between a Unicode single code page system A and a remote non-Unicode single code page RFC client or server B the code pages must match.

Note

You can run UMG_CHECK_RFC in non-Unicode Systems only.

1.3 Make ABAP programs Unicode-compliant

Only programs that comply with the stricter ABAP 6.10 syntax and semantics will run in a Unicode system. You must ensure that:

1. All your own programs are ABAP 6.10 compliant.

2. All SAP programs you modified (SAP Note 548016) – including customer exits that you use (SAP Note 549143) - are ABAP 6.10 compliant.

To determine which SAP programs you modified, run transaction SE95.

Programs: transactions UCCHECK and SCOV

Documentation: transaction ABAPHELP, search with keyword "Unicode" System Documentation in UCCHECK and SCOV

SAP Notes: 367676; 549143; 548016; 1139325 (general information, additional helper tools, etc).

Asian (especially Korean) customers: SAP Note 1007073 Status: mandatory.

Run UCCHECK and enter the programs you want to check: all objects in the customer namespace, all objects of type FUGS and the SAP programs you modified.

Caution

Do not run UCCHECK for all SAP programs. There are some SAP programs that have not been Unicode-enabled, because they are not needed in a Unicode system or will be regenerated in a Unicode system. It is not necessary to process them with UCCHECK.

After you have completed the check, and modified any code that was not ABAP 6.10

compliant, you should check the runtime behavior of your programs. UCCHECK issues errors or warnings for static errors, or where potential errors are possible, but some errors can only be detected at runtime. You can monitor your testing with SCOV.

Note

If you use C/C++ programs, they must also be Unicode-enabled (see RFC-Documentation on SAP Service Marketplace). Go to service.sap.com/rfc-library. Select Media Library 

RFC Library Guide.

Unicode Enhanced Syntax Check

The system profile parameter abap/unicode_check=on can be used to enforce the enhanced syntax check for all objects in non-Unicode systems. When setting this parameter, only Unicode-enabled objects (objects with the Unicode flag) are executable. Note that after setting the Unicode flag, automatically generated programs might need to be regenerated. The mentioned parameter should be set to the value "on" only, if all customer programs have been enabled according to transaction UCCHECK.

Note:

If you have problems with generated objects which are not Unicode-enabled, search for information in the following notes:

SAP Note Short Text

84023 Re-generating drilldown reports (gen. Reports in Package KC_GEN) 99507 LO-LIS: Update termination after upgrade/client copy

321714 PE03: Technical information on features 497850 Condition maintenance reports and Unicode 563417 Unicode indicator for BOR object type programs 652129 SAP BP: Business partner search

673066 LSMW: Upgrade to SAP Enterprise 4.7 (or Basis 6.20) 674882 Upgrade: Syntax error in program RKE5XXXX

708442 Incorrect generated programs in Unicode systems 886771 Generation in condition maintenance

1275149 Input help (F4): Preparing the Unicode conversion

BW System conversions: There are programs starting with GP* which cannot be re-generated via SAP Note 84023. You can use transaction RSSGPCLA as described in SAP Note 609054.

If you have problems with regeneration of reports RK31*, RK32*, RK33* or RK34*, create a customer message under component CO-PA.

1.4 Delete Matchcode IDs

[This section is only required for Support Packages lower than SP22. With SP22 and higher, TWTOOL01 is included in report UMG_ADD_DOWNTIME_STEPS.]

Program: TWTOOL01 Documentation: SAP Note 24860 Status: required.

Run report TWTOOL01 to find all active pool-matchcode IDs. This is important because matchode IDs are not supported in Unicode SAP systems and must be handled before the Unicode Conversion as described in SAP Note 24860.

Note:

It is recommended to run TWTOOL01 at this point of time during the Unicode Conversion Project and to process the output of the report now as described in the SAP Note. But note that you must be finished before the database export (chapter 3.)

Do not start the Export before all matchcode IDs have been deleted! Run this report until message “Check successful, no action necessary” is shown!

1.5 Reducing Data Volume

If not described differently in the relevant SAP Notes, you can carry out all the steps in this chapter during system uptime.

This section provides information about tables which show the largest growth in data volume. The content of this section relates to data gathered in systems with SAP R/3 Release 4.0 and later. Before starting the Unicode preconversion SAP recommends that you delete and/or archive obsolete data from these tables in order to improve the system performance during the conversion procedure.

Documentation: SAP Note 679456; SAP Note 1422822; SAP Note 638258; Data Management Guide.

You can download the Data Management Guide from the SAP Service Marketplace: http://service.sap.com/ilm Data Archiving.

Read SAP Note 679456 for details. Read the “Data Management Guide” for detailed information on how to maintain tables with large data volume in all SAP R/3 systems. Follow the steps described in SAP Note 1422822.

1.5.1 Pre-Conversion Correction of Table Data

If you have carried out a project of the SAP System Landscape Optimization, you have imported objects of the Conversion Workbench into your SAP system. SAP recommends deleting these objects according to SAP Note 638258 before starting the Unicode conversion. SAP Technology Business Services - Adress Management:

Tables: ADRC and ADRP tables Documentation: SAP Note 673941

Status: recommended

SAP recommends that you maintain corrupt records in ADRC and ADRP tables according to SAP Note 673941.

QCM tables (Conversion Tables):

Tables: QCM <table_name>

Documentation: System Copy Guide, Section Technical Preparations"; SAP Note 9385

Status: recommended

Delete QCM tables from the source system as described in SAP Note 9385.

BW System conversions:

Tables: Tables starting with /BI0/0 Documentation: SAP Note 449891

Status: mandatory

Delete temporary database objects as described in SAP Note 449891. IS-AFS (Industry-specific component Apparel and Footwear): Documentation: SAP Note 1363394

Status: mandatory

There are wrong master language entries for AFS objects in table REPOSRC (field RLOAD). The entries must be deleted first and the correct values entered afterwards as described in SAP Note 1363394.

IDoc Interface/ALE: Organizing the change pointer log tables:

Table: BDCP, BDCPS, BDCP2

Documentation: SAP Notes 305462, 513454, 739210

Status: mandatory

1. You use the change pointer storage as described in SAP Note 305462.

Use report RBDCPCLR to maintain BDCP2 according to SAP Note 513454. Use report ZTKRBDCPCLR to maintain BDCP and BDCPS according to SAP Note 739210.

2. You use the old change pointer storage.

Use report RBDCPCLR to maintain BDCP and BDCPS according to SAP Note 513454. You do not need to maintain BDCP2.

This step is only required in SP 16/17/18. With SP 19 it is included in UMG_ADD_PREP_STEP.

Terminology and glossary text tables (e.g. STERM_TEXT): Documentation: SAP Note 1280494

Status: mandatory

Terminology and glossary text tables (e.g. STERM_TEXT) with EN language key contain some entries with non-7bit ASCII characters. Such entries are obsolete and should be deleted. Run report TERM_DELETE_INCORRECT_CHARSET as described in SAP Note 1280494.

The next two steps are only required in SP 16/17. The corrections are delivered with SP 18.

PA-PA-GB: Special handling for table T5GEFDATA required:

Table: T5GEFDATA

Documentation: SAP Note 1239557

Status: mandatory

T5GEFDATA is a container table, i.e. structured data (text and binary data) are stored in the character like field T5GEFDATA-DATA1. For the Unicode preparation a special handling has to be done for table T5GEFDATA, taking the substructure of the container field into account. Follow the description in SAP Note 1239557.

Special handling for table DBTABLOG required:

Table: DBTABLOG

Documentation: SAP Note 1255556

Status: mandatory

DBTABLOG is a container table, i.e. structured data (text and binary data) are stored in the character like field DBTABLOG-LOGKEY. For the Unicode preparation a special handling has to be done for table DBTABLOG, taking the substructure of the container field into account. Follow the description in SAP Note 1255556.

1.6 Language Flag Maintenance

As of Release 6.20 all LANG fields have a Data Dictionary (DDIC) attribute Text Lang. (indicator for a language field). This flag specifies that the LANG field determines the code

page of the character data in that table. Text Lang. flags are evaluated during RFC communication between Unicode and non-Unicode systems to ensure that the correct character conversion is used.

The flags are not required in SPUMG, but will be evaluated by R3trans during transports. After the conversion the flags are required for communication via RFC.

Make sure you run the most recent version of RADNTLANG. SAP Note 480671 provides a detailed and release-specific documentation of the text flag handling.

Run report RADNTLANG [page 41] to set the Text Lang. flag for all tables with one

LANG/SPRAS field. This report should be run in the background, since it may take several hours.

There are special cases when the flag should be turned off after RADNTLANG has run:

 The LANG field does not specify the code page of the character data in the table, but some other language property. In this case the Text Lang. flag must be turned off to ensure that the data is not converted with the wrong code page.

 When a table has more than one LANG field, only one may be set. For tables with more than one LANG field, there are two possible options:

a. Either one of the LANG fields determines the code page of the data and the Text Lang. flag must be set for the correct field, or

b. neither of the LANG fields determines the code page of the data and the Text Lang. flag should not be set for either of the LANG fields

When RADNTLANG is finished, SAP recommends resetting all nametab buffers. Enter / $NAM in the transaction code field and press ENTER.

Transports into a system can cause the Text Lang. flag value to be overwritten. It is therefore necessary to (re)run RADNTLANG directly before the Consistency Check in order to

actualize the flags.

But note that the Text lang. flag maintenance must also be finished before the Consistency Check is started. If you do any changes as described in this section after the Consistency, you must reset the changed tables and rerun the Consistency Check for those tables.

After you have run RADNTLANG please read SAP Note 672835 carefully. You will find information about how to maintain special tables which could be affected by wrong data conversion after the Text lang. flag has been set.

1.7 Printing Old Spool Requests after the Unicode Conversion

After the conversion it will be problematic to print out spool requests which have been created before the conversion. There is no possibility to recover the spool requests after the Unicode conversion.

Read SAP Note 842767. You will find a step-by-step description on how to handle such spool requests before beginning the conversion procedure.

1.8 OTF Documents after the Unicode Conversion

OTF documents that were created before the Unicode conversion can not be processed after the Unicode conversion and they cannot be created again in the Unicode system. To save your OTF documents you can convert them into PDF using report

RSBCS_CONVERT_OTF_FOR_UNICODE. This report is delivered with SAP Note 1349413. Follow the instructions in SAP Note 1349413 BEFORE beginning the conversion procedure.

1.9 Translation Environment

If you use the SAP translation environment (transaction SE63) you must export the Proposal Pool in the non-Unicode system. When the Unicode Conversion is finished, you must import the Proposal Pool into the Unicode system (see chap. 4.Unicode Conversion Completion. Follow the instructions in SAP Note 1055820, scenario 3.

2. Unicode Preconversion Phase

Database Check

SPUMG is used to prepare the database tables of a non-Unicode system for the conversion to Unicode. All steps in the Unicode Preconversion Phase are designed to be run at system uptime (i.e. when users are logged on to the system). The system conversion is carried out by the separate tool R3load [page 26] during the database export. R3load uses the results of SPUMG which are stored in the Export Control Table and the Language List [page 22]. Note: It is only possible to perform the data conversion during the export phase!

2.1 SPUMG

2.1.1 Restart SPUMG

It is mandatory that all data are completely deleted before starting the database check! Go to Scanner  Restart SPUMG.

After a restart, you will be displayed the entrance screen of SPUMG. All data which might have been already entered in SPUMG are now deleted.

2.1.2 Welcome to SPUMG

The entrance screen is divided into two sections. In the upper section you will find general information and a couple of links to Unicode information sites.

In the lower section there are three pushbuttons with additional Info buttons. Each pushbutton triggers a mandatory action to be performed before the worklist for the Consistency Check can be initialized. The checkbox Would you like to replace code page

1100 with 1160 in the Language List can be optionally selected in case the frontend code page 1100 has been used with system code page 1100.

The last pushbutton Continue with transaction SPUMG will trigger the automatical initialization of the Language List and lead to the Consistency Check screen.

2.1.3 Exception List

The Exception List contains SAP delivered tables which store data from only one language, for example tables with only Japanese or only German data.

The exception list is provided as XML file attached to SAP Note 996990. You must upload this file once. Select Download Exception List from note 996990 and save the XML file to your local PC.Then select Update the SPUMG exception tables and upload the XML file. You can display the content via Exception List  Default Exception List after the Consistency Check has been executed.

This list of tables is predefined by SAP. In principle it is possible to add or remove tables from the Exception List, but it is not recommended to change the default content in Single Code Page systems.

You can proceed after the confirmation message Upload of exceptions successfully finished is displayed.

2.1.4 Additional Preparation Steps

Select pushbutton Start additional preparation steps. Report UMG_ADD_PREP_STEP [page 42] will be initiated which consists of several reports which were created for deleting corrupt or obsolete table data prior to Unicode conversion. On the next screen the included reports are displayed. Choose Background. All reports will be executed automatically in sequential order.

Note:

You cannot proceed with SPUMG until you have executed UMG_ADD_PREP_STEP once using the background option. It is possible that some reports included in

UMG_ADD_PREP_STEP are not available in the system.

In this case, check whether you can implement them with SNOTE. If the corresponding software components do not exist in your system you can proceed with SPUMG. If you need to rerun one or more selected reports later, you can use button . It is not possible to use this option before UMG_ADD_PREP_STEP has been run using the background option.

Report name Software _Component What does the _report? SAP _Note /BEV1/CA_DEL_OBSOLETE_BEV1 EA-APPL Delete entries from tables /BEV1/, /DSD/

and /VSO/ 897577 /BEV1/CA_DEL_OBSOLETE_BEV3 EA-APPL Delete entries from_{/BEV3/ tables} 897577 AGR_MASS_STAR_0_PROBLEM SAP_BASIS Delete entries from

USR11, USR12 and USR13

BVED_SRV_917_UCD_DE2EN

EA-APPL Overwrite German program names in table /BEV2/ED917 with English text

1274744

COR_SODI_UNICODE SAP_BASIS Delete entries from ADRC from group

SODI 712619

CY_TCYD_UNICODE SAP_APPL Delete entries from _{table TCYD} 899931

DELETE_T059U SAP_APPL Delete inconsistent entry from table

T059U 1274945

DMS_DELETE_CORRUPTDATA_TDWD SAP_APPL Delete entries from _{Table TDWD} 991541

ECATT_CONV_XMLDATA2XSTR

SAP_BASIS Convert XML data from EC* tables from CHAR-based file format to binary format

1153130

EFG_CLEAR_TEXTFIELDS

SAP_ABA Delete entries from tables EFRM, EFRMSTR, EFCL, EFCLSTR,

EFG_COLLECTION

1312757

GRIX_DELETE_RW_EXTRACTS SAP_APPL Delete extracts for _{Report Writer} 892607

G_CORR_BAJP_IN_SETHEADERT

SAP_APPL Delete entries from table SETHEADERT with subclass = BAJP 1259178 HARUT720 SAP_HR/ SAP_HRCAR (in EhP applications)

Delete entries from

T7AR72 1101259

INDX_IW_DELETE SAP_BASIS Delete entries from table INDX (RELID =

IW) 1292125

INDX_KC_DELETE SAP_ABA Delete entries from _{table INDX} 1055431

INDX_KE_DELETE SAP_APPL Delete entries from table INDX (RELID =

KE) 1318670

INDX_KU_DELETE SAP_APPL Delete entries from table INDX (RELID = KU)

1302042

INDX_PC_PE_DELETE

SAP_BASIS Delete entries from table INDX (RELID =

‘PC’ or ‘PE’) 1089012

INDX_PR_DELETE SAP_BASIS Delete entries from

PR)

INDX_SEM_DELETE

SAP_BASIS Delete entries from table INDX (RELID = VM and RELID = RT)

1294414

INDX_SH_DELETE

SAP_BASIS Delete entries from table INDX (RELID =

SH) 989070

INDX_SM_DELETE SAP_ABA Delete entries from table INDX (RELID =

SM) 977726

RGX_SETS_TO_40

SAP_APPL Delete entries from tables T800S, T800X, T800Y and SETDATA

928859

RFPAYM_UNICODE_VARIANTS

SAP_APPL Convert variants of program SAPFPAYM

(cross-client) 1388649

RISSR_DEL_ALL_ENTRIES_TZA11

Not known Delete entries from tables TZA11, TZR96 and TZR96A11

1364690

RISSR_DEL_ALL_ENTRIES_TZBAG Not known Delete entries from _{table TZBAG} 1364690

RPU470ADJUST_T52C5 SAP_HRRXX Delete entries from _T52C5 679275

RSBCS_SOER_REF_UPDATE SAP_BASIS Adjust records for table SOER in table ADRVP

1003800

RS_DM_CLEANUP_TDM_TABLE

SAP_BASIS Delete content from tables TDM10 and

TDM11 781211

RSDB4PREP_UCPC SAP_BASIS Delete entries from _{SQ* tables} 932034

RSSCD_CHECK_OLD_ENTRIES SAP_BASIS Delete entries from _CDPOS 1096470

RSSPAM_PREPARE_UC SAP_BASIS Delete content of _OCSCMPLOBJ 889596

RSTXCLEARTTDTG SAP_BASIS Delete entries from _{table TTDTG} 992857

RS_DELETE_VARIANT_SPACE SAP_BASIS Delete empty entriesfrom table VARI

(RELID = 'VX') 1132850 RS_FILL_TRDIR_RLOAD SAP_BASIS Fill REPOSRC-_RLOAD 684332

RS_SCRP_D020S_CLEAN

SAP_BASIS Delete screen source codes with invalid keys from tables D020S and DYNPSOURCE

870601

RS_TESTREPORT_DELETE_ONLINE SAP_BASIS Delete old test

builder

RS_TEST_REPORT_GENERATE_JOB SAP_BASIS See relevant SAP _Note 931824

RS_TPARA_PARTEXT_CLEAN SAP_BASIS Delete entries from table TPARA in field

PARTEXT 1256148

RUTDD07TLA SAP_BASIS Delete entries from _{table DD07T} 1275254

SAPRSEUG SAP_BASIS Delete entries from _{table RSMPTEXTS} 542302

SDBI_POOL_CLEANER SAP_BASIS Delete entries for TCP00, TCP01 or TTDCF from ATAB

920138

SEO_CLEAN_TYPESRC

SAP_BASIS Correct entries in table SECOMPODF (fields TYPESRC and TYPRSC_LENG

1164530

SIAC_DELETE_INVALID

SAP_BASIS Correct characters in IACSERVP and IACS_C; Obsolete entries in IACMIMEL 862196; 1345033 STSTCP_REPAIR SAP_BASIS Delete entries from _TSTCP 897002

TERM_DELETE_INCORRECT_CHARSET

SAP_BASIS Delete erroneous terminology and glossary text from STERM_TEXT

1280494

If the system code page is 1100 you should check whether the frontend code page (or SAP GUI code page) is also 1100. Run report RSCP0013 in transaction SE38 and check, if 1100 is displayed in field Character set of SAPgui. If yes, users are able to input characters which are not covered by the system code page. Such characters – for example the Euro sign - will get lost during the database conversion because they are not stored on the database. You can prevent this at least for characters in transparent tables by switching to 1160 in the SPUMG Language List.

Select checkbox would you like to replace code page 1100 with 1160 in the Language List? Note that there is no automatical replacement option for other code pages than 1100. Afterwards choose pushbutton Continue with transaction SPUMG.

You are now on the tabstrip Consistency Check. The Language List is now initialized and filled, and the default settings for SPUMG are set.

2.1.5 Language List

All languages which are productively used in your system are now inserted in the Language List as active languages in conjunction with the system code page. All other languages (i.e. languages which are supported by SAP) are inserted as inactive languages. The reason is to ensure that R3load uses the correct code page for languages which are not installed in the system but nevertheless occur in tables with language information.

Select Edit  Language List from the SPUMG menu, and check whether all productively used languages are marked as active languages. If you are not sure which languages are productively used in your system, do the following:

Call SE38, enter report RSCPINST and press F8. On the next screen select Current NLS config to display the current i18n settings. In the following section the language keys of all productively used languages are listed:

Database table entries  TCP0I Processed language(s) entry

Systems with Code Page 8340

If you use code page 8340 (Traditional Chinese HKSCS Vers.1) in your system, you must perform additional preparation steps as described in the supplementary documentation “Conversion of HKSCS Systems to Unicode”. Download from SAP Note 551344.

Systems with Code Page 8300

Depending on font and input method it is possible that HKSCS characters have been entered in systems with code page 8300 (Traditional Chinese Big5, based on MS CP950). If this is the case, proceed as described in section Systems with Code Page 8340.

2.1.6 SPUMG Settings

Depending on the system type the settings for the database check have different default values. These default values are described in the F1 help documentation of each input field. To access the SPUMG Settings select Scanner  Settings. In general, SAP recommends that you keep the default values.

There are cases where you should change the default value of the Global Fallback Code Page. For example:

 If you have replaced code page 1100 with 1160 on the SPUMG Welcome Screen, you should change the Global Fallback Code Page from 1100 to 1160.

 If the system code page is 1610, apply SAP Note 1459066.

All code pages which are used for the conversion must be roundtrip compatible. This means that a roundtrip conversion (for example: 1160  Unicode  1160) must be possible. Therefore the system executes a roundtrip compatibility check when you enter a new Global Fallback Code Page.

2.1.7 Initializing the Worklist

Select Scanner  Initialize  Worklist. Depending on the data volume the initialization job may take several minutes. Select . You have generated the worklist for the Consistency Check.

The worklist of the Consistency Check (CC worklist) contains a list of all tables taken from the database’s nametab. By default, only 200 entries are displayed. To increase the number of entries that are visible in the ALV Grid, select Selection from the toolbar and increase the number of lines.

Caution

Tables added to the database (Transports, Support Packages, etc.) are not automatically inserted into the CC worklist. Update the CC worklist regularly. You can find more information in section SPUMG Updates [page 26].

Select Scanner  Update Worklist.

SPUMG Main Log

Check the main log regularly. Select Scanner  Main Log from the menu bar.

2.1.8 Consistency Check

Select Schedule Worker Jobs from the toolbar, and then set the time and date for the worker job. You can run multiple jobs simultaneously, but you must add a suffix to the second and all subsequent jobs.

Recommendation

Use the following naming convention: <run><scanlevel><job>. For example 1cc2 is the second job of the first run of the Consistency Check.

Select Monitor from the toolbar.The scan is finished when the number of initial tables and tables in process is 0.

Mandatory: Check if tables with status ‘Error’ exist and correct them as described below:

Choose Selection from the toolbar, and in the field Status enter the value ‘E’. Select to show additional information, including the message type (field Msg.type).

Message Type: Database consistency

Msg.Type Definition Description/Correction Steps 1 Table definition contains

errors The table definition is incorrect. A nametab entry may exist, but it is not defined in the ABAP Dictionary.

Display the table in SE11. In the SE11 menu, select:

1. Utilities  Database Object  Check. 2. Utilities  Runtime Object  Check.

If one or both checks show inconsistencies, try to correct them, for example by activation.

more, you can ignore the SPUMG error message. Other options:

If the table itself is obsolet, you can also delete before the conversion. In this case, delete the table from the database using SQL statements and then delete the table entry from nametab tables DDFTX, DDNTF, DDNTT on database level and reset the table in the CC Worklist.

2 A background job was

canceled The background job which processed the table was canceled. Possible reasons: 1. A user canceled the background job

manually or

2. the table cannot be accessed from ABAP via OPEN SQL or

3. the application server was shut down abnormally

What to do?

1. Examine the table in transaction SE11. In SE11 menu select

a. Utilities  Database Object 

Check.

b. Utilities  Runtime Object 

Check.

2. Look for short dumps in transaction ST22. If the background job was canceled with a short dump, you might find the reason in the long text of the short dump.

3. Look in the system log in transaction SM21.

If you have removed the cause of the error, you can reset the table in the CC worklist and schedule a new worker job.

Double click on the table name in the list to see a detailed description of the inconsistency and how to handle the error.

Note

When a job is interrupted, one or more tables may have the status “in process” even after all tables have been completed and all jobs have been completed. Select Selection from the toolbar and then select all tables with the category “P”. The worklist will then contain only those tables that are in process. Select the tables and then select from the toolbar.

Read SAP Note 33814 for general information about inconsistencies between database and data dictionary.

Resetting Tables in the Worklist of the Consistency Check

Select the table(s) you want to reset and then select in the toolbar.

Result:

The tables have status INITIAL again. They are deleted from the Export Control Table but not from the Worklist of the Consistency Check.

Note

Tables which have been deleted from the database are automatically deleted from the CC worklist.

How to exclude tables from export

It is not possible to exclude a table from the export by adding it to the Exception List. The table will be automatically entered in the Export Control Table and therefore still be exported.

Note

If you want to exclude a table from export after the Consistency Check, you must: 1. Drop the table from the database

2. Delete the table entry from the nametab tables DDFTX, DDNTF, DDNTT on database level 3. Reset the table in the Consistency Check (see section Resetting Tables in the Worklist of the Consistency Check [page 26])

2.2 Final Preparation Steps

2.2.1 SPUMG Updates

If there is a time difference between the scan and the database export, it may happen that a new table has been created or a Support Package has brought a new table with it. In such a case, the preconversion must be rerun right before the export is carried out to ensure that the data change is reflected in the Export Control Table.

Proceed as follows:

2. Select Monitor from the toolbar. The Monitor will show you if new tables were added to the system. Those tables have the status “Initial”. For those tables the Consistency Check [page 24] needs to be run.

3. Select Scanner  Update Log.

After you have updated the worklist, this log displays all tables which have been added or changed after the consistency check. You can now reset those tables in the worklist of the consistency check and rerun the consistency check. Afterwards, the resetted tables will be removed from the log.

2.2.2 Check Matchcode IDs

[This section is only required for Support Packages lower than SP22. With SP22 and higher, TWTOOL01 is included in report UMG_ADD_DOWNTIME_STEPS.]

Run report TWTOOL01 again to check whether there are still existing active matchcode IDs. If yes, proceed as described in chapter 1.4 Delete Matchcode IDs [page 14].

Note:

Do not start the export before all matchcode IDs have been deleted! Run this report until message “Check successful, no action necessary” is shown!

2.2.3 Nametab handling

1. Delete entries from DDNTF_CONV_UC and DDNTT_CONV_UC: Delete the table entries on database level.

2. Create the nametabs. Caution

Do not import new DDIC objects or modify existing DDIC objects after you have created the Unicode nametabs and before the export of the database! Otherwise the nametabs will become invalid!

In SPUMG select Extras  Unicode Nametabs  Create Unicode Nametabs from the menu. A report is automatically started in the background with variant UNICODE-02-CRE. This variant creates the Unicode nametab.

If you try to repeat this process in SPUMG, you will receive a system warning. If you ignore this warning, SPUMG will automatically use variant UNICODE-02.

After having created the nametabs select Extras → Unicode Nametabs → View log of RADCUCNT from the menu. Check the log carefully. If you ignore errors, the import will not succeed and you will have to repeat the conversion procedure.

Nametab creation may produce messages due to old DDIC inconsistencies. Check the following SAP Notes for help:

1428028 Unicode Conversion: check nametabs report UMG_CHECK_NAMETABS 932779 Unicode conversion - analysis of nametab problems

765475 Unicode Conversion: Troubleshooting

Correct all errors.

3. Afterwards you must create the missing nametabs for the corrected objects. Repeat the procedure described in step 3.

4. After the nametabs have been successfully created, you should update the database statistics for the alternative active nametabs DDNTF_CONV_UC and DDNTT_CONV_UC in order to improve the performance of the R3load export procedure.

Perform the statistics update on database level. You can expect a runtime of at least several minutes.

2.2.4 Tables with obsolete data

[This section is only required for Support Packages lower than SP22. With SP22 and higher, skip this section and perform the steps described in 2.2.5 Additional Downtime Steps instead.]

The following tables need special treatment directly before the database export (not during system uptime!).

Proceed as described in the corresponding SAP Notes in column More information. Do not maintain the tables manually!

Tables Method More

information DDSHPVAL50

Personal Help Values

You cannot use personal value lists from table DDSHPVAL50 and generated selection reports (namespace /1BCF41/) of the input help (F4) after a Unicode conversion. You must delete them before the conversion and create them again in the Unicode system during runtime.

Use report UMG_F4_CLEANUP according to SAP Note 1275149.

1275149

GREP

Report Writer: File of Stored Reports

After a Unicode conversion, extracts for Report Writer reports can not be used anymore. Extracts should be deleted before the conversion to avoid converting data unnecessarily.

837184; 892607

GRRT

Report Writer: Runtime information for generated programs

To avoid converting data of table GRRT unnecessarily, the generated programs can be deleted with report RGRDLINC.

837184

REPOSRC

Report Source Code

Use report UMG_F4_CLEANUP only! Do not maintain the table manually!

1275149

TADIR Directory of

Repository Objects

Use report UMG_F4_CLEANUP only! Do not maintain the table manually!

1275149

TST01, TST03 TemSe: List of objects and parts; TemSe data

After a Unicode conversion, the RSPO1043 report terminates with the FB_RSTS_NOCONV dump. RSPO1043 stores inconsistencies in a special TemSe object. The error occurs if you attempt to read this TemSe object, which was created before the Unicode conversion, in a Unicode environment.

Run report RSTS0023 according to SAP Note 991122.

991122

VBDATA, VBHDR, VBMOD

Update data, Update header, Update function modules

Update Requests should be checked and maintained before the database export to avoid converting data unnecessarily.

Run report RSM13002 according to the documentation of the report.

67014

2.2.5 Additional Downtime Steps

Note: This report is available with SP22 and higher. If your system is on a lower SP level, follow the steps in chapter 2.2.4 Tables with obsolete data.

Make sure that the system is in business downtime now, i.e. no users should be working in the system. Then go to SPUMG menu  Extras  Additional Downtime Steps.

Report UMG_ADD_DOWNTIME_STEP will be opened automatically. This report consists of several reports which were created for deleting table data which will be obsolete after the Unicode conversion or maintaining data to make them usable after the conversion. On the next screen the included reports are displayed. You can run single reports by choosing . If you choose Background, all reports will be executed automatically in sequential order. Note:

All included reports must be executed and the log of each report must be checked for errors. Correct all errors before you start the database export. Otherwise either the database export or the import might fail including the risk of data loss.

Report Tables More information

TWTOOL01 695196

UMG_F4_CLEANUP DDSHPVAL50, REPOSRC, TADIR

(personal value lists and generated selection reports (namespace / 1BCF41/) of the input help (F4) are deleted)

1275149

RSTS0023 TST01, TST03 991122

SAP_DROP_TMPTABLES /BI0/0*

(BW system conversion: Temporary database objects)

449891 1701123

UMG_CLEAR_SVER_TABS TATGPC, TATGPCA 1429068

RSLANG20 DDFTX, D020L, D020LINF, DYNPLOAD, D021L, D021LINF, DYNPTXTLD, D345T, D346T, D342L, TTREELOADT, LTDXT 110910 UMG_DELETE_SSLOAD TCP00, T000, STXL 1132495

UMG_CHECK_APPLICATION_TABS The following tables are checked: TICNV, HRPADNN, GRRT, VBDATA, VBHDR, VBMOD. If the check reports errors or warnings, the tables must be handled as described in SAP Note 1429935.

1429935

UMG_CHECK_NAMETABS 1428028

UMG_CHECK_NAMETAB_TABS DDXTF_CONV_UC,

DDXTT_CONV_UC 1426513

3. Unicode Conversion Phase

Program: R3load

The default conversion procedure is to export the entire database using SAPinst (which controls R3load), create a new Unicode database, and then import the database using SAPinst again (internally R3load). You can choose either the “Two Server Method” which is recommended. In this case you build the Unicode database on an additional server. If you choose the “One Server Method” you must delete the non-Unicode database before. In fact you perform both a system copy using SAPinst (as described in the relevant System Copy Guide mentioned below) and simultaneously a database conversion to Unicode. The conversion is performed by R3load during the export procedure. For building the Unicode system you use the export files generated during the export procedure instead of the export media provided by SAP.

Note

You can choose either the homogeneous or the heterogeneous system copy method. If you want to perform a database or platform change during the conversion process, choose the heterogeneous system copy method.

Documentation:

For this chapter you must use the System Copy Guide in parallel. You can download the valid System Copy Guide for your release from www.service.sap.com/instguides.

Downtime Estimation

If you want to gain a rough estimation of the expected system downtime, run report UMG_R3LOAD_RUNTIME_PREDICTION in transaction SE38.

In addition SAP Note 857081 provides information about methods and tools for optimization of the export and import procedure.

Do not delete non-Unicode system immediately after the import

After both export/conversion and system copy has been successfully completed, SAP recommends keeping the non-Unicode system for the duration of the testing period of the Unicode system. Afterwards the non-Unicode system can be deleted using the standard procedure.

IBM DB2 UDB for UNIX and Windows: Tablespace sizes for conversion Unicode - non Unicode

To get the appropriate tablespace sizes for IBM DB2 UDB for UNIX and Windows, install R3szchk BEFORE the conversion. You can download from SAP Service Marketplace at service.sap.com/patches <your product> <your release> → Binary Patches. To avoid wasting space in your DB2 UDB for UNIX and Windows tablespaces we strongly recommend that you create all tablespaces in the target database with extentsize 2.

Note:

This is not the default for all SAPinst releases up to and including SAP NetWeaver 2004 SR1. You therefore need to manually adjust the extentsize in the SAPinst tablespace dialogs. The pagesize for a unicode system should be 16K as proposed by SAPinst.

3.1 Database Export and Import

The following section describes the R3load copy procedure of non-Unicode system to Unicode system.

Make sure that all required CDs/DVDs are available now as described in section Software Requirements in this document [page 9].

Import the latest SAP Kernel patch as described in SAP Note 19466 and the applicable R3load version.

Requirements: Use the latest R3load version and the latest version of R3ldctl and R3szchk for your release

Documentation: - this document

- System Copy Guide for your release. The System Copy Guides can be downloaded from:

http://www.service.sap.com/instguidesNW70

For detailed information about optimization of the system copy procedure go to https://service.sap.com/systemcopy -> optimization.

Status: required.

Perform the export from the non-Unicode system (source system), install the target system and import the database files that you have exported from the source system as described in the System Copy Guide:

“Homogeneous and Heterogeneous System Copy for SAP Systems Based on <RELEASE>” Section: System Copy Procedures on <OPERATING SYSTEM>”

It is not possible to perform the Unicode conversion during the import! Make sure you convert the MDMP data during export phase by calling R3load with parameter '-datacodepage 4102' or '-datacodepage 4103' (details see section 3.1.1 Database Export).

Read section Software Requirements [page 9].

Unicode Conversion with database change: Important information for Informix databases

If you plan to convert an Informix database, follow the instructions in SAP Note 811431 BEFORE the database export!

IBM DB2 Universal Database for iSeries:

Before starting the installation, follow the instructions in SAP Note 1158503 “iSeries: Setting environment Variables for SAPinst”.

3.1.1 Database Export

1. Perform the necessary preparation steps before starting SAPinst.

2. Read the document “Unicode Conversion: Tips and Tricks for Improving the Conversion Time”.

3. Perform the database export in the non-Unicode system (source system) as described in the relevant section of the System Copy Guide: Running SAPinst to Export the Database.

4. When running SAPinst to export the database and SAPinst prompts for General Export Parameters  Data file code page make sure the code page of the target system depending on the byte order of its CPU is entered (see SAP Note 552464):

 If the target platform (e.g. Linux, OSF1, NT) uses a little endian CPU (e.g. Alpha or Intel CPU), enter 4103.

 If the target platform (e.g. HP-UX, AIX, SunOS, OS/390) uses a big endian CPU (e.g. Sun SuperSPARC), enter 4102.

Caution

Be aware that this parameter depends on the processor architecture, not on the operating system.

Make sure that the most recent non-Unicode R3ldctl (SAP Kernel) is used for the export.

Note the additionalinformationfor the Unicode Conversion during the export of the database:

Server Necessary Steps Further Information

MS SQL Server only During the installation, the collation setting must be fixed.

See SAP Note 600027

Oracle only When running SAPinst to export the database and SAPinst prompts for Database Instance Parameters  General Settings  Database character set make sure the character set of the source database is entered (e.g. UTF-8, WE8DEC or US7ASCII).

See System Copy Guide, sections Input for Exporting Your Database

All servers During the export of the source system R3load writes log files into the installation directory of the source system. The file names are like SAP*.log for example SAPAPPL2.log. If you create own packages for the files, the file names are like <TABLENAME>*.log.

The SAP*log files or <TABLENAME>*.log files should be saved for later error analyis.

R3load Log Messages

Type

Error Error from: Codepage handling (RSCP) | code: 128

<table_name> ‘No such object, Row not found’

This error can occur when a new table was added to the system.

Update the worklist and execute step 2 for table <table_name> (see section SPUMG Updates [page 26]).

Read SAP Note 33814 for details. Error Received return code

2048 from rscpMCStartTab This error might occur when table clusters and cluster tables have different language information.

Check entries in the Export Control Table. Make sure the field Codepage Recognition is not empty and also check the fields Lang. Fld. And Lang. Pos. Error Error when retrieving

physical nametab for table <table name>

Error during Export: The Unicode nametab has not been created or there have been errors during the creation.

If this message occurs

repeatedly, go back to transaction SPUMG and create the Unicode nametab (again) (see chapter Nametab Handling [page 27]). SAP Note 932779 describes basic information about how to analyse nametab problems. Error during Import:

R3load performs a data conversion and cannot read the nametab. It could be one of the following conversion types: a) The conversion from a non-Unicode to a Unicode code page was performed.

b) The endiannes has changed (4102 <-> 4103).

a) The conversion to Unicode should always be performed during the Export, repeat according to chapter Database Export [page 32].

b) Make sure that the R3load package containing the nametab information is imported first.

Error Error from: Codepage handling (RSCP) code: 32 RSCPETOOLONG The data was longer than the buffer.

langMBCPMap: no c.p. assigned

module: rscpmi no: 15 line: 2060 T100: TS006

TSL01: F44

R3load tried to find a pool table which does not exist in the ABAP Dictionary.

This error occurs when the Consistency Check shows error message type 8 “Illegal pool table values” and report UMG_CHECK_POOL has not been run.

Run report UMG_CHECK_POOL [page Error: Reference source not found].

Error R3load terminates during export of single code page system

Read SAP Note 718329 for correction instruction.

Error (EXP) ERROR: <object name> missing in DDNTT_CONV_UC

R3load could not find the Unicode nametab for object <object name>

Ignore this error by setting the environment variable

I18N_NAMETAB_TIMESTAMPS = IGNORE as described in SAP Note 738858.

Warning UMGSETTINGS says:

RADCUCNT not succesful R3load notices if the Unicode nametabs have been created by SPUMG option, but not the execution with SE38 and therefore triggers a warning.

Ignore the message in case the Unicode nametabs have been created via report RADCUCNT in SE38. Otherwise start the Unicode nametab creation via SPUMG option

3.1.2 Transfer Files to Target Host

Perform the file transfer as described in the relevant section of the System Copy Guide: Transferring the Files to the Target Host

Caution

During the change, the syslog files are not converted to Unicode. To handle this problem follow the steps described in SAP Note 688089.

3.1.3 Database Import

Install the Unicode system (target system) as described in the relevant section of the System Copy Guide: Installing the target system

Note the additional information for the installation of a Unicode target system:

Issue Necessary Steps Further Information

Hardware resources When planning the installation of the target system, be aware that Unicode systems require additional hardware resources. Unicode SAP systems require approximately 50% of additional RAM.

SAP Service Marketplace: service.sap.com/unicode. SAP Note 790099.

R/3 Parameter Settings When installing the Unicode system you might want to adapt your R/3 Instances memory configuration (increase current buffer settings and memory parameters).

Read SAP Note 790099 for details.

Conversion from

only you have to adapt the tablespace sizes before the import by editing the file DBSIZE.XML.

Path: Export Folder

/DB/ORA/DBSIZE.XML

following rows.

DB6 only If you import into a DB2 UDB for Unix and Windows (DB6)

database, you have the following choice:

a. use the tablespace dialogs in SAPinst to adjust the tablespace sizes or

b. edit the file DBSIZE.XML.

Oracle only 1. If the file DBSIZE.XML only contains the SAP tablespaces

PSAP<SAPSID>, PSAP<SAPSID><RELEA SE> and

PSAP<SAPSID><USR>, increase the size of tablespaces SYSTEM, PSAP<SAPSID>, PSAP<SAPSID><USR> by 50% and the size of tablespace

PSAP<SAPSID><RELEA SE> by 100%.

2. If the file DBSIZE.XML also contains the ‘old’ tablespaces

PSAPBTAB{D,I},

PSAPSOURCE{D,I} etc., increase the size of tablespace

PSAP*<RELEASE>{D,I} by 100% and the size of all other tablespaces (excluding PSAPROLL and PSAPTEMP) by 50%.

During the installation of the new target system the old tablespaces are inserted into a smaller number of new tablespaces automatically, and the system will be installed with the new tablespace layout.

It is therefore not necessary to change the size of every single tablespace in DBSIZE.XML. This is especially valid for those tablespaces which are sources for the tablespace PSAP<SCHEMA-ID>620. If the sum of all required tablespace extensions is known, it is sufficient to extend one of the source tablespaces by this sum. See SAP Note 425079 for details.

Example:

If each of the tablespaces PSAPEL620D, PSAPEL620I, PSAPES620D and

PSAPES620I has to be extended by 100MB, it is sufficient to extend only one of them by 400MB in DBSIZE.XML.

During the tablespace layout change from PSAPEL620D, PSAPEL620I, PSAPES620D

and PSAPES620I in the source system to

PSAP<SCHEMA-ID>620 in the target system this last tablespace will become 400MB larger than the sum of the source tablespaces. Installation of Instances To install a Unicode central

instance, database instance or dialog instance, select Unicode <SAP Component> for

<Database> instead of <SAP Component> for <Database> in the installation tool SAPinst.

SAP Note 790099.

Conversion from non-Unicode to non-Unicode on MS SQL Server only

If SAPinst fails while trying to start the RFC jobs as SAPinst used the standard DDIC password

‘19920706’ instead of the

password you have entered in the corresponding SAPinst dialog, press RETRY and enter your DDIC password once again.

3.2 Follow-Up Activities

1. Perform the follow-up activites in the source system and in the target system as described in the System Copy Guide for your release.

2. Afterwards perform the completion steps in the Unicode system listed in the following chapter.

4. Unicode Conversion Completion

Phase

This section describes the steps which have to be performed in the Unicode system after the conversion and import of the database has been successfully completed.

Log on to your Unicode system.

Additional Post Conversion Steps

Go to transaction SE38, and execute report UMG_ADD_POST_STEP. This report consists of several reports which were created for saving the conversion history (logs, settings, language list, etc.) adjusting of settings, tables and RFC destinations, and for deleting obsolete table entries after the Unicode conversion. On the next screen the included reports are displayed. If you want to start all reports simultaneously, choose Background. If you want to run one selected report, mark the report and choose .

Note:

Depending on your support package level it is possible that some reports included in UMG_ADD_POST_STEP are not available in the system.

In this case, check whether you can implement them with SNOTE. If the corresponding software components do not exist in your system you can proceed with the next step.

Report Action SAP Note

UMG_SAVE_HISTORY Save and display data from SPUMG and SUMG

1128457

UMG_POOL_TABLE

Table pools which have been entered in UMGPOCNV during the Consistency Check are copied to table DDTPOOLCNV. Then report RADPOCNV enlarges the VARDATA fields of the table pools.

813445

UMG_ADJUST_I18N_SETTINGS

Update the I18N System configuration: Empty table TCPDB and adjust the country code information in TCP0D according to.

1128673

UMG_DELETE_SSLOAD Delete SAPscript load _{from table STXL.} 1132495

RSWW_DEST_SET_UNICODE

Adjust the RFC destination of the SAP Business Workflow after Unicode conversion.

1112206

UMG_CHECK_STXL

Blended Code Page Conversion only: Adjust table STXL after Unicode conversion

1128672

RSWOGIND

Correct inconsistencies in the Business Object Repository

1293806

CATT_CONV_TABLES_IN_UNICODE Correct entries in tablesCATF and CATP (CATT objects)

1288872

1. Special handling of TLOCK* tables:

Run the correction reports as described in SAP Note 795871.