08-04-2011 11:16 AM
HI All
During Unicode approach isit possible to do the conversion of custom and standard program to unicode and make the system live and later on do the data conversion with business downtime.
The reason i am asking so as to reduce the business down time. We are going for CU&UC and donot want a long business downtime.
Let me know if there are any approach where we can do the data conversion in the later phase.
Thanks
Rajat Sarkar
08-04-2011 12:24 PM
Hi,
Please refer http://wiki.sdn.sap.com/wiki/display/unicode/ProjectPlanning-SingleCodePageSystem
Above suggests performing the ABAP Unicode enabling well in advance. And to test the DEV unicode enabled ABAP in a non-UC QA system.
However I am not sure if the same should be done for a live/production system. I would consider that risky.
Regards,
Srikishan
08-04-2011 12:24 PM
Hi,
Please refer http://wiki.sdn.sap.com/wiki/display/unicode/ProjectPlanning-SingleCodePageSystem
Above suggests performing the ABAP Unicode enabling well in advance. And to test the DEV unicode enabled ABAP in a non-UC QA system.
However I am not sure if the same should be done for a live/production system. I would consider that risky.
Regards,
Srikishan
08-04-2011 12:38 PM
Hi,
please have a look at:
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000380759&_OBJECT=011000358700000620342009E
> Page 21
Excerpt begin:
1) Start release >= SAP NetWeaver AS 6.20
> UCCHECK can be run before or during Unicode conversion
2) Start release <= 4.6C (CU&UC or TU&UC*)
> Execute the whole UCCHECK procedure in the SBX Unicode system
> Upgrade the DEV system to SAP ERP 6.0 (Non-Unicode or Unicode) and execute UCCHECK (Additional Maintenance System necessary)
Excerpt End.
Therefore if you have a 4.6c system (or lower) as source system, then the Unicode enabling procedure (UCCHECK) cannot be separated from the actual Unicode conversion (Export / Import). In case of NW 6.20 or higher, you can do most of the enabling before the conversion (you will still need a rework after the conversion).
Best regards,
Nils Buerckel