Unicode Preparation

DB Export 64 bit Non Unicode

DB Import / System Copy with Unicode

Post Unicode Conversion Activities

Unicode ConversionCheck Tcode Parameters Action

710

Preparation SMLT Check for the existence of Installed LanguagesSA38 RSREFILL Execute ( This will transfer the languages into the productive client

UCCHECK

Data Maintenance SARA Archiving the data - This step can be skipped

SNOTE Apply Note 712619 - Not required if Not an MDMP system

SA38 UMG_ADD_PREP_STEP

SE38

SNOTE Download Note 794966 Applied after Basis Pack 48 for release 6.20SA38 RSTXCLEARTTDTG Execute (This will clear the corrupt in the table TTDTG)SE14 Extras --> Invalid Tables

SA38

SE38 UMG_R3CHECK_FILES Read Note 89384

Consistency Check SA38 RUTCHKNT --> Leave the check box unselected Execute

SE14

Log on to Productive Client

ABAP Programs for Conversion

Choose Object type FUGS and select the check box modified SAP objects as well.

Execute (This execution may take sometime) This checks for the programs which are needed to be marked for unicode conversion

Pre-conversion Correction

Execute in Background(This report maintains the corrupt data in many tables before conversion)

Create Report RSTXCLEARTTDTG and save in the package STXD

Delete all which start with QCM (These are temporary tables created during a upgrade, they don't appear in the dictionary, if not deleted they make their appearance in the consistency check)

RADNTLANG --> Select Check box Activate Inactive Version

Execute the report in Background (This report sets the Text Lang field for the tables for conversion)

In the section Object Types for Checking Select Checkbox Tables

Copy & Execute (This checks the objects which are inconsistent. Most likely this report will return some tables which are inconsistent.)

In the section Select Objects by Name Select filed Table Category Click the arrow

Go to tabstrip Exclude Single values. Choose Multiple Selection

Select INTTAB and VIEW and Enter

Enter the object name (Returned in the earlier check)

Extras --> Runtime Object --> Check ( An error is displayed stating why the object is inconsistent) if the object is not in the dictionary activate the object. If the objects are not found in the DB but they exist in Dictionary, they can be ignored.

SPUMG Scanner --> Reset all scans

Edit --> Language List. Change all entries which are 1100 to 1160Scanner --> Initialize --> Language ListScanner --> Settings Global Fallback Code Page 1160 & Save

This initializes all the tables which are required to be converted into Unicode

When the initialization is complete Scanner --> Update WorklistSPUMG UMG_PMIG_WORKER_JOB Click on Scheduled a Worker Job --> Specify the period to run JobSPUMG Scanner --> Update Log

Using SQL Query

SA38 TWTOOL01 & Execute

SA38 Using Variant UNICODE-02-CRE for the first time

932779

After successful completion

SA38 UMG_SHOW_UCTABS

Delete using SQl Query

SE11 If any adjust them.

SA38 Execute ( This creates the nametab for the specified table)

SA38 Execute ( This creates the nametab for the specified table)

Using SQL Query

SE11

Unicode Preconversion Phase

Scanner --> Initialize --> Work List (This step takes a long time) You can monitor the progress by clicking on monitor and refresh

You will see all the tables in the consistency check tab are set to status INITIAL

Additional Preparation Steps

Delete entries from tables DDNTT_CONV_UC and DDNTF_CONV_UC

Keep repeating the check until Check Successful, no action necessary is displayed.

RADCUCNT & Execute (This report creates the nametabs required for conversion) Using Variant UNICODE-02 for all the subsequent times if not successful

the first attempt

Specify a path for the log file as it is very important to read the log afterwards.

F:\Temp\Radcucnt.log (Check the log file for any errors. If any error says, Nametab could not be created it could be ignored, if anytime runtime errors are available try activating the objects as suggested earlier.)

Other error could be analysed with the note

Should not display any tables ( If it displays any tables run the consistency check using SE11 and deal with the tables accordingly)

Make sure tables DDXTT, DDXTF, DDXTT_CONV_UC, DDXTF_CONV_UC are empty before you proceed

Check DDXTT, DDXTF tables. There should not be any errors displayed.

RADCUCNT --> Generation for Single Object Type TABL Name DDXTT_CONV_UC

RADCUCNT --> Generation for Single Object Type TABL Name DDXTF_CONV_UC

Delete all entries for the tables DDXTT_CONV_UC, DDXTF_CONV_UC

In Table TRMTRA, If any entries exist SA38 --> RS_TRANSLATION_EXPORT_OLD_PP

Source Lang *, Target Lang *, Directory F:\Temp, File Translation

SE11

If no entries SA38 --> RS_TRANSLATION_EXPORT_PP

Database Export & ImportPhase Parameters Action Values

Screen Choose Service Choose SAP 4.7 Non-unicode Export DB-->

Screen General ParametersProfile Directory \usr\sap\D11\sys\profile

Screen Windows Domain Choose Local Installation

Screen PasswordsPassword of sidadm d11adm

Screen Prepare DB ExportExport Location \Export

Screen Summary Start

After Successful CompletionScreen Choose Service Choose SAP 4.7 Non-unicode Export DB-->

Screen General ParametersProfile Directory \sapmnt\

Choose Local Installation

Screen PasswordsPassword of sidadm d11adm

Screen Prepare DB ExportExport Location \Export

Screen SummaryRevise

Next & Start

Run SAPInst

Run SAPInst

Select Check Box SAP System > Database Export

Select the Check Box Unicode Target System

Database Import

Database Export & ImportRemarks

Make sure that the mount point Export exists

After Successful Completion

This Export takes around 31/2 to 4 hrs.

This export preparation might take around 1 1/2 to 2 Hrs. So Please don't Panic.

Unicode Conversion CompletionCheck Tcode Parameters Action

SA38 UMG_HISTORY

SA38 UMG_POOL_TABLE

SA38 RUTTTYPACT

Enter the logname \Export\Rutttypact.log

SA38 RSCPINST --> Select the Installed Languages SimulateRSCPINST Activate

SE11 CheckSE14 --> Extras --> Runtime Object --> Check

SA38 HRUU_CONVERT_IN_UNICODE

If no entries SA38 --> RS_TRANSLATION_IMPORT_PP

SA38 UMG_SCAN_STATISTICS ExecuteFile containging R3load log names \Export\file_infoDestination \Export\Scan_statistics

Upgrade the Kernel with latest patch levelConfigure STMSRun Sgen

Conversion Completion Phase

Select the Displayed Item and SAVE

Execute (If Short dump does not occur the check is successful. Nothing would be displayed)

Execute in Background (It eliminates any inconsistencies in the Nametab dictionary due to conversion)

Table DDTPOOLCNVIf any tables are displayed in the check, check them for consistency and adjust if necessary

Deselect the Checkbox Test Mode and Execute (Some records become impossible to interpret after the conversion because of incorrect code page they are corrected with this report.

Import Proposal Phase

In TRMTRA table during Addl. Preparation steps If any entries exist SA38 --> RS_TRANSLATION_IMPORT_OLD_PP

Source Lang *, Target Lang *, Directory \Temp, File Translation

Generate text file, e.g. ‘file_info.txt’

During the export of the source system R3load writes log and xml files (xml files in MDMP Systems only) into the installation directory of the non-Unicode system. You copied those files (e.g.SAPAPPL2001.xml) to your new Unicode server

This file ‘file_info.txt’ should contain all names and complete paths of the SAP*.xml files and SAP*.log files (Export and Import)