We are currently upgrading from 4.6 to ECC 6.0; in our current DEV environment we have some dev-only and test programs that have not, 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 considered 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. If it is deemed absolutely necessary, despite being considered not 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.
How to Earn Rs.25000 every month in internet without Investment?
Showing posts with label Migrating. Show all posts
Showing posts with label Migrating. Show all posts
Migrating test programs from ECC 4.6 to 6.0
Labels:
Migrating
Subscribe to:
Posts (Atom)
topics
-
▼
2010
(18)
-
▼
April
(13)
- SAP Netweaver XI Components - What are the Compone...
- SAP Message : TP_CANNOT_CONNECT_SYSTEM
- How To Do the TMS Configuration?
- Printing ABAP Report over LAN and WAN
- What are user groups and how can we use them?
- How to delete expired roles?
- Transport Tables between Clients
- Transport Tables between Clients
- Mass Maintenance of Users Profiles
- Changing the default password for sap* user
- How to apply OSS notes to my R/3 system?
- What is mean by OSS how to work on that?
- How do I find out the current patch level in SAP R...
-
▼
April
(13)