SAPFree templatePDF, Excel, Word exportSAP S/4HANA

SAP PP Master Data Change Request Template

Uncontrolled edits to a BOM or routing are a classic cause of wrong MRP and wrong product cost. This form puts current value, proposed value, impact and rollback on one page before anyone changes the data.

Fill in

Live preview
Download:

SAP PP Master Data Change Request Template

SAP PP Master Data Change Request

Number: MDCR-2026-0142 Date: 2026-10-20 Requester: Production planning

What is changing

Object type: Bill of material Object: FG-2210 plant 1000

Current: BOM FG-2210 component 100-455 quantity 2 EA, usage 1.

Proposed: Component 100-455 replaced by 100-470 quantity 2 EA, valid from 2026-11-15.

Reason

Supplier end of life notice on 100-455. Alternate qualified.

Impact on open orders and planning

Two released production orders use old component. Planned orders after 15 Nov will pick up the new BOM after MRP run.

Rollback

Reinstate old item with validity date change and re-run MRP for the material.

Pre-release checks

CheckDoneByDate
Tested in quality system
Costing run or cost estimate updated
Open orders reviewed
Routing and BOM consistent
Documents attached

Approvals

Requester / Date
Engineering / Date
Production planning / Date
Quality / Date
Master data steward / Date

Use for internal change control. If your change is a formal engineering change with change numbers, align this form with your ECN or ECO process. Template only.

Change impact report from SAP data

Optional: we can show open orders affected by a BOM or routing change.

Optional. The tool and every export work without this. No spam.

How to use the form

Raise one request per object and fill both current and proposed values with enough precision to be checked. Describe how open production orders and planned orders are affected, since orders already created from the old BOM keep their components until you regenerate or adjust them. Attach the exported document to the ticket in your service desk tool.

Why impact and rollback matter

In SAP, BOM and routing changes can be date-effective through validity dates or change numbers. That helps, but released orders and costing do not automatically follow. A rollback line forces the author to think about what happens if the change is wrong, and a pre-release checklist covers costing updates and consistency between BOM and routing.

  • Check validity dates
  • Review open orders
  • Update cost estimates when needed
  • Re-run MRP for affected materials

Common mistakes

Changing production data directly in the production client without a test is the biggest one. Another is forgetting that a BOM usage or status change hides the BOM from MRP. A third is skipping engineering approval for a component swap that changes form, fit or function.

Frequently Asked Questions

Is this the same as an engineering change number?

No. SAP engineering change management with change numbers is a system feature. This form is the human approval record that can reference an ECN number where you use one.

Who should approve a routing change?

Typically production planning or industrial engineering owns the routing, with quality reviewing inspection steps and controlling aware of cost impact. Your own governance decides the final list.

How do I handle changes to released orders?

Decide per order whether to let it finish on the old structure, adjust components in CO02, or cancel and recreate. Document that decision in the impact section.

Should every change use this form?

Use it for changes that affect planning, costing or quality. Minor corrections like a description typo can follow a lighter process agreed with the master data team.

Netray can add a read-only impact report that lists open orders and planned orders touched by a BOM change from your SAP data.