We will upgrade to ECC 6.0 from 4.6c, with the "Unicode Check Active" check box turned on for all programs (Z programs...
included). However, the underlying Oracle database will be kept as is. This means that the existing non-Unicode database from 4.6c will be copied for use with ECC 6.0.
Six weeks later, we intend to convert the non-Unicode database to Unicode with UTF-8.
Can you please let me know if you see any faults with the above implementation strategy? Is it a feasible one? Also, can the Unicode compliant ABAP programs exist with a non-Unicode database that we will convert later?
You can also go for the combined upgrade and Unicode Conversion project. Although more technically difficult, it might speed up your project.
Dig Deeper on SAP implementation and upgrades
Related Q&A from Bert Vanstechelman
An SAP user wants to know the risks of changing time zones in ECC 6.0. Continue Reading
An SAP user wants to know how to access an SAP IDES 4.7 system via the Internet through SAP GUI. Continue Reading
A SearchSAP.com reader wants to know how an increase of indexes and tables after upgrade to SAP ECC 6.0 will affect the memory requirements of a DB2 ... Continue Reading