How to Set Up a Conversion Project
Planning, Timeline, Tasks
Conversion of a Non-Unicode System
Conversion of a non-Unicode SAP system requires solid planning. Such a project consists of different action 'blocks', all of which require different experts and have to be done at different points of time. A Unicode Conversion is a combined approach which requires SAP NetWeaver and Business Application specialists. Consider the following aspects when you are planning a conversion project.
- Identify language specialists for all used languages in case of MDMP and establish a proper project team with all parties included.
- In case of large systems, Conversion Downtime will be time consuming. Several runtime tests might be necessary.
- One important and effective downtime optimization method is to make use of new hardware (additional server) in order to export and import in parallel. Therefore you should acquire new hardware as early as possible.
- Archiving and data reduction can significantly reduce the Unicode Conversion effort. Analyze archiving options as early as possible.
- A Sandbox Environment is highly recommended. To test the conversion of your productive system you should use a sandbox system.
- An SAP certified Third Party Product does not mean that it automatically supports Unicode. Ask the vendor about Unicode compliance as early as possible.
- Have your experts analyze all Unicode - Non-Unicode Interfaces in detail.
- Only for MDMP Systems: Plan sufficient time for SPUM* Scans.
- Especially for MDMP Systems: Use the latest Basis Support Package level for your release.
This presentation (PDF) provides basic information for the conversion of a typical 3-tier system landscape. It includes a sample schedule, the most important factors that influence such a project, and also a recommended sequence of steps.