Engineering Change Management (ECM) in SAP controls when changes to VC models take effect. Without ECM, changing a dependency or a variant table affects all configurations immediately : which is rarely what you want in a production system.
ECM gives you version control for your VC model. You schedule a change for a specific date, and all configurations created after that date use the new logic. Configurations created before it use the old logic.
Source: SAP Help: Engineering Change Management
Key Concepts
Change number (CC01): A master record representing a change. It has:
- A valid-from date
- A description
- A status
Validity period: The date range during which the change is active.
Object validity: Each VC object (dependency, variant table, BOM, routing) can be assigned a change number. The object is only valid when the change number's valid-from date is satisfied.
How ECM Interacts with VC Dependencies
When you create or modify a dependency (CU01-CU06), you can assign a change number. The dependency then only exists in configurations whose key date falls within the change's validity period.
The configuration key date comes from:
- In VA01/VA02: the sales order document date
- In production: the order start date
- In CU50: the test configuration date
Important: The key date is linked to the SO item creation time, not the delivery date. This means a change scheduled for June 1 affects orders created on or after June 1, even if delivery is months later.
ECM-Driven Dependencies in CU50 Trace
The CU50 trace shows you which dependencies are active for the current key date. If a dependency is inactive due to ECM, the trace shows:
Dependency PRO_001: Not processed (change number 0000001234 not valid for key date)
This helps debug "it worked yesterday" scenarios : the answer is usually ECM.
ECM and Variant Tables
Variant tables also support ECM. When you change variant table data with a change number, the system stores the old and new versions. The correct version is selected based on the configuration key date.
Transaction CU61 supports ECM-driven variant table maintenance.
Model Versions in AVC
AVC introduces Model Versions as an alternative to ECM for managing VC model changes. A model version is a snapshot of the entire configuration model at a point in time.
Comparison:
| Feature | ECM | AVC Model Versions |
|---|---|---|
| Scope | Individual objects | Entire model |
| Management | CC01 change numbers | Model version ID |
| Granularity | Per-object | All-or-nothing |
| Rollback | Complex | Simple (revert version) |
| Overhead | High (many change numbers) | Lower |
Best Practices for VC ECM
When to use ECM:
- Regulatory or compliance changes need audit trail
- Multi-site rollouts where different sites go live at different dates
- Safety-critical changes that must be traceable
When to skip ECM:
- Early model development (use CU50 test mode without change numbers)
- Simple pricing updates (use variant tables instead)
- Small fixes that don't affect existing orders
Common ECM Mistakes
- Wrong key date on sales order: the SO document date determines which ECM changes apply. A late-entered order may use old logic.
- Missing change number on dependencies: editing a dependency without a change number makes the change effective immediately for all configurations.
- ECM on individual values vs. full characteristics: applying ECM to characteristic values but not the characteristic itself can cause partial updates.
Sources: SAP Help: Engineering Change Management | CC01/CU50 transaction documentation