# SAP Engineering Change Number Checklist for Change Management > Source: https://netray.co/tools/sap-engineering-change-number-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Walk through a change master from reason and effectivity to affected objects and release so no BOM, routing or document is changed without a number. ## Category engineering-plm ## Erp SAP S/4HANA ## Audience - PLM engineer - BOM engineer - SAP PP consultant ## Tool **Kind:** checklist **Scoring Note:** Every item should be checked before a change number is released. Items marked critical protect traceability and production integrity. **Groups:** #### Define the change **Items:** **Text:** A written reason for the change exists and is entered in the change master description **Critical:** true The change request or engineering review that approved the work is referenced The affected product families and plants are listed **Text:** A single change number is used for all linked objects of the same change **Critical:** true The change type and priority follow company procedure The owner and approvers are named The target date and any customer notification need are recorded #### Create the change master **Items:** **Text:** The change number is created in CC01 with the correct description and valid-from date **Critical:** true The change number status is set according to your release procedure **Text:** Object types allowed by the change master include every object you plan to change **Critical:** true The reason for change and the authorization group are maintained Number range and external numbering rules are respected The change master is saved and displayed in CC03 for a final check #### Set effectivity **Items:** **Text:** Valid-from date is set and agrees with planned inventory run-out **Critical:** true If effectivity is by parameter, such as a serial number or lot, the parameter and value are defined **Text:** Old and new component effectivity do not overlap or leave a gap **Critical:** true Open production orders and planned orders affected by the date are identified Stock on hand and open purchase orders for the old component are reviewed Alternative or substitute parts are agreed where run-out is not clean #### Change the objects **Items:** **Text:** BOM changes are made with the change number in CS02, not by overwriting history **Critical:** true Routings and task lists affected by the change are updated with the same number Material master revision level is updated where your process requires it Document info records are revised or new versions created and linked (CV02N) Configurable material dependencies and classification changes use the change number **Text:** Where-used lists were checked to find every parent BOM affected **Critical:** true Production versions and planning settings are reviewed #### Release and follow up **Items:** **Text:** Approvals are recorded and the change number is released only after sign-off **Critical:** true Affected sites and suppliers are notified of the new revision MRP is rerun or checked to confirm the new demand picture Test orders or simulated configurations confirm the new structure The change history report is saved with the change record Lessons learned or recurring causes are logged for the next review ## Content **Intro:** In SAP, every controlled change to a BOM, routing or document should travel with an engineering change number. This checklist covers the steps from defining the reason to releasing the change, so nothing is altered without an audit trail. **Sections:** #### How to use the checklist **Body:** Work through the groups in order for each change. Tick each item as you confirm it, and treat the critical items as gates: do not release the change number if any of them is open. Export the finished list to PDF and attach it to the change record, which gives an auditor evidence of how the change was controlled. Share the list with everyone who touches the change, since the engineer, the planner and the document controller each own different items. #### What an engineering change number does **Body:** A change master, created in CC01 and displayed in CC03, holds a change number with a valid-from date, a reason and the object types it may govern. When you change a BOM in CS02 or a routing with that number, SAP records the change against the number and the effectivity date instead of overwriting history. This lets you see what the structure looked like on any date and lets planning use the right component. Effectivity can also depend on a parameter such as a serial number range, which is useful for products built to order. **Bullets:** - BOM, routing, material, document and classification objects can all use change numbers - Valid-from dates drive what MRP sees - Change history shows what changed, when and under which number #### Reading your result **Body:** If every item is checked, the change is traceable from reason to release. Open critical items are the real warning: a missing where-used check, for example, means a parent BOM may keep the old component. Open noncritical items usually indicate process gaps, such as notifications that rely on people remembering. Count the open items by group to see where your process is weak, and fix the process rather than adding more tick boxes. #### Common mistakes **Body:** Teams change a BOM without a change number to save time, then cannot explain a production problem later. Others set a valid-from date before the old stock is used and create shortages, or leave a gap between old and new component effectivity. A change number is often reused for unrelated work, which blurs the audit trail. Open production orders created before the change are also forgotten. The checklist addresses each of these directly. **Cta:** If your change process runs through email and spreadsheets next to SAP, we can discuss reading change records and flagging open items automatically. The checklist works as is. **Faq:** #### Which SAP transaction creates a change number? **Answer:** Change masters are created in CC01, changed in CC02 and displayed in CC03. These belong to engineering change management in the SAP PLM and production planning area. Menu paths and available functions depend on the release you run. #### Can I change a BOM without a change number? **Answer:** Technically it is often possible, depending on configuration, but you lose history because the change simply overwrites the current structure. Controlled environments, such as aerospace and defense, normally enforce change numbers through process or settings. #### What is parameter effectivity? **Answer:** Instead of a date, effectivity can be tied to a parameter such as a serial number or lot range, so a change applies from a given unit onward. It suits products built to order, where the date of the change matters less than the unit it affects. #### Does the change number cover documents? **Answer:** Yes, document info records can be managed with change numbers, so a drawing revision can be tied to the same change as the BOM. See the document info record template for the fields to plan. ## Search terms sap engineering change number, sap change master cc01, sap ecn checklist, sap engineering change management, sap effectivity parameter, sap bom change number, sap ecr eco process, change number sap valid from --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json