Decommissioning Cockpit Assign Package Button Purpose

[GreggHinkle]

Hi,

I am currently using the Decommissioning Cockpit in Solution Manager 7.2 SP07. I have created an Analysis, identified the objects to be decommissioned, and gone through the wait phase. I created a backup transport using the Backup Transport button and it created the backup transport in the Development system perfectly as I expected. However I noticed that there is no longer a Delete Transport button as there was in version 7.1. After doing a little research, I found OSS note 2435908 which stated that the delete transport button was removed and the objects to be deleted need to be deleted directly in the development environment of the managed system. However I also saw the Assign Package button. My first assumption was that this button would allow you to reassign the objects to a new package in the development environment of the managed system so that they can easily be identified and deleted from. When I selected several objects and clicked on Assign Package, it did not reassign the objects in the development environment of the managed system to the package indicated in the Retirement Package field. All it did was update the Retirement Package and Retirement Package Owner attributes of the objects and send an e-mail to the Retirement Package owner. My question is what is the purpose of this feature? I don't understand what is the benefit of updating just the attribute without actually creating the package in the managed system.

[GreggHinkle · Accepted solution]

I think that I figured out the purpose of the Assign Package option in the Decommissioning Cockpit.

After you enter the criteria when you create a new decommissioning analysis project, you run the analysis to generate the object list.This object list can be quite large based on the criteria that was entered. What I believe the purpose of the assign package button is for the objects contained in the object list to be grouped in smaller bundles (retirement packages) and have these retirement packages assigned to custom code library owners. That way multiple owners can review the objects of a single decommissioning project and see only the objects that are assigned to them when they filter on retirement package.

In our case, we create multiple small decommissioning analysis projects for each system that we are decommissioning custom code from. When we create a decommissioning project, we use the attribute Development Class / Package in the additional attributes section of the project settings to restrict the number of objects that will be contained in the project.

The confusion is around that the term "Package" that is used for this feature. The documentation is not clear as to what this feature is, why you would use it and how it fits in with the decommissioning methodology . As a developer when someone is referring to a package for development objects, I immediately think about the container that these objects reside in the managed system (the old concept of development class in SAP). In my opinion, a different term other than Package should have been used for this feature and the documentation should have been elaborated in order reduce confusion.

If my assumption is incorrect of someone else has another viewpoint, please respond. I would be interested to hear other opinions on this subject.