Problem solve Get help with specific problems with your technologies, process and projects.

Upgrading to ECC 6.0 while converting to Unicode

This reader is planning a split implementation upgrade for ECC 6.0. He will upgrade to ECC 6.0 from 4.6c, with the "Unicode Check Active" check box turned on for all programs (Z programs included). Read Bert Vanstechelman's advice here.

We are planning a split implementation upgrade for ECC 6.0:

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?

This is perfectly possible. Your ECC 6.0 will be Unicode "aware" without being Unicode. As such, you can split the project. First upgrade to ECC 6.0, modify all programs to Unicode compliancy and do the database conversion to Unicode later.

You can also go for the combined upgrade and Unicode Conversion project. Although more technically difficult, it might speed up your project.

This was last published in October 2007

Dig Deeper on SAP implementation and upgrades



Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.