Master-data deviation monitoring for SAP

Find every quiet drift between your SAP systems — before someone else does.

TCOMP compares table content across your source system and every connected system, surfaces every discrepancy, and opens a ServiceNow incident automatically — until the data lines up again. Configurable views, scheduled background runs, one place to see what's out of sync.

See how it helps → How it works
The problem

Master data drifts the moment you stop watching it.

Every multi-system SAP landscape has the same quiet failure mode: master and transactional data is supposed to stay in sync between the source system and the connected ones, and most of the time it does — until a small process error, a botched transport, or a manual edit silently breaks the contract.

The first sign is usually a downstream blow-up: a price doesn't propagate, a delivery rejects, a finance run reconciles short. By that point you're working backwards through three systems to find a field that's been wrong for two weeks.

The idea

Run the comparison continuously, not when something breaks.

TCOMP turns "compare these two tables in those four systems" into configuration. A team picks the tables and fields that matter, marks each one as Display, Warning, or Error, and saves the bundle as a View.

From that View, anyone can build a Variant — the same View pinned to a target system, with a few selection filters and an output mode. Variants run on a schedule, hit every system over RFC, join the data, and produce a colour-coded result you can see at a glance.

When a deviation shows up, TCOMP-MDD opens a ServiceNow incident automatically. When the next run shows the deviation gone, the same incident closes itself with a one-line note.

How it works

Four moving parts. One source of truth for "are we in sync?"

A View defines the shape; a Variant pins it to a target; a scheduled run pulls the data; the result tells the story.

1

View

Pick the tables, the join conditions, and the fields you care about — each marked Display, Warning, or Error. Saved once, re-used by every variant on top of it.

2

Variant

Pin the View to one target system, layer in selection criteria and Pro Conditions, choose how the result should be delivered (display, email, save). Save it. Run it. Schedule it.

3

RFC fan-out

At run-time TCOMP fires a dynamic SELECT to every target system over RFC, batches the rows so big runs don't blow memory, and joins the data in one place.

4

Result + INC

Colour-coded ALV by row and system. Errors auto-open a ServiceNow incident; the next clean run auto-closes it. No-one forgets to update the ticket.

Why teams adopt it

Continuous data quality, no manual ticket lifecycle.

Catches drift early

Daily / weekly runs surface deviations days or weeks before downstream processes notice them.

Auto-opens + auto-closes incidents

One TCOMP correlation_id → one ServiceNow incident. Errors gone? Incident closes itself with a clear note.

Configuration, not code

Adding a new comparison is a View + Variant — maintained by master-data product teams, no ABAP ticket required.

Cross-system by design

One source system, any number of connected systems. Each Variant pins to one RFC target — fan-out is built in.

Verify your fix

The result viewer has a re-execute button — run it after a fix, and the SNOW incident closes only when the data really matches.

Safe on huge runs

Batched DB-level comparison + temp-table buffering keeps memory bounded even when comparing tens of millions of records.

Power-user Views — write the SELECT yourself

Skip the tables-and-joins editor and supply a free Open SQL statement (CTEs, window functions, conditional joins, full HANA expressiveness). TCOMP fans the same SELECT out to every target system — same result viewer, same SNOW lifecycle.

Who it's for

Anyone who has to keep two SAP systems telling the same story.

📦

Article master-data

Catch GTIN, sales-org, plant-extension drift before listings hit the shelf wrong.

🤝

Business partner teams

Vendor & customer addresses, tax IDs, payment data — same in every system or you'll find out.

📑

Contract management

Validity, conditions, partner roles. Each contract has to mean the same thing in every region.

🏷️

Pricing & conditions

Condition records and access sequences — easy to lose in transports, painful when you do.

🛠️

IT services / ADM

Auto-generated incidents land in your queue with a clear correlation ID and one-click verify.

📊

Data governance

One log table for every comparison run — the trail auditors actually want.

🏢

System architects

One framework, one transport flow, one ServiceNow contract — across every BO and every region.

🧰

Customising leads

The sister "Customising Comparison" mode keeps configuration tables aligned, not just master data.

Want to see real situations?

Five everyday cross-system mismatches — article extension gaps, partner-address drift, contract validity, pricing scale records, customising tables — and the exact result + INC the user sees.

See the use cases →

Wondering how to install it?

Five steps to enable TCOMP for a new domain — define the comparison, set up the RFC connections, save a Variant, schedule the WLA job, configure the ServiceNow templates in RSDF.

See the installation →

Want to see the app itself?

A tour of the configuration screens — View setup, Tables and Joins, Field check types, the Variant selection screen, and a colour-coded ALV result. Six mocked screenshots, one page.

Inside the app →

See what's drifted in your landscape this week.

One View, one Variant, one daily run. The first time it executes you'll already see things you didn't know were broken — and the incidents to track them through to fixed.

Read the use cases →