Clean Core General
A knowledge-base assistant for Enterprise Architects and Architecture Advisors at SAP. Covers all five SAP Clean Core principles — Extensibility, Integration, Data, Business Processes, and Operations. Start with clean-core-general for overview and cross-cutting questions; use the principle-specific skills for deep guidance. Also generates ATC assessment dashboards from SAP ATC findings exports.
Use this skill when the user asks questions about SAP Clean Core Extensibility — including extension levels (A–D), on-stack vs. side-by-side extensibility, ABAP Cloud development model, ATC setup, KPI measurement (clean core share, technical debt score, unused code share, business modifications), Governance & Maturity Assessment practices (EXT-GOV-01 through EXT-SYS-05), RISE with SAP Methodology, Project Kernseife, the SAP API Policy, SAP Build and Joule Studio, or Get Clean / Stay Clean patterns. Also use when the user asks about the RISE with SAP Methodology Dashboard Extensibility section — Technical Debt Score, Clean Core Level distribution (A/B/C/D), Execution of Customer Objects, Business Modifications, Unused Customer Objects, ATC level mapping, the Customer Objects deep-dive, the Business Modifications deep-dive, or Object Type Harmonization (effective August 2026). For the full dashboard reference, use `clean-core-general`. For broad clean core overview questions, use `clean-core-general` first.
Use this skill when the user asks questions about SAP Clean Core Operations — including what clean core operations is, the four cornerstones of clean operations, Conway's Law and its impact on SAP transformations, the Customer Centre of Expertise (cCOE), Solution Standardization Board (SSB), Operations Control Center (OCC), SAP Activate and RISE with SAP Methodology, governance and operational practices (OPS-01 through OPS-08), the six Operations KPI categories, software stack currency, test management, software delivery efficiency, SAP Cloud ALM, SAP Focused Run, SAP Secure Operations Map, or the Autonomous Enterprise vision. Also use when the user asks about the RISE with SAP Methodology Dashboard Operations View — the Operations Score, Security score, System Health score, or Operations Setup score and their metrics, SLAs, and calculation formulas. Also use when the user asks about KPIs or governance maturity for the operations dimension. For broad clean core questions, use `clean-core-general` first.
Use this skill when the user asks questions about SAP Clean Core Data — including what clean core data is, the five data pillars (data strategy, data governance, data quality, data volume efficiency, data protection), master data management with SAP Master Data Governance, data quality dimensions and the Data Quality Index, data profiling with SAP Information Steward, data volume efficiency and tiering, data lifecycle management and archiving with SAP ILM, data protection principles, SAP Business Data Cloud, SAP Datasphere, SAP Master Data Integration, SAP One Domain Model, the data product economy, or how to achieve clean data as part of RISE with SAP. Also use when the user asks about data KPIs (data volume efficiency, data quality index), governance maturity practices (DAT-01 through DAT-05), or how the RISE with SAP Methodology Dashboard measures data KPIs. For the full dashboard reference, use `clean-core-general`. For broad clean core overview questions, use `clean-core-general` first.
Generates a Clean Core ATC Assessment Dashboard from an SAP ATC findings ZIP export. Produces a self-contained HTML report in SAP Horizon look & feel covering: Technical Debt Score, Potential Score (successor-aware), Clean Core Level Distribution (Level B/C/D per object using worst-finding logic), top objects and packages by debt score, top objects by Level D (P1 error) findings, top referenced SAP objects by impact, and per-package top-3 referenced SAP objects. Use this skill whenever the user provides or mentions an ATC findings ZIP file, wants to analyse their clean core technical debt, asks for a clean core dashboard, wants to understand their Level D / Level C distribution, or asks about technical debt score, potential score, or successor-available findings.