# SAP QM Master Data Cutover Tracker Worksheet

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

## Short answer

Track each QM master data object through a migration: source records, loaded, errors and percent complete, with a total for the cutover meeting.

## Category

sap

## Erp

SAP S/4HANA

## Audience

- SAP QM consultant
- Data migration lead
- Project manager

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### QM object

**Key:** object

**Type:** select

**Options:**

- Master inspection characteristics
- Inspection methods
- Code groups and catalogs
- Sampling procedures
- Inspection plans
- Material QM views
- Quality info records
- Test equipment (PRT)
- Open inspection lots

#### Load method

**Key:** tool

**Type:** select

**Options:**

- Migration cockpit
- LSMW
- BAPI program
- Manual entry

#### Owner

**Key:** owner

**Type:** text

#### Source records

**Key:** source

**Type:** number

**Format:** integer

#### Loaded

**Key:** loaded

**Type:** number

**Format:** integer

#### In error

**Key:** errors

**Type:** number

**Format:** integer

#### Not yet loaded

**Key:** open

**Type:** number

**Expr:** source - loaded - errors

**Format:** integer

#### Complete %

**Key:** pct

**Type:** number

**Expr:** if(gt(source,0),loaded/source*100,0)

**Format:** percent

#### Error rate %

**Key:** err_pct

**Type:** number

**Expr:** if(gt(source,0),errors/source*100,0)

**Format:** percent

#### Load date

**Key:** due

**Type:** date

**Rows:**

**Object:** Master inspection characteristics

**Tool:** Migration cockpit

**Owner:** R. Nair

**Source:** 860

**Loaded:** 860

**Errors:** 0

**Due:** 2026-11-02

**Object:** Sampling procedures

**Tool:** Manual entry

**Owner:** R. Nair

**Source:** 42

**Loaded:** 42

**Errors:** 0

**Due:** 2026-11-02

**Object:** Inspection plans

**Tool:** LSMW

**Owner:** S. Iyer

**Source:** 1450

**Loaded:** 1180

**Errors:** 96

**Due:** 2026-11-09

**Object:** Material QM views

**Tool:** Migration cockpit

**Owner:** S. Iyer

**Source:** 5200

**Loaded:** 3900

**Errors:** 140

**Due:** 2026-11-09

**Object:** Test equipment (PRT)

**Tool:** BAPI program

**Owner:** M. Das

**Source:** 310

**Loaded:** 0

**Errors:** 0

**Due:** 2026-11-16

**Totals:**

#### Source records

**Key:** source

**Agg:** sum

**Format:** integer

#### Total errors

**Key:** errors

**Agg:** sum

**Format:** integer

**Summary:**

#### Overall complete

**Key:** overall

**Expr:** sum_loaded / sum_source * 100

**Format:** percent

**Primary:** true

#### Overall error rate

**Key:** overall_err

**Expr:** sum_errors / sum_source * 100

**Format:** percent

**Notes:** Object names and methods are examples. Load order matters: characteristics and methods first, then catalogs and sampling, then plans, then material QM views. Confirm the objects available in your release of the migration cockpit.

## Content

**Intro:** QM master data has a hard load order, and errors in an early object block everything after it. A simple tracker per object gives the cutover meeting one honest view of what is loaded, what failed and what is still open.

**Sections:**

#### How to use it

**Body:** List each QM object you migrate, the method used and an owner. Enter the number of source records, the number loaded and the number in error after each load run. The worksheet calculates the open records, percent complete and error rate for every object and for the whole load. Export to Excel for the cutover report.

**Bullets:**

- Update after every load cycle, not only at the end
- Keep error counts separate from not-yet-loaded counts
- Sort by load date to see the critical path
- Add a row for each separate plant load if plants load apart

#### Load order for QM

**Body:** Inspection plans reference master inspection characteristics, inspection methods, code groups, sampling procedures and often work centers and test equipment. Load those dependencies first. Material QM views and inspection types activate lot creation and should load after plans exist, otherwise lots are created with no plan. Quality info records and open lots come last, if at all. Many projects choose not to migrate open lots and instead close them in the legacy system.

#### Reading the numbers

**Body:** Percent complete is loaded over source records. Open is source minus loaded minus errors, so a negative number means counts were entered wrongly. A rising error rate on plans often points to a missing characteristic or a work center that was not loaded. Look at the first error messages before reloading, since repeating a failed load usually repeats the same failure.

#### Common mistakes

**Body:** Loading material QM views before inspection plans exist. Reloading plans that were created already, producing duplicate versions. Forgetting to transport the QM customizing before the data load. Not reconciling counts against the legacy system after the load.

**Cta:** If your plans and characteristics sit in spreadsheets or a legacy QMS, Netray can help check them for load errors before the cutover.

**Faq:**

#### Which method should I use to load inspection plans?

**Answer:** It depends on the release and the volume. The S/4HANA migration cockpit covers some QM objects, and older projects use LSMW or BAPI-based programs. Check which objects your release supports before you choose.

#### Should I migrate open inspection lots?

**Answer:** Usually not. Open lots carry results and status that are hard to recreate. Most projects finish them in the legacy system before cutover and start new lots in SAP after go-live.

#### What error rate is acceptable?

**Answer:** Any error needs a decision. Errors are acceptable only when they are understood and fixed in a later cycle before cutover. Zero unexplained errors on the final run is the usual exit criterion.

#### Why track not yet loaded separately?

**Answer:** Because records that were never attempted are a schedule risk, while records in error are a quality risk. Mixing them hides which problem you actually have.

## Search terms

SAP QM data migration tracker, SAP QM cutover checklist excel, inspection plan migration, SAP migration cockpit tracker, SAP master data load tracker, QM data migration S/4HANA, LSMW inspection plan load, cutover tracker worksheet

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