Skip to content
Ixia Consulting
Ixia DQ Platform

SAP ECC and SAP S/4HANA

Continuous data quality monitoring for SAP.

For organisations whose customer, business partner, material and sales area data has to be right every day, not only at go-live. Nothing is installed on SAP: Ixia DQ reads extracts or SQL views.

Request a demoTechnical overview
Rule Builder screen defining an SAP data quality rule with identity, blank-check logic on an SAP column, severity and business context
A rule in business terms: an SAP field, a logic type, a severity, and why the check exists.

SAP accepts it. The business process does not.

Profiling finds the technically invalid. Only rules the business wrote find the business-invalid.

Customer master data
Account group, country, region, tax numbers and payment terms on KNA1, KNB1 and KNVV. A blank or invalid value fails quietly until an order, a delivery or an invoice hits it.
Business partners
Customers and vendors converge in S/4HANA. Every duplicate pair left in ECC becomes a conversion decision; every one left afterwards splits history.
Material master data
Base unit of measure, material type, group, barcodes and descriptions decide whether a material can be bought, stocked, picked and sold.
Sales organisation extensions
A material or customer not extended to the sales organisation, channel and division it trades in does not exist for that order.
Missing and invalid values
Fields SAP does not enforce but the business depends on: delivery plant, transport zone, delivery priority. Region codes not valid for the country. Blank passes validation and fails operations.
Duplicates and cross-table checks
One legal entity under several numbers, one barcode on two products, a customer with company code data but no sales area. Individually valid, invalid as a set.

How the monitoring works for SAP.

SAP-aware rule packs
A library of 55 SAP master data rules across Customer, Material and Sales Area, 17 of them generic and shipped with every deployment. Your conventions are added in the Rule Builder without code.
Failures counted at business grain
Extracts are denormalised, so one material can sit on eleven plant rows. Every rule declares its reporting grain and a failure is counted once.
Scheduled runs with agreed exclusions
Nightly in live deployments, with inactive customers, plants and test accounts excluded by lists the data owners agreed.
Outputs the data owner can act on
A failure file per domain names the record, the field, the current value and the SAP transaction to correct it: XD02, MM02, VD02. The Power BI report and the daily email read from the same run.

SAP master data scorecard

Data quality run · nightly

0.6% overall failure rate · 3,781 of 612,400 records

CustomerKNA1 · KNB1 · KNVV

74 failures · 41,220 records

0.2% Good
MaterialMARA · MARC · MVKE · MAKT

2,988 failures · 512,640 records

0.6% Good
Sales AreaKNVV

719 failures · 58,540 records

1.2% Watch

Top rules in the latest run

RuleCheckDomainFailuresvs previous
IXIA014Duplicate EAN/GTIN across materialsMaterial2,214▲ 7
IXIA012EAN/GTIN not maintainedMaterial536▼ 12
IXIA015Delivery plant is blank on sales recordSales Area402▼ 31
IXIA016Distribution channel is blankSales Area236▼ 9
IXIA006Account group (KTOKD) is blankCustomer410
Illustrative example data, not a customer’s results. Rule codes are from the generic Ixia rule pack; the live scorecard is the Power BI report built on the run and result tables.

Rules that ship, and rules written for you.

In the generic pack today

  • IXIA001Customer name (NAME1) is blank
  • IXIA004Country is blank
  • IXIA005Duplicate Tax/VAT number
  • IXIA006Account group (KTOKD) is blank
  • IXIA009Base unit of measure is blank
  • IXIA012EAN/GTIN not maintained
  • IXIA013EAN/GTIN check digit invalid
  • IXIA014Duplicate EAN/GTIN across materials
  • IXIA015Delivery plant is blank on sales record
  • IXIA016Distribution channel is blank
  • IXIA017Division is blank

Eleven of the 17 generic rules. Each carries a severity, the business reason and how to fix it.

Illustrative examples of customer rules

  • Delivery priority must match the customer's channel
  • Transport zone must be valid for the customer's country
  • Payment term must be allowed for the company code
  • Gross weight and volume must be populated for stocked materials
  • A material extended to a sales area must have a delivery plant

The kind of convention written per customer in the Rule Builder and agreed with the data owner. Not shipped rules; yours will differ.

Related

See it on your SAP data.

A demonstration on example data, or on one extract of yours. You leave knowing which rules apply on day one.

Request a demoTalk to Ixia