You should take the following prerequisites into account.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Prerequisites and restrictions:
• Prior to the refresh, all change requests that exist in the development system must be imported into the production system or they must be deleted. The reason is that the version management refers to change request number. If you restore version tables containing references to change requests that no longer exist, problems may occur.
• The version data of the source system is completely lost. If there were differences between the two systems (e.g., repairs to SAP objects) then all record of these will disappear. To avoid conflicts because of this the source and target system should be at the same support package level (the note does not mention this, but the requirement seems obvious). Furthermore, the source (e.g., production) system should not contain any repairs that were not also applied in the development system.
• As an extra precaution -- not mentioned in the note -- it might be wise to export the version tables of the source system before the import of the version data from the old development system.
• After the refresh, check and if necessary change the transport number range in E070L.
Dig Deeper on SAP workflow development
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
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.