SAP Basis Tech Supports

Symptom

***********************************************************************
* Conversion from non-Unicode to Unicode / *
* *
* *
***********************************************************************

Other terms

Unicode, Language support, non-unicode, homogeneous system copy,
heterogeneous system copy
Reason and Prerequisites

Additional Information
Solution

This note contains solution specific supplementary information about the conversion from non-Unicode to Unicode and about a system copy of a Unicode system (SAP systems based on WAS 6.x or higher).
The main steps are described in the “Unicode Conversion Guide” (abbreviated with “UCG” in this note). Please use that document as basis for the conversion. You can find this release and support package dependent document as attachment of the following SAP notes:
1. Single Code Page systems: SAP Note 10515762. MDMP systems: SAP Note 5513443. Combination with Upgrade via CU&UC: SAP Note 9287294. Combination with Upgrade via TU&UC: SAP Note 9596985.
Please note that these documents are updated frequently. Therefore download the latest version right before scheduling the conversion.
Conversion Method – General Description:
One conversion method is to export the entire database using R3Load, create a new Unicode database, and then import the database using R3Load again. In principle this method is a “Homogeneous System Copy” and in addition a Unicode conversion during database Export. SAPInst (which controls R3Load) is used as tool for the Export process. The Unicode conversion is done during the export of data. After the export (and the conversion) have been completed successfully, the new Unicode system can be built up on a new Server (”Two Server Method” – recommended ) or the whole Non-Unicode system can be deleted (in case of the “One Server method” ). The following creation of the Unicode system is very similar to the installation of an entirely new Unicode system. Instead of the export CDs provided by SAP you use the export files generated during the export procedure before. Incremental conversion (IMIG) for large systems is supported on project basis only (contact globalization@sap.com for more information). The rest of this note describes the standard conversion method.

6. Restrictions regarding Unicode Conversions for different SAP solutionsa) Important: Please have a look at note 738858 right before beginning with the Unicode conversion !!b) R/3 Enterprise 1.1 :
Conversion is generally supported. The installation DVDs / CDs can now be downloaded from the Service Marketplace.
In case of an Oracle db, you can convert the system also using note
857734 – then you do not need the packages mentioned above.
c) R/3 Enterprise/ECC 5.0/ECC 6.0 (”Conversion without MDS/IMIG and/or MDMP”) :
Unicode conversion possible without SAP involvement.
For ECC 5.0 and ECC 6.0 (Netweaver based releases)
you have to follow SAP notes 771209 or 888210.d) BW 3.5, ECC 5.0, ECC 6.0 and other Netweaver systems based on WAS 6.40 or higher:
See SAP notes 771209 for 6.40 based systems and 888210 for Netweaver 7.0 based systems.e) CRM 4.0 or higher:
Unicode conversions for single code page (Single Byte)
systems are released. Please also have a look at note 793546.
Unicode conversions for MDMP systems, Double Byte systems and
systems which need to interface to MDMP R/3 systems are still
based on project with SAP Involvement.
For CRM Unicode conversions please refer to collection note 902083 and references.f) SCM 4.X or higher:
Unicode conversion for single code page systems are released.
LIVE CACHE has to be treated as described in note 632357.
Please also have a look at note 842788.
BW specifics: See point 1.d)g) SRM 4.0 or higher:
Unicode conversions for single code page systems are released.
Unicode conversions for MDMP systems and systems which
need to interface to MDMP R/3 systems are still based on project
with SAP Involvement.h) R/3 Enterprise / SAP ERP 2004 based on MDMP or Ambiguous Blended
code pages:
Unicode conversion released – for minimum Basis Support package level see Unicode conversion guide. SAP involvement is still recommended. Especially in case of more
complex system landscapes, technically complicated languages (e.g. Asian languages, Hebrew … etc. !).i) SAP ERP 6.0 based on MDMP:
MDMP is not generally released for SAP ERP 6.0 !
Please have a look at notes 79991, 928729 and 896144.
Contact globalization@sap.com for more information.
j) MDS (IMIG) conversion for very large databases:
Unicode conversion based on project with SAP Involvement. Please have a look at SAP note 693168.k) For all “project based solutions”, please send a request to globalization@sap.com. Send the request AS EARLY AS POSSIBLE, ideally in the first planning stage !l) It is highly recommended to setup the Unicode system based on 64 bit platforms.7. Information about Unicodea) You can find more information about Unicode SAP systems in the SAP Service Portal at: http://service.sap.com/unicode and technical details under https://www.sdn.sap.com/irj/sdn/i18n –> Unicodeb) Please also have a look at SAP Notes 1319517 and 1322715.