# SAP QM Go-Live and Cutover Checklist

> Source: https://netray.co/tools/sap-qm-go-live-cutover-checklist
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A checklist of what to confirm before switching on SAP Quality Management: master data, integration, authorizations, migration and hypercare.

## Category

sap

## Erp

SAP S/4HANA

## Industry

Discrete Manufacturing

## Audience

- SAP QM consultant
- Project manager
- Quality manager

## Tool

**Kind:** checklist

**Scoring Note:** Tick what is done and signed off. Any unchecked critical item is a go-live risk to resolve or formally accept.

**Groups:**

#### Master data

**Items:**

**Text:** Material masters have the QM view and inspection setup where required

**Critical:** true

**Text:** Inspection plans are created, released and assigned to materials

**Critical:** true

Master inspection characteristics reviewed and approved by quality

Inspection methods and sampling procedures loaded

**Text:** Catalogs for defects, causes and usage decision codes agreed

**Critical:** true

Vendor and QM info record data loaded where QM in procurement is used

#### Configuration and process

**Items:**

**Text:** Inspection types and lot origins configured for each process

**Critical:** true

**Text:** Usage decision codes post stock to the correct stock types

**Critical:** true

Notification types, screens and workflows configured

Dynamic modification rules tested with realistic lot sequences

Quality score and vendor evaluation settings agreed

Print layouts for inspection documents, certificates and labels approved

#### Integration

**Items:**

**Text:** Goods receipt triggers an inspection lot as designed

**Critical:** true

Production order and delivery triggers tested end to end

Interfaces to MES, LIMS or test equipment tested with error cases

**Text:** Stock posting from inspection stock reconciled with inventory

**Critical:** true

Costing and finance impact of scrap and rework posting reviewed

Fiori apps and reports used by inspectors tested on target devices

#### Security and compliance

**Items:**

**Text:** Roles separate results recording from usage decisions where required

**Critical:** true

Plant level authorizations tested with realistic users

**Text:** Change documents and audit trail confirmed for key QM objects

**Critical:** true

Regulated processes (for example electronic records) validated

Test equipment and calibration data handled per quality system

#### Data migration and cutover

**Items:**

**Text:** Open inspection lots and notifications cutover rule agreed

**Critical:** true

Migration of master data rehearsed at least twice with reconciliation

Historical results archiving or access plan agreed

Cutover schedule includes freezes on plans and characteristics

**Text:** Rollback criteria and decision owner defined

**Critical:** true

#### Training and hypercare

**Items:**

**Text:** Inspectors trained on results recording with their own parts

**Critical:** true

Quality engineers trained on usage decision and notifications

Hypercare roster and issue triage defined for the first weeks

Daily check of open lots and blocked stock during hypercare

Lessons learned and backlog captured after the first month

## Content

**Intro:** 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.

**Sections:**

#### How to use the checklist

**Body:** 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

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### What is the biggest risk when going live with SAP QM?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

SAP QM go-live checklist, SAP QM cutover checklist, SAP QM implementation checklist, SAP quality management readiness, SAP QM data migration checklist, SAP QM hypercare, SAP QM testing checklist, QM go live readiness

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json