Overview
Preparation
Determine target configuration
- Language Requirements
- Check Unicode availability of required components in the target release (SAP Note 79991)
- Determine hardware requirements for:
- Target Unicode systems (sandbox (SB1/2), DEV, QAS, PRD)
- Additional systems for conversion tests
- Possibility of keeping non-Unicode systems (one by one) until target systems are stable and no errors have to be tracked any more
- Available hardware for the distribution monitor
Create Inventory
- Current release, support package
- Current hardware
- Current database, operating system
- Current system landscape
- 3rd party software and tools
- C/C++ RFC clients
- Full list of interfaces
- Self-developed ABAP, user exits, modifications etc.
- Existing test plans/scripts, top transactions etc.
Collect required documentation
- Unicode Conversion Guide and referred SAP Notes
- Homogeneous and Heterogeneous System Copy Guide and referred SAP Notes
- SAP Note 548016 and related SAP Notes
Determine available manpower
- Database administrator
- System administrator
- Developer ABAP/C/C++
- Person responsible for data cleanup and archiving
- One native speaker per language for language assignment in vocabulary
- Persons conducting test in Unicode system (ABAP programs, interfaces)
Locate and get required software
Apply required (recommended: latest) support packages to systems
Blueprint
Create detailed execution plan
Realization
Start data clean-up and archiving
DEV (Development System)
- Start ABAP Unicode-enabling (4 to 8 weeks including tests in the QAS)
- Do tests in the non-UC QAS before forwarding to PRD
- Do final tests in the UC QAS system (4 weeks)
- Run SPUMG Scans (1 week)
- Feed system with vocabulary and reprocess information from SB2
- Finish vocabulary maintenance (2 days)
- Convert the system (2 days)
- Post-conversion steps (SUMG, others ) 1 day
- Verify result (1 week)
- Drop old system
SB1 (Sandbox System 1)
- Create SB1 by copying the productive system (2 days)
- Run Consistency Check (1-2 days)
- Start exercising System Copy (6 weeks):
- Use Migration Monitor
- Use Distribution Monitor
- Check database tuning possibilities
- Repeat until downtime requirements are met
- In the meantime feed system with vocabulary and reprocess information from SB 2
- Use for as many test runs as you need to feel comfortable with the procedure
- Use SB1 for your first complete system conversion
- Perform last test run before conversion of the productive system
SB2 (Sandbox System 2)
- Create SB2 by copying the productive system (2 days)
- Run SPUMG scans (1-2 weeks)
- Maintain vocabulary, create and use hints for maintaining the vocabulary (4 weeks)
- Run reprocess, maintain reprocess (1 week)
- Save vocabulary, hints and reprocess log for reuse in other systems
QAS (Test and quality assurance system)
- Run test of Unicode-enabled ABAP programs in the non-UC QAS
- Run SPUMG scans (1-2 weeks)
- In the meantime feed system with vocabulary and reprocess information from SB2
- Finish vocabulary maintenance (1 day)
- Convert the system (1-2 days)
- Post-Conversion Steps (SUMG; others) (1 day)
- Verify result (1 week)
- Drop old system
- Use the UC QAS for ABAP and interface tests. (Transports from DEV to the Unicode QAS are still possible and necessary for program corrections
PRD (Productive System)
- Run SPUMG scans ( 1-2 weeks)
- In the meantime feed system with vocabulary and reprocess information from SB2
- Finish vocabulary maintenance (1 day)
- Convert the system (1-2 days)
- Post-Conversion Steps (SUMG; others) (1 day)
- Verify result
- Keep the old system as long as you have Unicode conversion related open customer messages!
If system verification is OK, you can drop the old system.