SAP QM Go-Live and Cutover Checklist
Switching on SAP QM changes how goods are received, produced and released, so a weak cutover blocks stock and slows lines. This checklist groups what to confirm before go-live, with the critical items marked.
0 of 33 items complete
12 critical items still open - these are the highest-risk gaps.
Master data
Configuration and process
Integration
Security and compliance
Data migration and cutover
Training and hypercare
Tick what is done and signed off. Any unchecked critical item is a go-live risk to resolve or formally accept.
Want a second pair of eyes before go-live?
An optional review of your SAP QM readiness and cutover plan.
Optional. The tool and every export work without this. No spam.
How to use the checklist
Work through each group with the owner named beside it: quality for plans and catalogs, the functional team for configuration, the interface team for integration and the security team for roles. Tick items only when evidence exists, such as a test script result or a reconciliation report. Export the checklist to PDF or Excel for the go-live review and keep the critical unchecked items on the risk log until they are resolved or formally accepted.
Where QM go-lives usually go wrong
Most problems come from stock and master data, not from the inspection screens. Goods receipts that create lots for materials without a usable plan block stock. Wrong usage decision stock posting leaves good parts in inspection stock. Catalogs that nobody agreed make later reporting useless. Test the full path from trigger to stock posting with realistic data rather than only the QM screens in isolation.
- Lots created for materials without a plan or with the wrong plan
- Usage decision codes that post to the wrong stock
- Open lots at cutover with no agreed rule
- Roles that let one person record results and decide
Cutover choices for open inspections
For open lots you have three practical options: finish them in the old system before cutover, close them with a documented decision and migrate only the stock, or recreate them in the new system as new lots. Pick per process and per risk. Regulated products usually need the documented decision with traceable records. Whatever you choose, reconcile inventory in inspection stock before and after, because that is where mistakes show first.
Hypercare
In the first weeks watch open lots, blocked stock, lots without a plan and notifications without owners every day. Keep a short feedback loop with inspectors, since their workarounds reveal gaps in plans and screens. Plan for plan and characteristic corrections, and give the master data owner clear authority and a change process so fixes do not bypass quality approval.
Frequently Asked Questions
What is the biggest risk when going live with SAP QM?
Usually stock and master data: lots created without a valid inspection plan, or usage decisions that post to the wrong stock type, leave material blocked or released by mistake. Test the complete trigger to stock posting path with realistic data.
How should I treat open inspection lots at cutover?
Decide per process: complete them before cutover, close them with a documented decision and migrate the stock, or recreate them as new lots. Regulated products need traceable records. Reconcile inspection stock before and after the cutover.
How many test cycles does a QM go-live need?
It depends on scope, but plan for unit tests, an integrated end to end test with real parts and plans, a user acceptance test with inspectors, and at least two migration rehearsals. Any process with MES or lab interfaces needs extra error case testing.
Do we need separate roles for results and usage decisions?
Many quality systems require that the person recording results is not the only one deciding, and auditors look for it. Design roles accordingly in PFCG and confirm with your quality manager which processes need the separation.
If you want a read-only view of open lots, blocked stock and notification backlog during hypercare, we can set that up over your SAP data, on-premises if required.
Related Tools
SAP QM Maturity Assessment
Nine questions about plans, catalogs, notifications, integration and analytics give you a maturity score for your SAP QM use and a list of next steps.
SAPSAP QM Transaction Codes Reference
A searchable list of the SAP QM transaction codes consultants and key users use every day, grouped by inspection, results, notifications and master data.
Developer ToolsSAP QM Usage Decision BAPI Skeleton
An ABAP skeleton for recording an inspection lot usage decision through the standard BAPI, with error handling and a commit only when no error is returned.
SAPSAP QM Database Tables Reference
Searchable lookup of the core SAP Quality Management tables, what each one stores and its main key fields, for report writers and data migration teams.
More SAP tools
See all- SAP Production Order Types, Categories and Statuses Reference
- SAP MRP Controller Daily Worklist Template
- SAP MD04 Exception Messages and MRP Elements Reference
- SAP Routing Upload Worksheet (Excel)
- SAP BOM Usage, Status and Item Category Reference
- SAP Lot Sizing Procedures and MRP Parameters Reference
- SAP Work Center Capacity Planning Calculator
- SAP Planned Order to Production Order Conversion Checklist
- SAP Movement Types Reference