Working with a Release Key and a Change Hierarchy

Up to now, you have made changes to your master data that directly affected the logistic supply chain. Now you are looking for a tool that makes a controlled release possible.

Watch the following video, which explains the release key in more detail.

Inside Customizing, you can determine whether change numbers are to be locked, even if they are already released for one or more areas. Then, after the lock has been released, you can edit the release key and the deletion flag.

You can use a simulation for production to check new developments or changes for production.

For example, you have early control over whether all the changed data (such as BOM, routing, and so on) fits together.

• Rlsim: Indicator controls that changes are also included in the simulation for production. This simulation enables you to check new developments or changes in simulation orders for production.

• Relcst: Indicator that controls that the changes in costing are taken into consideration.

• Rlplan: Indicator controls that changes are included in planning.

• Rlprod: Indicator controls that the changes are included in production. Changes can only be included in production if the changes are included in planning at the same time. Therefore, also set the release indicator for planning. For a release key that releases the changes for production, you also have to set the indicator release for simulation.

• Gl.rel: Indicator controls that change master records are released for all areas of the company. If you set this indicator, then the changes are released automatically for all areas. Therefore, do not set any other indicators.

• Rel. OCM: Indicator that controls that, for basic data changes with this release key, a planned change is automatically created for the order change process. The planned change triggers the change process and manages the change activities.

• Date OCM: Indicator controls that, during a date shift, a planned change is automatically created for the order change process.

When you decide to work with the release key, only a set of object types can be defined.

Watch the following video, which explains the possible object types.

The following objectscannot be changed with a change number, based on a release key:

• Inspection Plan

• General Task List

• Equipment Task List

• Functional Location Task List

• Document

• Material

• Objects of Variant Configuration

• Objects of Recipe Management

• Objects of Environment Health and Savety

Up to now, you have created a change number and assigned several objects.

You now want to use a separate change number for each object.

Watch the following video, which explains the use of a hierarchy.

Using a hierarchy of change numbers, it is possible to clearly structure and control complex product changes while also providing them to operational areas as a logical unit.

An important property of the change hierarchy is the option to define different, organization-specific change processes on the change package level, using status management and the integrated workflow. Some control elements are maintained centrally in the leading change master record for the entire hierarchy.

If you want to release a leading change master record, then all lower-level change packages have to be technically released. This dependency, however, only applies for global release and release for production. If this indicator is set, you cannot undo it later.

You can only process an object with reference to a package that is not technically released.

In the standard system, you cannot add additional packages after the release of leading change master record for production. However, you can add late packages or use packages that are not technically released, if the late packages indicator is set in the "Control data process step".