SAP Change Master and Revision Level Log
The change master (change number) is the backbone of engineering change management in SAP: it carries a validity date and lets you change BOMs, routings and documents with history. This log gives the team a single sheet to see which changes are open, when they take effect and how many objects each one touches.
| Change number | Description | Reason | Valid from | Revision level | Status | BOMs affected | Routings affected | Objects affected | |
|---|---|---|---|---|---|---|---|---|---|
5 | |||||||||
6 | |||||||||
5 | |||||||||
10 |
In SAP the change master record holds the change number, validity and reason, and objects are changed with reference to it. Revision levels can be assigned to materials with the change. Use this log as the human readable register.
Change impact report
Optional help building a read-only change impact report from SAP data.
Optional. The tool and every export work without this. No spam.
How to use the log
Create the change master in the system, then add a row here with the same number, description and valid from date. Record the revision level that the change sets on the material and update the status as the change moves from draft to implemented. Count the BOMs and routings touched so impact is clear. Export to Excel for the weekly change board.
- Keep numbers identical to the system record
- Set the status when the system status changes
- Count affected objects from the where-used list
- Review draft changes with an old valid from date every week
How change numbers work
A change number is created in CC01 and carries a description, a reason, a valid from date and a status. When a BOM or routing is changed with the change number, the system creates a new validity step from the valid from date, so history stays visible and the old state remains for earlier dates. Revision levels identify the state of a material and can be assigned in the change process.
Reading the register
The objects affected total and the average per change show the weight of your change load. A change that touches many BOMs should have a release plan and a check that all affected plants are covered. Changes with the same valid from date and overlapping objects are a conflict risk, so review them together.
Common mistakes
Users change objects without a change number and then lose history. Others set valid from dates in the past, which can disturb open production orders. A third problem is using one change number for many unrelated actions, which makes rollback and audit hard. Keep one purpose per number.
Frequently Asked Questions
What is a change master in SAP?
It is a record created with CC01 that holds a change number, description, reason, validity date and status. Objects like BOMs, routings and documents are changed with reference to it so history is kept.
What is a revision level?
A revision level identifies the engineering state of a material. It can be assigned to a material through a change number so the team and downstream documents reference the right design state.
Can I change a BOM without a change number?
Yes, if the settings allow it. But then history is not created and the change takes effect immediately. Most manufacturers require a change number for controlled products.
Does this log replace SAP ECM?
No. It mirrors the registers you need for the change board. The approval workflow and object changes happen in SAP. The log gives a simple summary and export.
If you want a live view of open changes and their impact built from your SAP data, we can set up a read-only report for your team.
Related Tools
SAP Engineering Change Request (ECR) Template
A structured change request form that captures the reason, impact on stock and open orders, and approvals before a change number is created.
Engineering & PLMSAP BOM Usage and Item Category Reference
Look up the standard BOM usage keys and item category codes, with a plain note on what each controls.
SAPSAP Variant Table Maintenance Worksheet
Lay out valid characteristic combinations for a variant table, with lead time and price class per row, before you maintain the table in SAP.
SAPSAP Variant Configuration Sales Order UAT Script Template
A test script for configured sales orders covering value entry, dependency checks, BOM explosion, pricing and result recording.
More Engineering & PLM tools
See all- SAP Super BOM Design Worksheet
- SAP Engineering Change Number Checklist
- SAP Document Info Record Template
- SAP Engineering Change Obsolescence Exposure Calculator
- SAP Engineering Change Affected Materials Impact Worksheet
- Cloud MRP BOM Data Cleanup Worksheet
- Part Numbering Scheme Generator Template
- BOM Accuracy Calculator
- BOM Error Cost of Poor Quality Calculator