Work aids for daily work

Purpose

This page bundles practical guardrails for recurring decisions in daily MDM work. It is aimed at users who release relations, evaluate review results, follow up substitution changes, or want to structure daily maintenance tasks more efficiently.

Business value

• Shortens the daily classification of common MDM decisions.
• Supports a consistent assessment of releases, review errors, and follow-up work.
• Makes recurring control points for relations, DSR, substitutions, and field views more transparent.
• Complements process and FAQ pages with concrete orientation for everyday work.

Focus

Decision aid for status actions

Not every status action serves the same purpose. Releasing a relation is the standard path after a complete review, reopening brings a relation back into a controlled editable state, and release without update remains a deliberate exception for cases without retroactive redistribution.

Short checklist before release

Before every release, a compact quality review is worthwhile: Are source and target companies assigned correctly, are field rules and dependencies complete, and are special cases through exclusions or substitutions already clarified? Only when these questions are answered clearly is the relation stable enough for productive status.

It is also useful to check whether expected follow-up work such as the first consistency checks or delta updates has already been planned. This keeps the release not only technically successful, but also dependable from a business perspective.

Evaluate typical work situations compactly

In daily work, it helps to treat recurring situations differently on purpose. A new business-relevant table requires a complete setup of relation, company assignment, and rules before release. An already released relation, by contrast, starts with reopening so that changes can be maintained in a controlled and traceable way.

When target values should intentionally differ from the source company, substitutions and their follow-up processing are the primary focus. When deviations or gaps are reported, teams should first review consistency findings, field views, and potentially missing relations before changing rules or correcting data.

Assess DSR decisions safely in daily work

When records should deliberately not reach individual target companies, review the DSR filters first and then the distribution matrix. What matters is not only whether a record is distributed, but also whether the displayed decision source matches the intended business rule. After filter changes, teams should also decide consciously whether existing data should be re-evaluated immediately.

Classify review results more quickly

Consistency findings become more useful when they are not read in isolation. Always assess review entries together with the relation, the field view, the source and target company, and the question whether the deviation is intentional or really needs correction.

When several causes are possible, views such as active fields, all fields, or the source-table view help narrow the error space. This avoids unnecessary changes to rules when the real cause lies in the data.

Daily routine for open changes

In daily work, it is worth keeping a short control rhythm for open substitution changes, relations in maintenance status, and new review results. These three areas show most quickly where MDM is still not operating in the intended target state.

A simple routine is: first review open relations, then inspect substitution changes with possible delta updates, and finally evaluate the most important consistency findings. This keeps the maintenance effort manageable and prioritized.

Result

• Recurring decisions in daily MDM work are summarized in one compact orientation page.
• Release, review, and follow-up work can be assessed consistently with the same guardrails.
• The page complements the process catalog and FAQ with concrete work aids for ongoing operations.