SAP MDM Migration Lab

How MDM cutover actually runs

My seat is the MDM · BA lane: stewarding quality and mapping while functional and tech lanes move the load.

Read left to right. Blue row is where I sit as MDM SPOC · migration BA.

How modules connect (one picture)

Not nine articles: one flow from masters to processes to control to KPIs.

1 · Master data

MM · SD · BP

Material, customer/vendor BP, ship-to. Clean before any load.

2 · Processes

P2P · O2C

Purchasing and order-to-cash define what “ready” means in ops.

3 · Control

FI · CO

GL, AP/AR, cost objects must still close month-end after go-live.

4 · Proof

BW · KPIs

Reporting packs confirm fill rate, spend, OTIF still reconcile.

MDM Migration Lab

Synthetic ECC → S/4 style cutover for material, customer BP, vendor BP, and ship-to. DQ rules, mapping templates, and readiness scorecards. No confidential client data.

Ready vs legacy by object

Migration readiness

DQ scorecard

Object	Legacy	Ready	Pass rate	Status

Sample customer BP mapping

Source KUNNR	Target BP	Name	Country	Region	Status

Cutover pattern

1

Extract legacy masters (MM material, SD customer/ship-to, MM-PO vendor, FI financial views).

2

Apply DQ rules: UOM, plant extension, orphan ship-to, tax, bank keys, duplicates, sales-area completeness.

3

Map to S/4 BP and material numbers with partner roles, purchasing org, and plant views aligned to CO and FI.

4

Stage READY and NEEDS_REVIEW loads (LTMC-style), track pass rates, reconcile with BW-style KPI packs.

Module detail (optional)

Collapsed by default; open only if you want the deeper module notes.

BW · CO · FI · HR · MM-IM · MM-PO · PM · PP · SD

BW: reporting packs and post-load KPI reconciliation.

CO · FI: cost objects, BP financial views, month-end awareness.

MM-IM · MM-PO: material master and supplier/P2P readiness.

SD: customer BP and ship-to masters in this synthetic dataset.

PP · PM · HR: plant, technical object, and org master adjacency.