Book a call

Data Health Check for ERP master data

Clean SAP master data in weeks. No major project.

  • Developed in Germany
  • Hosted in the EU
  • No training on customer data
Book a call

The Health Check at a glance

Fixed price

Duration

2–4 weeks

Start

Scoping, 1–2 hours

You provide

ERP extract with material, plant, routing, and supplier data, plus two years of transaction data

You get

Error report by class, top findings with impact, cleansed correction list, recommendation

No major project. Your IT provides the extract, your business teams approve the findings. We estimate the effort during scoping.

Companies working with paretos

  • Otto Group
  • bonprix
  • LASCANA
  • Würth MODYF
  • AAA-Pharma
  • Hermes Einrichtungs Service
  • Pietsch
  • adapa
  • Otto Group
  • bonprix
  • LASCANA
  • Würth MODYF
  • AAA-Pharma
  • Hermes Einrichtungs Service
  • Pietsch
  • adapa
  • HelloFresh
  • Hermes
  • schülke
  • Faller Packaging
  • Pfenning
  • perpedes
  • Spektrum
  • premiumXL
  • HelloFresh
  • Hermes
  • schülke
  • Faller Packaging
  • Pfenning
  • perpedes
  • Spektrum
  • premiumXL

Socrates finds, corrects, recommends.

  • Finds

    Typos, contradictions, and different values for the same machine at different sites, in SAP, Microsoft Dynamics 365, and other ERP systems.

  • Corrects

    Clear-cut typos and formatting errors, based on rules you define up front.

  • Recommends

    Everything else comes with a suggestion, your business teams approve.

Socrates shows the error report after the Health Check: findings by error class and plant, typos and formatting errors corrected automatically, and the three biggest levers with ownership. Screenshot in German. Sample data.

The problem

Master data errors are costly and stay invisible.

Whether SAP, Microsoft Dynamics 365, or another ERP system, teams maintain many fields in the ERP by hand. Whatever is wrong there flows unchecked into planning, MRP, and forecasting.

Maintained by hand, used unchecked.

Every typo in the material master ends up in MRP, planning, and forecasting.

Same machine, different values.

Two plants run the same equipment. The system still shows different setup times.

Data that contradicts itself.

End of life comes before launch, and the launch date comes after the first sale.

5 full-time employees

is what a mid-sized manufacturer dedicates to master data maintenance alone on average, often more.

Anonymized example

Why now

Clean up before your ERP migration, then migrate only once.

AI and planning projects need a reliable data foundation. And every ERP change forces you to touch your master data anyway, whether you move to S/4HANA, Microsoft Dynamics 365, or another system. If you migrate flawed data, you end up fixing it in the new system.

Example SAP: maintenance deadlines for ECC 6.0 and S/4HANA

Today

Your ECC 6.0 still runs under mainstream maintenance.

In 13 months

End of 2027

SAP ends mainstream maintenance for ECC 6.0.

In just over 4 years

End of 2030

Optional extended maintenance runs out as well.

In just over 14 years

End of 2040

That is how long SAP commits to maintaining S/4HANA. What you migrate now, you will use for years.

Source: SAP press release, February 2020

How it works

Check, correct, hand over, keep clean.

Error report in Socrates: 8,725 findings in 6,180 of 48,210 records, 1,960 typos and formatting errors corrected automatically in the correction file, 6,765 awaiting approval with a suggestion, plus findings by error class and plant. Screenshot in German. Sample data.

After the check run: 8,725 findings in 6,180 records, sorted by error class and plant.

Sample data

FAQ

Frequently asked questions about the Data Health Check

What is the Data Health Check for master data?

The Data Health Check is a fixed-price offering from paretos. In 2–4 weeks, Socrates checks an extract of your ERP master data, for example from SAP, Microsoft Dynamics 365, or other ERP systems, against five error classes and against your transaction data. You get an error report by class, the most important findings with their business impact, a cleansed correction list, and a recommendation.

Do we need an IT project for the Health Check?

No. Your IT provides a data extract from your ERP and loads the correction file at the end. Your business teams approve the findings. We estimate the effort during scoping, which takes 1–2 hours.

What data does Socrates need for the check?

Material, plant, routing, and supplier data, plus two years of transaction data, from SAP, Microsoft Dynamics 365, or another ERP system. We agree on the exact field list with your IT during scoping.

Does Socrates change our master data in the ERP without approval?

No. Socrates does not write to your ERP. Socrates corrects clear-cut typos and formatting errors in the correction file, based on rules you define up front, and every change is logged. Your business teams approve everything else. Your team loads the file into the ERP.

How do the corrections get into the ERP?

Socrates creates an approved correction file that your team loads with your ERP’s standard tools. In SAP, this works via mass maintenance (transaction MASS, which changes existing records; we check during scoping which objects your system supports) or, on S/4HANA, via the Migration Cockpit. Other ERP systems have their own import or mass change functions. Alternatively, we hand over via a custom interface.

When does maintenance for SAP ECC 6.0 end?

According to SAP, mainstream maintenance for SAP Business Suite 7 with ECC 6.0 ends at the end of 2027, and optional extended maintenance at the end of 2030. For SAP S/4HANA, SAP commits to maintenance until the end of 2040.

Is it worth cleaning up master data before an ERP migration?

Yes, whether you move to S/4HANA, Microsoft Dynamics 365, or another system. Every record you clean up before the migration does not need rework in the migration project. And what you carry over clean, you will use in the new system for years.

Isn’t SAP MDG enough for clean master data?

SAP Master Data Governance (MDG) controls the creation and change of master data through workflows. Socrates works on your existing data, checks it against your transaction data, and delivers correction suggestions for approval. The two are not mutually exclusive.

Can our integrator handle the cleanup in the migration project?

Yes, but then it happens late in the project and under deadline pressure. Cleaning up beforehand gives your integrator a clean basis for the migration.

Can’t we clean up the master data ourselves in Excel?

Once, yes. But an Excel cleanup cannot be repeated, patterns across several plants are hard to spot there, and without ongoing checks the old errors come back.

Why not build our own validation rules in IT?

Validation rules are the easy part. The hard work is matching against transaction data, the approval workflow for business teams, and ongoing maintenance.

Where is our data stored?

Exclusively in the EU, for storage, processing, and AI model calls. Your data is never used to train models and is logically separated from other customers.

Data Health Check

In 2–4 weeks, you will know how good your master data really is.

In the first call, we clarify which data is affected and what the Health Check would examine at your company. If it is a fit, we start with scoping.

Book a call
Ben EdlichDecision Intelligence Consultant
Nils KlingelhöferDecision Intelligence Consultant

Sources: maintenance periods according to the SAP press release from February 2020. The figure of five full-time employees is anonymized. All other examples and values are for illustration.