Introducing Engineering Change Management

Objective

After completing this lesson, you will be able to give an overview of Engineering Change Management.

Engineering Change Management Overview

Up to now, you have created or modified SAP master data directly with the current date as the effective date.

You are now looking for a tool that not only documents these creations and changes in a more structured way, but also allows you to plan and schedule changes in advance within the SAP system.

Engineering Change Management (ECM) provides a solution to meet these requirements.

Watch the following video to get a first impression of working with SAP Engineering Change Management.

You can perform changes to objects in the SAP system, such as routing changes, either with or without history.

For changes without history, the system generates change documents, but the change statuses themselves are not saved.

When changes are made using a change number, they are referred to as historical changes. These changes can be scheduled to become effective on a specific date. In this case, both the state before and after the change are stored, and the system also generates change documents.

Engineering Change Management in SAP ensures that changes are fully documented. This level of documentation is often required for legal or compliance purposes, such as product liability.

The figure explains BOM changes using a Change Master Record.

When you change a bill of material (BOM) using a change master record, the system stores both the state before and after the change. The pre-change state is valid up to the valid-to date, while the post-change state becomes effective from the valid-from date, which is typically the following day.