Architecture decision
Extensibility Routing & Sign-Off
Classify custom ABAP against SAP Clean Core guidelines, get a deterministic RAP-vs-CAP recommendation, and gate transformation behind an explicit architect sign-off.
Stage 2 — Solution DesignWhat it is
Before any code is generated, Clean-Core.io classifies each piece of legacy custom logic against SAP’s Clean Core extensibility guidelines and routes it to the right target track: In-App Developer Extensibility (ABAP Cloud / RAP) or Side-by-Side on SAP Business Technology Platform (CAP).
The recommendation is deterministic — derived from the evidence engine (data coupling, released-API usage, transaction semantics) — not guessed by a language model.
What’s possible
- Automatic In-App RAP vs Side-by-Side CAP recommendation with a confidence score and justification
- Explicit architect sign-off gate before transformation, with an optional override + reason captured in the audit trail
- The decision is recorded against the immutable, HMAC-signed analysis run
Honest scope & limitations
- The routing is a recommendation for a qualified architect to review — not a binding decision.
- The sign-off is self-attested (recorded from your own session), not a formal organizational approval or a governed workflow.