Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Repeating the Preparation steps for unicode

venu_katamneni
Participant
0 Kudos

Hi,

We are planning to convert our system to unicode soon and run the Preparation steps in the QAS system. But, if we run the Preparation steps and some of the objects are modified before the end of the Prepare,how much of it is needing to be re-done before the actual downtime? We are not advocating a freeze of transports on the system during the preparation. What steps may need to be redone and how much of the total effort would that be?

1 ACCEPTED SOLUTION

nils_buerckel
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

in case of a single code page system I do not see many problems here (compared e.g. to an Upgrade) .

For new customer objects, you should set the language flag.

Changes of tables should be treated with RADCUCNT right before the export (as stated in the Unicode conversion guide).

However if you have many changes and these were not included in your tests - then unexpected problems could occur.

This is the reason why SAP recommends to minimize changes during the conversion project.

To be more precise: Recommendation is to do a Sandbox conversion (copy of PRD system). The status of this SBX system should be as near as possible to the status of the PRD system right before the conversion.

Best regards,

Nils Buerckel

SAP AG

Edited by: Nils Buerckel on Nov 11, 2010 9:20 AM

6 REPLIES 6

Former Member
0 Kudos

Hi,

Confirm whether you are referring to upgrade prepare steps or pre Unicode conversion steps.

Regards

Rahul

0 Kudos

It is the pre-unicode conversion preparation prior to the unicode conversion.

nils_buerckel
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

in case of a single code page system I do not see many problems here (compared e.g. to an Upgrade) .

For new customer objects, you should set the language flag.

Changes of tables should be treated with RADCUCNT right before the export (as stated in the Unicode conversion guide).

However if you have many changes and these were not included in your tests - then unexpected problems could occur.

This is the reason why SAP recommends to minimize changes during the conversion project.

To be more precise: Recommendation is to do a Sandbox conversion (copy of PRD system). The status of this SBX system should be as near as possible to the status of the PRD system right before the conversion.

Best regards,

Nils Buerckel

SAP AG

Edited by: Nils Buerckel on Nov 11, 2010 9:20 AM

0 Kudos

so based upon this, do we even needto have a TRANSPORT FREEZE during the final preparation days? I don't want the downtime window to be extended due to things needed to be re-run due to any table changes during the pre-conversion.

nils_buerckel
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

I would recommend to at least minimize the changes as much as possible in the period right before the Unicode conversion.

If for example you detect inconsistent tables right before the Unicode conversion, it might be challenging to decide what to do with it. And the more changes you have, the higher the probability that this occurs.

Best regards,

Nils

venu_katamneni
Participant
0 Kudos

Thanks. We are asking for a 2 day FREEZE before the conversion.