topic Re: Create a package whose objects can't be transported??? in Application Development and Automation Discussions

Create a package whose objects can't be transported???

Former Member — Thu, 22 Sep 2005 17:07:33 GMT

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

Re: Create a package whose objects can't be transported???

RichHeilman — Thu, 22 Sep 2005 17:13:24 GMT

When coping them, you can assign them to $TMP development class(package). This will keep them local. You could also create a custom or "Z" devleopment class(package) which is not transportable.

Regards,

Rich Heilman

Re: Create a package whose objects can't be transported???

RichHeilman — Thu, 22 Sep 2005 17:20:46 GMT

When creating a development class(package) for local objects, it must begin with $. So if you want to create a custom DC, start with $Z. Don't enter anything for transport layer and use LOCAL for the software component.

Regards,

RIch Heilman

Re: Create a package whose objects can't be transported???

Former Member — Thu, 22 Sep 2005 18:57:46 GMT

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

Re: Create a package whose objects can't be transported???

Former Member — Thu, 22 Sep 2005 19:06:04 GMT

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

Re: Create a package whose objects can't be transported???

Former Member — Thu, 22 Sep 2005 19:22:24 GMT

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

Re: Create a package whose objects can't be transported???

Former Member — Wed, 18 Feb 2009 18:23:49 GMT

closing old post