Release Procedure Using the Release Key (SAP Library - Engineering Change Management (LO-ECH))

Release Procedure Using the Release Key

Use

The procedure for releasing object changes in the operative areas (for example, planning, production) is controlled by the change master record release key.

Change statuses of objects that have have been changed with a change master record that has not been released are not taken into account by the operative areas.
Change statuses of objects that have have been changed with a change master record that has been released are taken into account by the operative areas. This ensures that the changes made to the objects become effective in the operative areas as one logical unit. For example, you cannot then have the case of drawings and routings not fitting together.

This regulated release procedure ensures that the changes are activated in the operative areas in a controlled, step-by-step way.

Integration

You control the release procedure by using a release key. You define the release key with the Release active indicator in Customizing for Engineering Change Management. You select the release key in the change master record (change header).

Prerequisites

You must perform the following activities in Customizing for Logistics - General ® Engineering Change Management.

Activate the release procedure under Set up control data.

Define the release keys for the release procedure under Define release keys.

Features

You decide whether you want to create a change master record with or without a release key on the initial screen (for creating a change master record).

Without release key

No release procedure takes place. The changes are released automatically for the operative areas.

With release key

You can define the release key in Customizing so that the release only affects certain areas of your company. You can also use the release key to determine whether Order Change Management (OCM) processes are started automatically.

Using the Release Key to Control the Release Procedure

Release for Enterprise Areas

The release procedure is designed in such a way so that you can release changes either globally for all operative areas, or release them for a specific area or areas (for example, costing, planning, or production). For example, if a product structure that has been changed has not yet been released for planning and production, but must be used for preliminary costing, the Released for costing indicator is set in the appropriate change master record. You can perform the release for other (or all) areas at a later date.

As long as you are making object changes, you must choose a release key that has not been defined as released. You should not choose a release key that is defined as released until you have finished making the object changes and you want them to be taken into account in the adjoining work areas.

You can also simulate the changes for production so that you can check new developments or changes for production in simulation orders. For example, you receive information earlier for your simulation telling you whether all the changed data (for example, BOM, routing, document) fits together.

Making Changes Later

Planned changes cannot always be implemented, for example, when sales orders or projects that are affected by a change have already been planned in production and converted to production orders. However, you can adapt production orders that are already being used in production to the changed product structure by using the Order Change Management (OCM) tool.

You can initiate the changes, for example a design change, by using a change request. Releasing a change in the design or performing a date shift automatically starts the OCM process.