‎2005 Sep 22 6:07 PM
Hello all,
We are planning on deleting a number of customer programs that have become obsolete. Before we delete these programs we plan on copying them to a new package. We do not want any of the objects that are created within this new package to be transported out of our development environment. Is there a way to accomplish this systemically rather than depending upon discipline?
Is this a situation anyone has experienced and do they have a solution?
Thanks
Bruce
‎2005 Sep 22 6:13 PM
‎2005 Sep 22 6:20 PM
‎2005 Sep 22 7:57 PM
Rich,
Thanks for your answer. I took a different approach. These are the values of the parameters I set when creating the new package:
Transport layer - I left this blank
Software component - Home
I set the software component to home instead of local because I wanted a transport request to be created. This will allow better auditing as well as prevent multiple users from editing the same object once the object has been assigned to a development request.
I set the transport layer to space to prevent the development request from being transported.
Thanks
Bruce
‎2005 Sep 22 8:06 PM
Your approach will work Bruce. I am assuming that you are going to <b>copy not reassign</b> each of the obselete custom objects. Copy them to a new program that is assigned to this new development class and kept in a transport request.
The reason for copying instead of reassigning is that once you are ready to delete the obsolete objects from your production system, you need to send a transport deleting them to production. If you just reassign, you will not be able to transport it and delete the objects in production.
Srinivas
‎2005 Sep 22 8:22 PM
Srinivas Adavi,
Yes, we will be copying these programs to the new package, adding the suffix "_OBS" to the program name. After we've copied the program, we will delete the original.
Thanks
Bruce
‎2009 Feb 18 6:23 PM