SAP / SAP Senior Level (10+ yrs) Interview questions
What extensibility options are considered "clean" under this philosophy?
Clean extensibility means building custom logic through mechanisms SAP explicitly supports and guarantees compatibility for, rather than reaching into unreleased, internal core objects that could change without notice.
| Clean | Not Clean |
| In-app extensibility using released, stable APIs/CDS Views (key user tools, RAP-based custom fields). | Direct modification of standard SAP objects/code. |
| Side-by-side extensions on SAP BTP calling released APIs. | Enhancements/user-exits touching unreleased internal logic. |
| ABAP Cloud development model, restricted to released objects. | Classical ABAP development with full, unrestricted core access. |
The common thread across every "clean" option is that it relies on SAP's own stable, released extension points — ones SAP commits to maintaining compatibility for across releases — rather than depending on internal implementation details that are free to change without warning.
More Related questions...