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

How to go about replacing a development system -- if you must

A department is upgrading from R/3 4.6 to ECC 6.0, but will not transport some programs in its current DEV environment. The administrator wants to know how to migrate them to the new ECC DEV environment.

We are currently upgrading from R/3 4.6 to ECC 6.0. In our current DEV environment, we have some dev-only and test programs that have not been, and will not be, transported. How do we go about migrating them to our new ECC DEV environment, which will be a copy of our latest 4.6 production environment?
It is generally a very bad idea to replace a development system. You lose all the history of the developments carried out, as well as useful utilities as you mention.

But if it is deemed absolutely necessary, despite being considered not a best practice, then you can safeguard your dev/test programs by putting them into a development class/package, recorded against a transport. When you release the transport, transport files are created on the applications server, which can be later used to re-import the developments.

Dig Deeper on SAP implementation and upgrades

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.