Clean code conventions
The naming, structure and language-subset conventions that make ABAP readable across a team — and the question of which of them a checker can enforce.
Showing artifacts, examples and content with confirmed ABAP Cloud applicability. View All ABAP
Overview
SAP ships a separate Cloud Editioncode pal for ABAP — Cloud EditionThe same Clean ABAP check set for ABAP Cloud, where the legacy edition cannot run.sap official, abap of code pal, because the legacy editioncode pal for ABAPATC and Code Inspector checks for the parts of Clean ABAP a static analyser can actually check, installed into a system with [abapGit](artifact:abapgit-abapgit) rather than delivered with it.sap official, abap cannot run inside a Steampunk system, so the same Clean ABAPClean ABAPSAP's open, versioned style guide for ABAP: the answer to how a piece of ABAP should be written, an agreement a team adopts rather than anything to install.sap official, abap styleguide is enforced through ATC checks in the released-API, RAP-only ABAP Cloud model too.
Not covered: Its own migration list puts about 20 of the legacy edition's 62 checks in the Cloud Edition so far, with 15 still to migrate and 8 under discussion; 19 were dropped, several because ABAP Cloud already forbids the construct they guard against (COLLECT, PERFORM) and others because the cloud check API cannot yet see comments or pragmas.
No community artifact is documented here.
Artifacts
Details
Coverage
For your agent
- Ref
capability:abap-clean-code- JSON
- /capabilities/abap-clean-code.json
- MCP
- Connecting an agent