S/4HANA QM Migration: Master Data, Open Lots and Cutover

Key takeaway

Plan QM migration by cleaning quality master data, defining treatment of open inspection lots and notifications, and proving end-to-end quality execution after cutover.

Explanation

QM migration is sensitive because master data and active execution objects interact. Before conversion or migration, profile inspection plans, MICs, catalogs, selected sets, material inspection setup and quality info records for duplicates, obsolete content and invalid assignments.

Open inspection lots require a deliberate cutover strategy. Decide whether they complete in the legacy system, migrate through supported mechanisms or are recreated according to project rules. Similar decisions apply to open quality notifications and CAPA records.

Historical quality data may be needed for compliance, supplier evaluation or trend analysis even if it is not migrated into active S/4HANA tables. Archive/reporting access should be part of the design.

After cutover, run process validation across incoming inspection, production inspection, results recording, usage decision, stock posting, notifications and certificate output.

Do not judge QM migration success by master-record counts alone; prove that the right inspections are created with the right specifications and follow-on actions.

Real project scenario

A migration loaded all inspection plans but did not validate material-plan selection. New lots chose obsolete alternatives after go-live. A targeted plan-selection reconciliation corrected the issue.

Common mistakes

Migrating obsolete quality master data.
Having no strategy for open lots.
Losing historical evidence needed for audit.
Validating counts but not plan selection.
Ignoring certificate and notification processes.

Best practices

Clean before migration.
Decide open-object treatment early.
Preserve regulated history.
Test plan selection and lot creation.
Reconcile stock and quality status after cutover.

Interview angle

Explain the QM cutover decisions for master data, open lots, notifications and historical records.

Practice this lesson

Quick check

1. A project team faces this situation in "S/4HANA QM Migration: Master Data, Open Lots and Cutover": A migration loaded all inspection plans but did not validate material-plan selection. Which action is the most appropriate next step?

2. Your client is transforming from ECC QM to S/4HANA and wants to standardize on Fiori Quality apps with embedded analytics. How would you design architecture governance to ensure consistency and prevent app sprawl across plants? Choose the response that best aligns with the expected SAP approach.

3. For S/4HANA Quality Management, Migration, Public Cloud and Architecture, consider this mapped project scenario from Why Inspection Planning Matters: Foundations and Master Data: A mid-sized automotive parts supplier onboarded a new raw material and forgot to maintain inspection type 01 in the QM view of the material master for the receiving plant. Which response best addresses the underlying risk?

Interview questions

1. A project encounters this situation while working on S/4HANA QM Migration: Master Data, Open Lots and Cutover: A migration loaded all inspection plans but did not validate material-plan selection. Walk through how you would analyze the requirement or issue, what you would validate, and how you would test the solution before release.

Answer it in your own words first, then compare.

2. In S/4HANA Public Cloud, what data archiving controls are available for inspection lots and quality notifications integrated with EWM, and what limitations should an architect anticipate?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.