Enablement & Platform

S/4HANA migration for machine builders: how to prepare material master and BOM data

Whatever the migration approach, bad master data moves with you unless you clean it first. A 6-step plan for material master, BOMs and Business Partner data, with readiness rules and a score you can track weekly.

Not ready to talk yet? Take the 3-minute Data Foundation Check

IllustrativeS/4HANA DATA READINESSMaterial master cleansedDoneBOM status and usageDone!Units and plants harmonisedIn progress!Duplicates mergedIn progressTest migration rehearsedOpenMigration readiness60%

TL;DR

  • Greenfield, brownfield or selective: bad master data moves with you unless you clean it first.
  • Clean before the project, not during it. The project plan has no room for it.
  • Focus on what blocks go-live: material master, BOMs, customers and suppliers (Business Partner), classification and supersession.
  • Track readiness with written rules and a score per object. Rerun it every week until cutover.
For:SAP / ERP programme leadsMaster data managementEngineering & PLMSystem integrators

Why does master data decide the S/4HANA timeline?

Mainstream maintenance for SAP ECC 6.0 ends at the end of 2027, with optional extended maintenance until 2030. Many machine builders are in the middle of their move right now. Test loads are where schedules slip, and they mostly fail on data, not on code.

ApproachWhat happens to the dataWhere data prep focuses
System conversion (brownfield)Existing data is converted in placeCleanse and archive before conversion, prepare Customer-Vendor Integration
New implementation (greenfield)Data is extracted, transformed and loaded freshDecide what not to take, map to new structures
Selective data transitionChosen company codes, plants or history are movedScope rules per organisational unit

Which objects matter most for a machine builder?

ObjectTypical problemsWhy it hurts in S/4HANA
Material masterDuplicates, free-text descriptions, inactive materials, mixed unitsEvery duplicate multiplies BOM, routing and stock records to migrate and test
BOMs (STKO / STPO)Old alternatives, items pointing to blocked materials, missing effectivityLoad errors and wrong MRP explosions after go-live
Customers & suppliers → Business PartnerDuplicates across company codes, missing tax data, dead accountsCVI conversion fails or creates duplicate business partners
ClassificationClasses and characteristics nobody maintainsVariant configuration and search break
Spare parts & supersessionSuccessor information hidden in text fieldsLost in migration unless it is structured first

How do you prepare? A 6-step plan

  1. Profile. Measure duplicates, blanks, invalid values and usage per object. Usage means any movement, order or where-used in the last few years.
  2. Decide what stays. Materials with no stock, no open documents, no movements for 5+ years and no where-used are archive candidates. Get sign-off from engineering and service, not only IT.
  3. Merge duplicates. Pick a survivor, map the others to it, update BOMs and open documents. Keep the mapping table. You will need it to read history.
  4. Standardise. Units, descriptions in noun-modifier form (BEARING, BALL, 6204-2RS), material types, and classification to eCl@ss or ETIM where it helps.
  5. Fix BOMs. Remove items pointing to blocked materials, clean up obsolete alternatives, structure supersession.
  6. Score and repeat. Written rules per object, a readiness score, rerun weekly until cutover.
MIGRATION READINESS PER OBJECTWeek 1Week 8Target 90%Material master58%94%BOMs61%92%Business Partner70%97%Classification34%85%Supersession22%80%
Illustrative readiness scores before and after eight weeks of cleansing.

What readiness rules look like

RULE MAT-01  description filled, max. 40 characters
RULE MAT-04  base unit in approved list (PC, KG, M, L, SET)
RULE MAT-09  no other material with same normalised description + manufacturer part no.
RULE BOM-03  no BOM item pointing to a material with deletion flag
RULE BP-02   VAT ID present for EU customers

Readiness (per object) = records passing all rules ÷ records in scope

Don’t archive your installed base

A spare part with no movement for six years may still be the only part that fits 300 machines in the field. Check the service BOM and installed base before you archive anything.

Who should own what?

TaskOwner
Rules and readiness scoreMaster data team
What to archiveEngineering, service and finance together
Merging duplicatesMaster data team, approved by engineering
BOM clean-upEngineering and manufacturing engineering
Load and testSystem integrator / migration team

Checklist: are you ready to start?

  • Every object in scope has a named owner
  • Data-quality rules are written down, not only in people’s heads
  • A baseline readiness score per object exists
  • Archive criteria are signed off by engineering and service
  • A duplicate mapping table is kept for history

FAQ

When does SAP ECC mainstream maintenance end?

Mainstream maintenance for SAP ECC 6.0 ends at the end of 2027. SAP offers optional extended maintenance until the end of 2030 at an additional cost.

Should we clean data before or during the S/4HANA project?

Before, as far as possible. Cleansing during the project competes with design, testing and training for the same people, and test loads keep failing on the same errors.

What is the Business Partner in S/4HANA?

In S/4HANA, customers and suppliers are maintained as Business Partners. In a system conversion, existing customer and vendor masters are converted with Customer-Vendor Integration (CVI), which stops on inconsistent data.

Which materials can we archive before migration?

Typical candidates have no stock, no open documents, no movements for several years and no where-used. Keep anything that is still a spare part for machines in the field.

Does the material number length change in S/4HANA?

Yes. S/4HANA supports material numbers with up to 40 characters instead of 18. It is a chance to rethink numbering, but many companies keep their existing numbers to avoid touching drawings, labels and catalogues.

Is your master data ready for S/4HANA?

Send us material master and BOM exports under NDA. We’ll come back with a readiness score per object and the top issues to fix.

Similar Posts