# SAP PP Go-Live Checklist: Master Data, MRP and Cutover Readiness

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

## Short answer

A tick-box readiness check for production planning go-live, covering master data, configuration, cutover and support.

## Category

sap

## Erp

SAP S/4HANA

## Audience

- SAP PP consultant
- Project manager
- Plant manager

## Tool

**Kind:** checklist

**Groups:**

#### Material master and BOM

**Items:**

**Text:** Every producible material has MRP 1, MRP 2, MRP 3 and work scheduling views maintained

**Critical:** true

**Text:** MRP type, MRP controller, lot size and procurement type reviewed for each material group

**Critical:** true

In-house production time and planned delivery time are set and plausible

Safety stock and reorder points loaded only where policy requires them

**Text:** BOMs exist for all produced materials with correct usage, status and validity dates

**Critical:** true

BOM quantities, units of measure and scrap percentages checked against engineering data

Phantom assemblies and alternative BOMs documented and tested

**Text:** Production versions created with BOM and routing assigned

**Critical:** true

#### Routings and work centers

**Items:**

**Text:** Every routing has valid operations, work centers and control keys

**Critical:** true

Standard values (setup, machine, labor) are loaded and reviewed with production

**Text:** Work centers carry capacity, cost center and activity types for costing

**Critical:** true

Shift and available capacity calendars match actual plant calendars

Routing group counters and sequences are consistent after migration

Operations that need confirmation have the right confirmation control

#### Configuration and MRP

**Items:**

**Text:** Order types, number ranges and status profiles are tested for each plant

**Critical:** true

Scheduling parameters and reduction strategies are configured and tested

**Text:** MRP run variants, planning horizon and firming rules are defined

**Critical:** true

MRP groups and exception message settings agreed with planners

Backflushing and goods movement defaults agreed with warehouse

**Text:** Settlement rules and costing variants tested with finance

**Critical:** true

#### Testing and cutover

**Items:**

**Text:** End-to-end test: demand, MRP run, planned order, production order, confirmation, goods receipt, settlement

**Critical:** true

Test of subcontracting, rework and scrap scenarios if used

**Text:** Migration reconciliation shows row counts and key totals match source

**Critical:** true

**Text:** Open production orders and planned orders have a cutover decision (close, migrate or recreate)

**Critical:** true

Stock and work in process balances agreed with finance

Authorisation roles for planners, supervisors and shop floor tested

**Text:** Rollback plan and cutover timeline signed off

**Critical:** true

#### Hypercare

**Items:**

Planners trained on MD04, COOIS, CO15 and COGI

**Text:** Daily COGI and MRP exception review assigned to a named owner

**Critical:** true

Shop floor confirmation errors have a support route

**Text:** First MRP run reviewed line by line against expectations

**Critical:** true

Issue log with priorities and daily review during first four weeks

**Scoring Note:** Critical items should all be complete before go-live. If more than two critical items are open, treat the cutover date as at risk and review it with the project steering group.

## Content

**Intro:** Most SAP PP go-lives that go badly fail on master data, not on configuration. This checklist covers the master data, configuration, testing and support items that planners and consultants consistently need to confirm before switching on production.

**Sections:**

#### How to use the checklist

**Body:** Work through the groups with the people who own each area: engineering for BOMs and routings, planning for MRP settings, finance for costing and settlement, and the shop floor for confirmation. Tick items as they are verified, not when they are promised. Items marked critical block go-live if open. Export the list to PDF or Excel and attach it to your go-live decision record.

#### Where PP projects go wrong

**Body:** Routing and BOM data migrated from a legacy system often passes technical checks but fails practical ones: a work center without capacity, a missing production version or lead times left at zero. These do not stop the system working; they just give wrong dates and wrong shortages. A first MRP run on migrated data should be reviewed with planners, material by material for the top items.

**Bullets:**

- Check that MRP actually plans the materials you expect, using MD04 on a sample.
- Check scheduled dates against realistic lead times, not just that scheduling ran.
- Check confirmation and goods issue end to end with a real operator.

#### Cutover and hypercare notes

**Body:** Decide early what happens to open orders. Migrating open production orders is possible but risky; many plants complete or technically close them on the old system and recreate only the remaining work. Plan a stock count and WIP reconciliation with finance. After go-live, give planners a named support contact for the first weeks and review COGI and MRP exceptions daily.

**Cta:** Netray can help you validate migrated PP master data with read-only analysis of BOMs, routings and material settings, flagging inconsistencies before the first MRP run.

**Faq:**

#### What is the most common PP go-live issue?

**Answer:** Missing or inconsistent master data: no production version, no routing, wrong lead times or work centers without capacity. They cause wrong planned order dates and wrong shortage lists without producing system errors, so they are found late unless checked deliberately.

#### Should open production orders be migrated?

**Answer:** Often not. Migrating open orders brings partially confirmed history and component issues with it. Many plants finish or close orders in the old system and recreate the remaining quantity in SAP. Decide with finance, because WIP values must reconcile either way.

#### How many MRP test runs should we do?

**Answer:** At least one full regenerative run on migrated data before go-live, reviewed by planners, plus a net change run after master data corrections. Compare results with the legacy system on a sample of materials to explain differences.

#### Does this apply to S/4HANA conversions?

**Answer:** Yes, but conversions add checks for simplification items, changed data models and Fiori app adoption. Use this list for the PP business checks and add your conversion project's own technical checks on top.

## Search terms

sap pp go live checklist, sap production planning cutover checklist, sap pp master data checklist, sap s4hana pp migration checklist, sap bom routing validation, sap mrp go live readiness, sap pp hypercare checklist, sap pp uat checklist

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