Defining as a Basic Change (SAP Library - Engineering Change Management (LO-ECH))

Defining as a Basic Change

Use

If you want a change status to be generally accepted as effective, even if other changes exist for other effectivity periods, you can define the changes as always effective for a specific change number. This could be useful for a routing, for example, if one machine has been replaced by another and you only want the routing that takes the new machine into account to be selected.

Integration

Defining a change status as a basic change is only supported for leading change master records. You can define a basic change in the leading change master record using the Define basic change function and this includes all the changes from all the assigned change packages.

Prerequisites

In Customizing Logistics General ® Engineering Change Management you have set the Assign alternative date indicator in Setup control data.

Additionally the following prerequisites must also filled:

The leading change master record

has been maintained with a date effectivity (valid-from date)
has been released for production

All the allocated change packages have been released technically.

Features

The following rules apply when you define a change as a basic change:

The change master record is effective

without any time limits (always)
without any status restrictions

You cannot create any Late packages for the leading change master record, even if the Late package indicator is set.

You cannot withdraw a basic change.

Activities

Change the leading change master record that the changes are to be defined as basic changes for.

Choose Define basic change from the menu in the change header.

You see a warning telling you that you cannot withdraw the definition as a basic change.

Confirm the warning and save the change master record.