Self-audit
Clean Core readiness self-audit
Answer honestly about your custom ABAP. Each risky practice is weighted by how hard it blocks Clean Core; the result is a readiness score plus a remediation list sorted worst-first, each linked to the module that fixes it. This is a triage — the authoritative check is ATC with the ABAP_CLOUD_DEVELOPMENT_DEFAULT variant on your target system.
- 1Data writes
Does your code write directly to SAP standard tables (UPDATE / MODIFY / INSERT / DELETE on an SAP table)?
Direct writes bypass application logic and break on data-model changes.
- 2Modifications
Do you modify SAP standard objects or rely on implicit enhancements?
- 3Data reads
Do you SELECT from physical SAP tables (MARA, VBAK, BSID, …) rather than released CDS interface views (I_*)?
- 4Integration
Do you automate transactions with BDC / CALL TRANSACTION (batch input)?
Batch input replays the UI and is not available on ABAP Cloud.
- 5UI
Are your apps built on SAP GUI (Dynpro, full-screen ALV, module pools)?
- 6Security
Do you build dynamic WHERE / ORDER BY by concatenating user input into the statement?
- 7Performance
Do hot paths contain SELECT * or SELECTs inside loops (N+1 reads)?
- 8System fields
Do you read restricted system fields directly (sy-uname, sy-datum, sy-mandt) instead of a released context API?
- 9Configuration
Are org values and thresholds hardcoded as literals in the code (company codes, batch sizes, plant ranges)?
- 10Tooling
Is the package's ABAP language version set to 'ABAP for Cloud Development' on new objects?
Pinning it makes Clean-Core violations fail at compile time, not just in ATC.
- 11Tooling
Do you run ATC with the Clean Core variants regularly (ABAP_CLOUD_DEVELOPMENT_DEFAULT or ABAP_CLEAN_CORE_DEVELOPMENT, plus the target-release S4HANA_READINESS_<year>)?