Clean Core Strategy
Knowledge Hub
Clean Core & BTP Reference Hub
Discover the technical architectures, security guidelines, and extensibility patterns approved by SAP for S/4HANA clean-core compliance.
Frequently Asked Questions
Structured architectural explanations for developers and crawler extraction
Extensibility Models
What is the difference between In-App RAP and Side-by-Side CAP extensions?
Security Architecture
How does Clean-Core.io secure Side-by-Side BTP integration?
Tenant Security
What is the BYOT (Bring Your Own Tenant) connectivity model?
Automation Engine
How does Clean-Core.io automate legacy ABAP modernization?
Key Terms
A quick glossary mapping technical SAP terms to modern integration architectures:
- SAP BTP (Business Technology Platform)
- The integration and extension platform for SAP applications. It enables the development of side-by-side extensions, data orchestration, and custom cloud-native business processes separate from the ERP core.
- SAP Cloud Connector
- A secure software link that runs inside the customer's on-premise or private cloud network, establishing an encrypted TLS connection to SAP BTP without requiring complex inbound firewall configurations.
- OData (Open Data Protocol)
- An OASIS standard protocol defining best practices for building and consuming RESTful APIs. It is the default communication standard for SAP S/4HANA business services.
- CDS (Core Data Services)
- The data modeling infrastructure used by SAP. CDS views define database tables, relationships, and service projections declaratively inside both the ABAP environment (RAP) and the Node.js/Java environment (CAP).
Extensibility Paradigm Comparison
Decision framework comparing SAP RAP and BTP CAP extension routes
| Feature / Criteria | In-App RAP (ABAP RESTful) | Side-by-Side CAP (SAP BTP) |
|---|---|---|
| Runtime Environment | Directly inside SAP S/4HANA (ABAP stack) | SAP BTP (Node.js, Java, Cloud Foundry/Kyma) |
| Primary Use Case | Modifying/enhancing standard SAP business logic | Standalone apps, partner SaaS, multi-system integration |
| Development Languages | Modern ABAP (Cloud-enabled subset) | JavaScript, TypeScript, Java |
| Database Access | Native SQL on HANA via CDS views | OData, REST, or database targets (HANA, PG, SQLite) |
| Core Decoupling | High logical coupling (shares SAP memory) | Complete architectural separation (connected via APIs) |
| Upgrade Impact | Zero impact (uses officially released SAP APIs) | Zero impact (completely independent execution) |
SAP Verified Extensibility Compliance
Clean-Core.io leverages standard SAP technologies, securing transactions according to the SAP Cloud SDK guidelines. Keep your ERP core system upgradeable while expanding functionality with cloud-native scalability.
SAP Verified Strategy