What does it actually look like? Below are the screens a
functional consultant works in, from defining a View through to
running a Variant and reading the result. All examples use a
sample PMD_05_MARC_05 View on the
ARTICLE domain.
SM34 view-cluster · functional consultant
The TCOMP setup transaction opens an SE54 view cluster with the same shape on every screen. Pick a View on the right; drill into its Tables, Joins, Fields, and Long Texts via the Dialog Structure on the left.
| View Name | Description | Compare | Batch Rows | Open SQL | |
|---|---|---|---|---|---|
PMD_05_MARC_05 | PMD · MARC daily drift check | In DB | 400 000 | ||
BP_ADDR_05 | BP · Address consistency | In DB | 200 000 | ||
CONTRACT_05_EKKO_05 | Contract · EKKO + EKPO weekly | In DB | 200 000 | ||
PRICE_KONP_05 | Pricing · KONH + KONP daily | In DB | 400 000 | ||
CUST_T001W_05 | Customising · plant table | In DB | 50 000 |
Screen 1 — five Views configured. Each one is a self-contained comparison shape. Variants are built on top of these.
View → Tables
For the PMD_05_MARC_05 View, three tables: MARA at
tab level 01 (the most fundamental), then MARC and MVKE joined
upward. The "All Fields" flag picks every column; otherwise the
consultant lists fields explicitly on the next screen.
| Tab. Lvl | Sort | Table Name | All Fields | Check Type | Description | |
|---|---|---|---|---|---|---|
| 01 | 10 | MARA | Display | General article master | ||
| 02 | 10 | MARC | Error | Article + plant | ||
| 02 | 20 | MVKE | Display | Article + sales org |
Screen 2 — MARA at the bottom; MARC and MVKE join upward via the keys. Field-level overrides on the next screen.
Join Conditions and Fields, side by side
Join Conditions say how MARC and MVKE attach to MARA — usually via MATNR. Fields set the check type per column: Display (key fields), Warning, Error, Exclude, Always Display.
| Join | Lvl | Table | Field | Ref. Value | |
|---|---|---|---|---|---|
| Table | 01 | MARA | MATNR | — | |
| Constant | — | MARC | WERKS | = ER01 |
| Sort | Lvl | Table | Field | Key | Check Type | |
|---|---|---|---|---|---|---|
| 10 | 01 | MARA | MATNR | Display | ||
| 20 | 02 | MARC | WERKS | Display | ||
| 30 | 02 | MARC | MMSTA | Error | ||
| 40 | 02 | MARC | DISPO | Warning | ||
| 50 | 02 | MVKE | VKORG | Display | ||
| 60 | 02 | MVKE | VTWEG | Display | ||
| 70 | 02 | MVKE | VMSTA | Error |
Screen 3 — Joins (constant filter on plant) + Fields with check types. Errors red, Warnings amber, key fields are always displayed.
TCOMP main transaction · ABAP report selection screen
One screen with two panes. Execution & Output Parameters on the left — what to run, against which system, in which mode. Selection Criteria on the right — every field of every table in the View, ready to be filtered. Save the whole thing as a SAP variant.
Mode
Status Criteria
| Tab. Lvl | Sort | Table | Field | Desc. | Value | Post · A | Post · B |
|---|---|---|---|---|---|---|---|
| 1 | BUT000 | CLIENT | Client | ⇲ | ⇲ | ⇲ | |
| 1 | BUT000 | PARTNER | Partner | ⇲ | ⇲ | ⇲ | |
| 1 | BUT000 | TYPE | Partn. Cat. | ⇲ | ⇲ | ⇲ | |
| 1 | BUT000 | BPKIND | Part. Type | ⇲ | ⇲ | ⇲ | |
| 1 | BUT000 | BU_GROUP | Grouping | ⇲ | ⇲ | ⇲ | |
| 1 | BUT000 | BPEXT | Extern. No. | ⇲ | ⇲ | ⇲ | |
| 1 | BUT000 | BU_SORT1 | SrchTerm 1 | ⇲ | ⇲ | ⇲ | |
| 1 | BUT000 | BU_SORT2 | SrchTerm 2 | ⇲ | ⇲ | ⇲ | |
| 1 | BUT000 | SOURCE | Origin | ⇲ | ⇲ | ⇲ | |
| 1 | BUT000 | TITLE | Title | ⇲ | ⇲ | ⇲ | |
| 1 | BUT000 | XDELE | Arch. Flag | ⇲ | ⇲ | ⇲ | |
| 1 | BUT000 | XBLCK | Central | ⇲ | ⇲ | ⇲ | |
| 1 | BUT000 | AUGRP | Auth grp. | ⇲ | ⇲ | ⇲ | |
| … and so on for every field of every table in the View. | |||||||
Screen 4 — the real variant screen for View BP.
Sample RFC_SYS_B as the comparison target. The
"Selection Criteria" pane shows every field of every table in
the View; each row has its own value-help button per system
("Post · A" = current system, "Post · B" = the RFC target).
Save the whole configuration as a SAP variant, then hand it
to WLA.
TCOMP result viewer · colour-coded ALV
One row per key combination. Two status columns at the front (Status A — current system; Status B — RFC target), then the key fields, then every checked field shown as a side-by-side pair ("A BP Category" / "B BP Category", "A Grouping" / "B Grouping", and so on). The header summary tells you at a glance how many records exist on each side; the Summary button opens a per-field findings breakdown.
| Status A | Status B | Partner | Customer | Supplier | A · BP Category | B · BP Category | A · Grouping | B · Grouping | A · Search Term 1 | B · Search Term 1 |
|---|---|---|---|---|---|---|---|---|---|---|
101 | 100000 |
2 | 0001 | MERCH NF1 | ||||||
105 | 100004 |
2 | 0001 | MERCH S1 | ||||||
100002 | 100002 | 2 | ZI00 | A190 | ||||||
1900050 | 1900050 |
2 | ZS01 | DUAL | ||||||
G334 | G334 | G334 |
2 | S100 | 505-038 | |||||
G335 | G335 | G335 |
2 | S100 | 505-039 | |||||
G335 | G335 | G335 |
2 | S100 | 505-039 | |||||
G336 | G336 | G336 |
2 | S100 | 505-040 | |||||
| … 14 293 more rows | ||||||||||
Screen 5 — same View as Screen 4 (BP) but
executed. means "row exists in this system";
means "key combination missing here". Each Error /
Warning field in the View becomes a side-by-side
("A · field" / "B · field") column pair so the discrepancy is
one glance away. Click Summary for the per-field
findings breakdown ↓
Screen 5b — the Summary modal: same header counts, plus a per-field findings table grouped by Check Type (Error / Warning). Click any row → the ALV behind it filters to just those rows. Mirrors how the team triages "what's actually broken in this run".
External · linked via correlation_id
Each Group + View + GroupNo gets one stable
correlation_id. Every TCOMP run pushes a fresh
payload to ServiceNow; the incident state lifecycle is steered
entirely by the error count.
TCOMP · PMD_05_MARC_05 · 17 deviations
| Date | Comment |
|---|---|
| 2026-05-08 06:14 | Auto-opened by TCOMP. 17 deviations across System B / System C / System D. |
| 2026-05-09 06:11 | Daily run · External ID updated · 17 deviations remain. |
| 2026-05-10 06:09 | Daily run · External ID updated · 14 deviations remain. |
Screen 6 — once the next clean run arrives, this incident auto-closes with the standard note: "The errors no longer appear in the Table Comparison Tool."
Every domain — articles, BPs, contracts, pricing, customising — slots into the same Dialog Structure. Configure once, run on schedule, watch the incidents close themselves.
See real situations → How to install