Person

Björn Jüliger

Capabilities4

Contributes to 4
ABAP Cloud readinessABAPABAP Cloud readinesscapabilityWhether code can run in ABAP Cloud — released APIs only, no direct table access, no obsolete statements — and what to do with the code that cannot.Clean code conventionsABAPClean code conventionscapabilityThe naming, structure and language-subset conventions that make source code readable across a team — and the question of which of them a checker can enforce.Source controlABAPSource controlcapabilityKeeping source code and development objects in version control, comparing their revisions, and moving them between development environments. Managed delivery of changes belongs to [transport management](capability:change-promotion).Static analysisABAPStatic analysiscapabilityCatching problems in code before it runs: naming, obsolete statements, security findings, and compatibility with a target environment. Style linting, security scanning and cloud-readiness checks are often treated as one concern.

Entries5

Group by
EntrySignals
Contributes to5
abap-file-formats
none

SAP's specification for serialising ABAP objects to files

abapOpenChecks
none

Open-source rule pack for SAP Code Inspector and ATC

Clean ABAP
none

Open, versioned style guide for ABAP

code pal for ABAP
Functional boundary

ATC and Code Inspector checks for Clean ABAP

code pal for ABAP — Cloud Edition
none

Clean ABAP check set for ABAP Cloud

Details

For your agent
Ref
actor:bjoern-jueliger-sap
JSON
/actors/bjoern-jueliger-sap.json
MCP
Connecting an agent