Skip to Content

Basic Steps of a Unicode Conversion

I.Prepare The Non-Unicode System
Prepare the non-Unicode System as described in section: First Preparation Steps.
Perform the SPUMG scans and the language assignment as described in section: Advanced Preparation Steps.
Perform the final updates and create the Unicode nametabs as described in section: Final Preparation Steps.

II. Perform the System Copy
A Unicode conversion is done as part of either a Homogeneous or a Heterogeneous System Copy and Migration. After the preparation of the non-Unicode system is finished, you use SAPInst to create the system copy. During this process, the data is converted to Unicode by the Export/Import tool R3load. Unicode conversion can take place only while the data is being exported because R3load has to access the SPUMG results in the database. The data is saved in files with a platform-neutral format (file server). During the export, all of the data records are logged in XML files (R3load Log (XML files)), which must be checked later on in the Unicode system after the converted data are imported into the new Unicode database (see section Database Conversion).

III. Perform the Conversion Completion Activities
When your non-Unicode system was an MDMP system, you need to run transaction SUMG after the System Copy is finished: See section Conversion Completion with SUMG. For former Single Code Page systems, this step is not required.

Other (in many cases application-specific) post-conversion task are not covered by this overview. They are listed in the Unicode Conversion Guides in combination with the relevant release information, instructions and SAP Notes.

Back to Unicode Conversion Overview Guide

Former Member

No comments