Skip to content

Extensibility & platform governance

Clean Core &
SAP BAIP

Extend SAP without compromising the next upgrade.

Decide what stays in the SAP transaction, what deserves its own lifecycle and how each extension will be secured, released and operated.

Explore extension choices
Joule, SAP Autonomous Suite and SAP Business AI Platform
SAP Business AI Platform and SAP Autonomous Suite · Source SAP

Start with the transaction boundary.

The strongest placement decision starts with what must happen inside the SAP transaction and what can run independently through a supported contract.

Business authority

Which system owns the decision, the data and the posting? Which checks must run before the SAP transaction commits?

Upgrade exposure

Which SAP objects does the extension depend on? Verify the release and support status for the target edition and version.

Lifecycle ownership

Who deploys the extension, operates it and handles failed exchanges? What does that operating model cost?

Extensibility Decision Explorer

Where should the extension live?

Check standard fit first. Compare supported in-app changes, local developer extensions and side-by-side applications as the requirement warrants.

Standard & Configuration

Architecture challenge
The requirement can be met by an existing SAP process or a supported configuration choice.

Relevant decision criteria
Confirm standard fit with a process walkthrough and representative data.
Principal trade-offs
Less custom code to own. The business may need to adjust its process or controls.
Architecture implications
Keep transactional behavior, data and process ownership within the existing SAP scope.
Governance considerations
Record the fit-to-standard decision, process owner and regression evidence.

In-App / Key User

Architecture challenge
A supported field, layout or rule is needed inside an existing SAP process.

Relevant decision criteria
Check the extensibility tools, supported scope and transport path for the target release.
Principal trade-offs
A focused in-app change can be simpler to support. Its reach depends on the available extension points.
Architecture implications
Use supported mechanisms and verify downstream effects on authorizations, reporting and interfaces.
Governance considerations
Assign ownership and test the full process in the target environment.

On-Stack ABAP Cloud

Architecture challenge
The rule must participate in SAP-local processing, or the extension needs a local business object.

Relevant decision criteria
Confirm transaction semantics and suitable released local objects, APIs or BAdIs.
Principal trade-offs
Local implementation can protect transaction consistency. The extension shares the SAP release lifecycle.
Architecture implications
Keep the local scope bounded. Evaluate the appropriate RAP model for a new business object.
Governance considerations
Review dependencies, authorization, ATC findings, relevant tests and deployment readiness.

Side-by-Side

Architecture challenge
The application or workflow needs its own lifecycle and can interact with SAP through supported remote contracts.

Relevant decision criteria
Compare SAP BTP capabilities and enterprise runtimes. Check API or event fit, security, skills and total cost.
Principal trade-offs
Independent releases add flexibility. Distributed processing adds latency, failure modes and support obligations.
Architecture implications
Keep SAP authoritative for its transactions. Define data ownership, retries and reconciliation across boundaries.
Governance considerations
Confirm entitlement or capacity, runtime ownership, telemetry, promotion and recovery before go-live.

For an independent application, SAP-centric landscapes may evaluate SAP BTP capabilities first. Enterprises with established application platforms may start there. In either case, verify the SAP-side contract, operational fit and total cost.

Govern the portfolio across its actual boundaries.

SAP Business AI Platform (BAIP) brings together capabilities for applications, integration, data and AI. SAP Business Technology Platform (BTP) capabilities are a core part of that portfolio and retain their own account model.

BTP account design

Organize directories around accountable domains and separate production from non-production in subaccounts.

  • Applications & Extensions
  • Integration
  • Data & AI
  • Platform & Operations

Tenant & service ownership

Map each service to its provisioning model. Register separately provisioned services, such as SAP Business Data Cloud where applicable, with their owners, region, trust and entitlements.

Release, cost & AI controls

Confirm promotion and recovery per service, with named operators and cost owners. For agent workloads, define permitted actions, access to business context, evaluation and human oversight.

Turn the design decision into release evidence.

Translate the placement decision into checks that delivery and operations teams can verify before the extension goes live.

Architecture decision
Record standard fit, transaction ownership, runtime alternatives and the released interfaces in an Architecture Decision Record (ADR). Review placement deviations and technical Clean Core exceptions on their own merits.
Engineering design
Use ABAP Cloud where supported. For compatible new RAP business objects, start with Managed. Evaluate Managed with Unmanaged Save when an existing API owns persistence. Justify fully Unmanaged behavior when the interaction model requires it.
Promotion readiness
Review relevant ABAP Test Cockpit checks, tests for authorization and failure handling, transport and recovery evidence, monitoring and operational ownership. Give each approved exception a review or retirement date.

Architecture Deliverables

A placement framework, a platform governance guide and engineering standards that make the decision reviewable and executable.

Architecture in Practice

Two illustrative examples show how transaction ownership changes the placement decision.

Validate before a posting commits

Check configuration and a supported in-app rule first. If developer logic must run during the posting, evaluate a released local extension point and keep the approved rule within the transaction. Test both the accepted and rejected posting paths.

Coordinate a cross-system approval

Run the approval in an independent workflow when its lifecycle spans multiple systems. Use a released interface for the resulting SAP action, keep SAP authoritative for the posting, and assign ownership for retries and reconciliation.