Change Process With Release Process 

Purpose

You can control and activate complex object changes step-by-step for operative areas using a regulated release process.

Prerequisites

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

·        You have activated the release process under Set control data.

·        You have defined the release keys for the release process under Define release keys.

Process Flow

...

       1.      Create a change number.

...

                            a.      Choose Logistics ®Central Functions ® Engineering Change Management ®Change master ® Create.

You see the Create Change Master: Initial Screen.

                            b.      Enter the required data. In the Function dataset, choose the function you require (for example, With release key).

                            c.      Confirm your entries.

The Change Header screen appears.

                            d.      Maintain the data that is required for the function you selected.

Select a release key for the duration of the object changes. The key must not support release for operative processes.

                            e.      Enter further required data, for example object type indicators.

                              f.      Save the change master record.

       2.      Process the change objects (for example, BOMs) with reference to the chosen change number.

Save your changes.

At this processing stage, the changed object data is not yet taken into account in the operative areas because the changes have not yet been released in the change master record.

In this processing situation you can simulate the changes as being effective.

       3.      After you have finished making the object change, and you want the change to be taken into account in adjoining processes (for example, costing, requirements planning, and production), you change the release key in the change master record.

...

                            a.      Choose Logistics ®Central Functions ® Engineering Change Management ®Change master ® Change.

                            b.      On the Change Header screen, choose a release key for your chosen area or one that is defined for the required processes (costing, requirements planning, production) as Released globally.

For a change hierarchy, you define the release key in the change leader.

                            c.      Save the change master record.

The changed data is now read in the adjoining processes.