SAP QM Implementation Readiness Checklist

0%

0 of 34 items complete

9 critical items still open - these are the highest-risk gaps.

Download checklist:

Scope and design

Inspection types in scope are listed per plant (goods receipt, in-process, final, stock, return)CRITICALInspection lot origins and the triggering business events are confirmed with logisticsCRITICALMaterials in scope have the QM view maintained and the inspection setup flag decidedSampling procedures and sampling schemes are agreed with quality engineeringDynamic modification rules and quality levels are defined or consciously excludedQuality notification types and catalogs for defects, causes and tasks are designedCertificate requirements for customers and vendors are listedData ownership between QM, logistics, production and maintenance is documented

Master data

Master inspection characteristics are created with units and decimals checkedCRITICALInspection methods and code groups are created and linked to characteristicsInspection plans are assigned to materials with valid dates and status releasedCRITICALInspection equipment and calibration plans are in place for each gauge usedVendor and customer quality settings and QM control keys are reviewedUsage decision codes and code groups are mapped to stock postingsAuthorisation roles for QM master data and result recording are tested

Integration

Goods receipt triggers the inspection lot and the stock posting to quality inspection stockCRITICALUsage decision posts stock to unrestricted, blocked or scrap as designedCRITICALProduction order and process order inspections trigger at the right operationsProcurement quality assurance agreements and release strategies work with purchasingQuality notifications integrate with maintenance and customer complaint flowsBatch management and batch determination rules behave with inspection resultsOutput forms such as inspection certificates and sample labels print correctlyInterfaces to LIMS, MES or measurement devices are tested end to end

Testing and training

Test scripts cover results recording, defect recording and usage decision for each plan typeCRITICALNegative cases are tested: reject lots, blocked stock, missing planInspectors recorded sample results on real devices or terminalsQuality users trained on worklists and the exception processReports for lot status, rejection rate and open notifications are validatedKey users own the first-week issue log

Cutover and support

Open inspection lots and open notifications are cleared or migrated by planCRITICALStock in quality inspection is counted and reconciled before cutoverCRITICALFallback procedure exists if inspection lots do not generateHypercare roster covers QM, MM, PP and basisAudit and regulatory records requirements are met for the migrated history

Items marked critical should be complete before cutover. A clean list means ready, not that the project is risk free.

SAP QM readiness review

Optional: have a consultant review your open items before cutover.

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

How to use it

Work through the groups with the quality lead, the SAP QM consultant and a key user from logistics. Mark each item as done only when someone has seen it work in the test system, not when it is configured. Items flagged critical should be closed before cutover. Export the result to share the status in the steering meeting.

What the groups cover

Scope and design settles what is inspected and how. Master data covers characteristics, methods, plans and equipment. Integration tests the touchpoints with materials management, production and maintenance. Testing and training ensures people can record results and take decisions. Cutover and support deals with open lots and stock in quality inspection, which is where migrations commonly stumble.

SAP behaviours worth knowing

Inspection lots are created from events such as goods receipt, production order release or goods issue, and the type is set by the inspection type assigned to the material. The usage decision (QA11) is what moves stock out of quality inspection. Blocked or unclear stock is the largest source of cutover disputes, so reconcile it early.

Common mistakes

Testing only the good path, loading inspection plans late so that users record results against nothing, and under-planning training for inspectors who work on shop floor terminals rather than the SAP GUI. Also check authorisations carefully, because a missing role often looks like a configuration error.

Frequently Asked Questions

Does this apply to S/4HANA and ECC?

Yes. The structure of QM master data, inspection lots and usage decisions is the same, though user interfaces and some transactions differ between releases.

Who should own the checklist?

The SAP QM lead owns it, with the quality manager signing off the business items and logistics owning integration checks.

How long does QM readiness take?

It depends on scope. Plan weeks for testing and master data for a single plant and longer for several plants with different inspection types.

Can I add my own items?

Yes, export the checklist and extend it with industry or customer specific requirements such as aerospace or medical record rules.

We can support SAP QM projects with AI-assisted master data checks and reconciliation queries against your own system, with a person approving every change.

Talk to an Expert Explore More Free Tools

Related Tools

SAP

More SAP tools

See all

SAP QM Implementation and Go-Live Readiness Checklist