DQC

DQC for SAP: Material data that is right the first time and Material mass improvements

DQC logo with the title "DQC for SAP" over a glass atrium

Every new material in SAP is a chance for bad data to get in. With DQC, material data is checked against your rules before it is saved, completed from similar existing materials, and corrections from DQC flow back into SAP under your control. No data migration, no change to your data model.

Most data quality problems in SAP do not start in a migration project. They start on an ordinary day, in an ordinary transaction: a material number that already exists, an English short text that describes something else, an empty material group, a missing commodity code. Each gap is small. Downstream, in purchasing, logistics, customs, and reporting, they add up.

DQC addresses this in both directions. It stops bad data at the point of entry, and it writes improvements for existing data back into SAP. The two short videos below show both directions in an SAP S/4HANA system.

Check before saving and auto improve with DQC

Finding errors is half the job. With Improve with DQC, the user starts an improvement flow that builds the new material from the most similar existing one:

  1. Data input: one new material with five findings from the ruleset.

  2. Reference material lookup: the most similar material is 2000-1202 (96 % similar), based on five neighbours.

  3. Data enrichment (AI): seven values are proposed.

  4. Verification against the ruleset: the improved material is validated again through the DQC Validation API.

DQC SAP Validation API and Automatic (agentic) Improvements

A new material is checked against the DQC ruleset before it is saved in SAP, then completed from the most similar existing material.

The business team owns the rules

The rules do not live in ABAP code. They live in DQC, where the business team manages them. The ruleset behind the demo has 17 active rules, including:

  • Material number is not yet used (MATNR)

  • German and English short texts are maintained (MAKTX)

  • Short texts contain no superfluous spaces

  • Material group is maintained (MATKL)

  • Net weight does not exceed gross weight (NTGEW, BRGEW)

  • EAN is not used by another material

New rules can be described in plain language. Ask the DQC assistant for "English short text is max 40 characters", and it prepares a rule that checks MAKTX_EN for at most 40 characters, ready for review.

Every rule runs against the actual material master data. The same ruleset monitors your existing data and is available through the Validation API for any application that creates or changes materials. One set of rules for prevention and monitoring.

Corrections back into SAP, under your control

Prevention covers new data. Your existing material master also needs attention, and a list of findings is only useful once the corrections are back in SAP.

In the second video, a DQC improvement flow has checked series consistency across material group, commodity code, country of origin, and weight unit. In SAP, the Import DQC Improvements app loads the latest run: 885 proposals for 850 materials, each compared with the current value in SAP, read live.

DQC Write Back Integration into Core Data Systems

885 proposals from a DQC improvement flow are reviewed in SAP, and 774 corrections are posted back to the material master.

Each proposal shows the current value, a confidence score, and the reasoning.

You decide the threshold. In the demo, all 774 proposals with a confidence of at least 90 % are preselected. Proposals below the threshold stay in the list for manual review. You can filter by field and change the selection before anything is written.

One click on Post to SAP updates the material master through the SAP BTP integration: 774 field changes on 768 materials, 0 errors. Every change creates a change log entry that references the DQC flow run, so every update can be traced back to its source and reasoning.

What it takes to connect

SAP is a standard connector in DQC. Your SAP IT team sets up a technical user and connects SAP to the DQC platform over the network. Validation and writeback then run through API calls.

The business team decides the rules and the data. There is no data migration and no change to your data model. Setup takes days, not weeks.

Start with one process

Pick the process where bad data hurts most, for example material creation or a specific set of fields in your existing material master. Define the rules with your business team, check before saving, and write the first corrections back.

Contact DQC to connect your SAP system