Public Cloud Extensions (S/4HANA Cloud)
Extensibility in SAP S/4HANA Cloud Public Edition — the most restrictive but most upgrade-safe environment. Only Key User tools and Tier 3 side-by-side extensions are available. No ABAP developer access.
Architecture Overview
Executive Summary
S/4HANA Cloud Public Edition (formerly S/4HANA Cloud, essentials edition) is SAP's multi-tenant SaaS offering. SAP manages all infrastructure, upgrades (quarterly), and the ABAP codebase. Customers have no ABAP developer access — only Key User tools and side-by-side BTP extensions. This is the most restricted extensibility model but also the most upgrade-safe: SAP handles all upgrades automatically every quarter.
Quarterly Upgrade Cadence
- Release frequency
- 4× per year (quarterly)
- API deprecation window
- As short as 2 release cycles
- ABAP access
- None — SAP-managed codebase
- Upgrade managed by
- SAP (automatic, no customer effort)
Available Extension Patterns
| Pattern | Available | Notes |
|---|---|---|
| Custom Fields (F1481) | ✅ Yes | YY1_ prefix, auto-OData |
| Custom Business Objects | ✅ Yes | With UI and OData |
| Business Rules | ✅ Yes | No transport needed |
| SSCUI Configuration | ✅ Yes | All config via Fiori |
| Released BAdI implementation | ⚠️ Limited | Some BAdIs via guided UI |
| Custom ABAP development | ❌ No | Not available in Public Cloud |
| Side-by-side CAP on BTP | ✅ Yes | Via released OData V4 APIs |
| SAP Build Apps | ✅ Yes | Consumes S/4 APIs |
| Build Process Automation | ✅ Yes | Workflow on BTP |
| Integration Suite | ✅ Yes | A2A and B2B |
API Access & Communication Arrangements
All API access is through the SAP API Business Hub catalog. APIs are versioned (v1, v2). The Communication Arrangement concept replaces Cloud Connector for Public Cloud — BTP apps connect to S/4HANA Cloud via Communication Arrangements using OAuth 2.0 client credentials.
# S/4HANA Cloud Public Edition API access setup
# (Communication Arrangement — replaces Cloud Connector for Public Cloud)
# 1. In S/4HANA Cloud: Create Communication System
# App: Manage Communication Systems
# System ID: BTP_CAP_PROD
# Host: <btp-subaccount>.cfapps.eu10.hana.ondemand.com
# OAuth 2.0 Client ID: <from BTP XSUAA service binding>
# 2. Create Communication Arrangement
# App: Manage Communication Arrangements
# Scenario: SAP_COM_0193 (Sales Order API V2 — OData V4)
# Communication System: BTP_CAP_PROD
# Authentication: OAuth 2.0
# 3. In CAP app (.cdsrc.json)
# credentials.destination: S4C_PROD
# (Destination configured with Communication Arrangement credentials)Enterprise Example — UAE Public Sector
A UAE public sector organisation running S/4HANA Cloud Public Edition:
- 15 Custom Fields added to Purchase Order and Asset Management modules
- 3 Custom Business Objects: Asset Inspection, Compliance Certificate, Permit Tracker
- 2 CAP side-by-side extensions on BTP: Advanced Procurement Analytics + Permit Workflow
- Integration Suite connecting S/4HANA Cloud to legacy Oracle Finance (A2A iFlow)
- Zero ABAP development — full Key User + BTP model
Best Practices
Public Cloud upgrades quarterly — new features arrive fast and API deprecations move faster than on-premise.
Monitor help.sap.com "What's New" for S/4HANA Cloud to catch API deprecations before they affect your extensions.
Communication Arrangements (OAuth 2.0) are the mandatory connectivity pattern for BTP-to-S/4C — not username/password.
All side-by-side extensions must be regression-tested against the Preview tenant before SAP rolls out the quarterly release.
Tighter integration with Public Cloud than custom CAP workflows; supports standard S/4C approval processes natively.