← Back to Clean Core Architecture Hub
Enterprise Reality: When activating Clean Core quality gates on existing SAP systems, thousands of legacy issues immediately surface. If every warning blocks transport release, critical business enhancements freeze. The ATC Baseline Architecture decouples legacy debt suppression from strict zero-tolerance enforcement on new code.
Limited Time Deal
Master S/4HANA Clean Core Architecture & Quality Gates
Get the Complete SAP Enterprise Architecture Suite: 40 Retina architecture diagrams, 61 production-grade code listings, and decision frameworks. Use code FLASH80 at checkout for 80% OFF.
1. The Two-Pronged Clean Core Strategy
Effective enterprise Clean Core governance operates on two concurrent tracks:
- Zero New Technical Debt: Every new development (classes, CDS views, RAP services) must pass ATC check variant
ABAP_CLEAN_CORE_DEVELOPMENT with zero Priority 1 errors before transport release.
- Controlled Legacy Quarantine: Existing classic custom code is captured in an ATC Baseline. Baselined findings are suppressed during developer transports, allowing business changes to proceed without requiring immediate refactoring of the entire codebase.
2. Baseline vs. Exemption: Key Differences
| Governance Dimension |
ATC Baseline |
Formal ATC Exemption Request |
| Scope |
Mass snapshot across entire packages or whole custom landscape. |
Granular object-level or check-level exception. |
| Use Case |
Suppressing historical technical debt accumulated over 10–20 years. |
Authorizing legitimate exceptions (e.g. Tier-2 Quarantine Wrappers). |
| Expiration |
Permanent until refreshed or targeted by a decommission wave. |
Time-bound (typically 90 or 180 days with mandatory review). |
| Approval Authority |
Enterprise Architecture Board / Head of SAP COE. |
Lead Solution Architect / Quality Gate Lead. |
3. The Formal Exemption Lifecycle
When a developer legitimately requires an unreleased API (e.g., inside an isolated Tier-2 Quarantine class), the governance workflow proceeds as follows:
The 4-Stage Approval Workflow:
- Developer Request: In Eclipse ADT, right-click the ATC finding > Request Exemption. Fill out Category, Technical Justification, and Compensating Control.
- Architectural Review: Lead Architect verifies whether an alternative C1-released API exists (using the Released API Catalog).
- Time-Bound Grant: If approved, the exemption is granted with an expiration date (e.g., 90 days). The transport release blocker is cleared.
- Audit & Recertification: Prior to expiration, the system flags the exemption. The developer must either migrate to newly released SAP APIs or renew the exemption with updated justification.
4. The Myth of Pseudo-Comments in ABAP Cloud
Critical Clean Core Fact: In classic ABAP, developers frequently suppressed ATC warnings by adding pseudo-comments like "#EC CI_SUBMIT. In pure ABAP Cloud (Language Version 5), pseudo-comments DO NOT WORK against clean core rules! Obsolete statements (such as CALL FUNCTION or TABLES:) are hard compiler syntax errors, not warnings.
Pseudo-comments are only applicable in Standard ABAP (Tier-2 Quarantine packages) to suppress ATC warnings for isolated wrapper classes.
5. Check Variant Severity Classification
| Priority Level |
Transport Behavior |
Examples in ABAP_CLEAN_CORE_DEVELOPMENT |
| Priority 1 (Error) |
Hard Blocker: Transport cannot be released from CTS without formal approval. |
Direct SQL on standard tables, Dynpro screen statements, unreleased BAPI calls, non-cloud syntax. |
| Priority 2 (Warning) |
Soft Blocker: Requires developer confirmation or architectural review. |
Sub-optimal CDS view entity annotations, missing draft administrative fields, performance cautions. |
| Priority 3 (Info) |
Informational: Does not block transport release. |
Naming convention recommendations, documentation comments, minor style advice. |
Recommended Clean Core Developer Tools
Explore free client-side interactive utilities to accelerate your S/4HANA migration:
Accelerate Your SAP Transformation
Get complete architectures, downloadable code listings, and decision frameworks in the official handbooks.