CDQ & LANXESS Data as a Shared Asset

Master data rarely gets the spotlight in day-to-day business conversations. Yet when something goes wrong—when a delivery cannot be shipped, a payment cannot be processed, or a customer record appears ten times in the system - the importance of trusted data becomes impossible to ignore.

During the webinar “Data as a Shared Asset at LANXESS”, Katja Tintes shared how LANXESS transformed master data into a strategic foundation for global operations. By combining strong data governance, clear stewardship responsibilities, and integrated data quality checks in SAP MDG, the company built a system where data is created right the first time.

The results are tangible. From smoother supply chain operations to transparent global processes and even zero fraud cases related to bank data - trusted master data has become a backbone for operational reliability.

Below are the key insights from the session and questions from the audience.

Is the Data Wiki a standalone application, or is it integrated with SAP MDG?

At LANXESS, the Data Wiki is a separate web-based knowledge repository, similar in concept to Wikipedia. It is not directly integrated into SAP MDG, meaning users cannot navigate to it directly from the system.

The wiki documents important master data concepts, including:

• mandatory fields

• country-specific requirements (such as tax numbers)

• process explanations

• partner roles and partner functions

Maintaining the Data Wiki is an ongoing effort. Two dedicated people are responsible for keeping the information up to date: one for business partner data and one for material master data.

The goal is not only to document technical specifications but also to make data processes more understandable for business users.

How many people work in data governance, data maintenance, and data quality management?

The LANXESS setup combines central governance with distributed data stewardship.

• Around 10 people in IT globally maintain dashboards, reports, and technical infrastructure.

• Each business unit has data stewards for materials and business partners, often supported by small teams.

• Across the global stewardship community, there are roughly 30-40 people involved.

• The Master Data Services (MDS) department itself consists of 21 people, with teams located in Germany and India.

Which workflow tools are used to collect input for new business partner creation?

The workflow is managed directly inside the M4P system.

LANXESS does not use a separate workflow tool. Instead, the process is controlled through roles and authorizations within the system.

For example:

• Requesters can submit requests.

• Approval roles are assigned to specific functions.

• Final approvals are performed by the responsible master data team.

This role-based approach ensures clear responsibilities and structured approvals.

Which departments benefit the most from higher data quality and a single SAP system?

According to LANXESS, the entire organization benefits from a centralized system and improved data quality.

However, the largest impact is visible in supply chain and production.

 Transparency across the system makes it easier to track:

• shipment status

• stock availability in other plants

• delivery progress across countries

Data quality also prevents operational disruptions. For example, dangerous goods require certified packaging materials with a valid UN code stored in the master data. If this information is missing, the system will block the delivery process.

This kind of hard stop demonstrates how critical trusted master data is for operational processes.

What framework is used for defining data standards? Is DAMA DMBOK applied?

LANXESS does not follow a formal external framework such as DAMA DMBOK or Gartner guidelines.

Instead, the company has developed its own internal standards and governance framework over the years.

These standards are based on:

• regulatory requirements in different countries

• internal operational experience

• strict data quality rules designed to prevent downstream issues

In some cases, the rules are intentionally strict to ensure that data is created correctly the first time, avoiding costly corrections later.

How is CDQ incorporated into the SAP MDG system?

CDQ services are directly integrated into the SAP MDG workflows.

Within the business partner creation process, CDQ capabilities are used at several validation steps, including:

• duplicate detection

• First Time Right checks

• bank trust score validation

• tax number validation

These checks are embedded directly into the system workflows and appear as part of the operational screens used by data stewards.

Are the customer account groups shown in the slides the only ones used at LANXESS?

Yes. In the current S/4HANA landscape, LANXESS follows a lean account group concept.

The main account groups used are:

• Sold-to

• Ship-to

• Bill-to

Additional distinctions are handled through partner roles and partner functions, which allow more detailed process definitions without creating unnecessary account groups.

How are duplicates handled when they are required for business processes?

LANXESS aims to avoid duplicates entirely, but there are cases where records may appear similar while still representing different business contexts.

For example:

• A single Sold-to party may have multiple Ship-to parties with the same address but different contact persons or delivery points.

• Different departments within a customer organization may require separate business partner records.

Some countries also require special structures. In Brazil, for instance, a secondary branch setup allows two companies to share the same tax number. In these cases, the system explicitly flags the relationship to ensure the records are not treated as duplicates.