Release in a Change Hierarchy 
Release in a Change Hierarchy
Use
You can use a
Release Key to control the release of objects in a Change Hierarchy. This ensures that all the objects involved in this complex change become effective as a logical unit in the operative areas.Integration
In a change hierarchy, the object changes are with reference to the change packages. The release of all the changes that were made with reference to the change packages is by means of the release key in the superior change leader that they are allocated to.
Features
You can release the changes in a leading change master record either by using a release key or by using the Technical release function.
Release key
The release key is a required entry in the leading change master record.
All the changes in a change hierarchy are released by the release key in the leading change master record.
You release object changes that are made with reference to change packages with the release key in the leading change master record. After releasing the changes in the leading change master record, they are taken into account in the operative areas.
Technical Release
The Technical release indicator helps to control the completeness of changes in the change hierarchy.
In the standard system, you can only perform a technical release for a leading change master record if all its change packages have been technically released. You release the change leader or the packages technically by using the Technical release function. The system then automatically sets the Change package released technically indicator in the change header of the leading change master record or the change package. The changes are then released, for example, for production or globally, depending on your settings.
You cannot withdraw the technical release. However, if you make special settings for
Late Packages, you can make changes to the change leader even after you have released it.