Overall: — —
This system at the centre; every connected SAP and third-party system around it, coloured by how its interface is doing (last 7 days).
High-severity items with a 30-day horizon. Full register under Risks and next steps.
How big and how spread out the solution is.
Where the company operates on this system, what each country does, and the regulations it must meet there.
Each statutory, tax, financial and data-privacy obligation, the SAP solution that meets it, and its status. Problems first. Deadlines should be re-verified on every run.
| ID | Status | Country | Regulation | Type | Requirement | Deadline | How SAP meets it | Action |
|---|
Every application in the solution, what it does, where it runs, whether it holds personal data, and the regulations it supports.
| Application | Category | Business capability | Deployment | Countries | Personal data | Regulations supported |
|---|
Active = documents in the last 90 days and people using it. Low use = little or no recent activity. Configured or installed = set up but not used: clean-up or licence candidates. Figures are documents in the last 90 days.
Each box is one step with the document it creates. Arrows that cross lanes are integration handoffs, labelled with the technology used.
Every system this one exchanges data with, problems first. Volume is messages or records in the last 30 days; errors are the last 7 days.
| System | State | Type | Direction | What it carries | Technology | Middleware | Volume, 30 days | Errors, 7 days |
|---|
Each metric with its threshold and what it means for the business. Red first.
| Metric | Status | Value | Unit | What it means | Threshold | Evidence |
|---|
What to do, who owns it and by when. Red dot = high severity.
Overall — of 5 (—). Each dimension scored 1 (simple) to 5 (very complex).
Every risk with its evidence area and owner.
| ID | Severity | Risk | Area | Owner | Days |
|---|
Of — customizing requests, — are described human work, the build log of SAP's S/4HANA courses; finance holds — of what could be classified. Real data, read-only from SAP Learning system S4C03 (client 400) on 10 Oct 2026; the other tabs show sample data.
Each step keeps a subset of the one above.
How each of the 2,019 customizing requests was sorted.
Classified from request descriptions and course codes, so approximate. Hover a bar for a summary; click it to open the full detail panel.
The course build peaked 2017-2019 and faded after 2021.
Number of local requests that changed each view. Click a bar for detail.
Your T41K934629 is shown in bold; together the others hold about 21 objects. Click a row for detail.
| Request | Owner | Created | Description | Objects | What it configures |
|---|