SAP Build Work Zone
SAP's managed digital workplace hub on BTP — unifying SAP Fiori apps, custom micro-frontends, and third-party content into a role-based portal. Standard Edition included in RISE and GROW with SAP. Advanced Edition adds Spaces, Pages, Workflow Inbox, and Joule AI.
What is SAP Build Work Zone?
SAP Build Work Zone (formerly SAP Launchpad Service and SAP Work Zone) is a fully managed BTP service providing a unified digital workplace portal for SAP and non-SAP applications. It consolidates SAP Fiori apps (federated from S/4HANA on-premise, RISE, and GROW), custom applications built with SAP CAP or SAP Build Apps, and third-party content cards into a single role-based launchpad experience.
The service has two editions. The Standard Edition provides a BTP-hosted SAP Fiori Launchpad with content federation from S/4HANA — it is included in RISE with SAP and GROW with SAP at no additional BTP charge. The Advanced Edition extends the Standard with a full digital workplace hub: structured Spaces and Pages, SAP UI Integration Cards, a Workflow Inbox, Joule AI assistant, Microsoft Teams integration, and per-workspace analytics. Advanced Edition is licensed per active user.
Work Zone is the strategic SAP launchpad for the Clean Core scenario: all custom Fiori apps built on CAP are hosted and launched from Work Zone, not deployed into S/4HANA itself — maintaining separation between SAP standard and customer extensions.
Quick Facts
- Standard incl.
- RISE with SAP · GROW with SAP
- Advanced
- Per active user (subscription)
- Previous names
- SAP Launchpad Service · SAP Work Zone
- Protocol
- OData V4 · REST · SAP UI5 · CDM v3
- Identity
- IAS (SAML/OIDC) + IPS (SCIM 2.0)
- Dev tool
- SAP Business Application Studio
- Mobile
- SAP Mobile Start (iOS / Android)
- AI assistant
- Joule (Advanced Edition)
- MS Teams
- Embedded tab (Advanced Edition)
- Task Center
- SAP Task Center integration
Video Tutorials
Official SAP channel walkthroughs — click any card to play
12:20Work Zone — Setup & Configure
24:15Work Zone — Content Federation from S/4
20:00Work Zone — Custom UI5 App Integration
Architecture
Work Zone runs as a managed BTP service. Its architecture has three horizontal planes: the user interface plane (browser, mobile, Teams), the Work Zone service plane (Standard + Advanced capabilities), and the content and identity plane (content providers, BTP Destination Service, and SAP Cloud Identity Services).
Standard Edition vs Advanced Edition
Both editions share the same Fiori Launchpad core. The Advanced Edition adds a full digital workplace experience on top — Spaces and Pages, richer card support, workflow integration, and Joule AI. The table below shows the capability split.
SAP Build Work Zone — Standard vs Advanced Edition Capabilities
Capability | Standard EditionIncluded in RISE / GROWGenerally Available | Advanced EditionPer-user subscriptionGenerally Available |
|---|---|---|
| Core Launchpad | ||
| SAP Fiori Launchpad (BTP-hosted) | ||
| Role-based app tile catalogue | ||
| Content federation from S/4HANA (CDM v3) | ||
| Site Manager (admin console) | ||
| SAP Mobile Start (mobile launchpad) | ||
| Transport packages (import/export) | ||
| SAP Task Center (basic — limited) | Limited | |
| Digital Workplace (Advanced only) | ||
| Spaces and Pages (workspace portal) | ||
| UI Integration Cards (widgets) | ||
| Workflow Inbox (full task management) | ||
| Joule AI Assistant embedded | ||
| Microsoft Teams tab integration | ||
| SAP Build Apps embedded in pages | ||
| Third-party content cards (SharePoint) | ||
| Workspace analytics and adoption reports | ||
| Custom branding per workspace | ||
| Licensing | ||
| Included in RISE with SAP | ||
| Included in GROW with SAP | ||
| Standalone subscription | Per active user / month | |
Site Management
The Work Zone Site Manager is the administrative console for configuring launchpad sites. Site administrators can create and manage multiple sites (e.g., separate sites per business unit or region), configure content providers, import CDM from S/4HANA, manage role-to-catalogue mappings, create transport packages, and deploy site settings.
Configure site name, URL subdomain, language defaults, and branding (logo, theme colours, background). Each site has a unique URL.
Manage the content catalogue — apps, groups, roles, and spaces. Import content from CDM v3 JSON. Publish content to assigned groups.
Register content providers (S/4HANA, third-party). Configure CDM synchronisation schedule. Review import logs and errors.
Export site configurations as transport packages. Import packages in target system. Supports dev → QAS → PRD promotion workflow.
Spaces and PagesAdvanced Edition
In the Advanced Edition, Spaces are role-based portal collections (e.g., "Finance Portal", "HR Hub") that group related Pages. Pages are structured content layouts built with a visual page designer — similar to a modern intranet page builder. Content blocks on pages include app tiles, UI Integration Cards, news feeds, workflow tasks, rich text, images, and embedded videos.
Spaces
A Space is a role-based portal collection with a dedicated navigation menu. Assign a Space to one or more role collections — users see only the spaces assigned to their roles. Spaces contain multiple Pages.
Pages
A Page is a visual layout of content blocks. Each page is structured in responsive sections and columns. Pages live inside Spaces and can be reordered. Administrators design pages in the Page Designer WYSIWYG editor.
Section and Columns
Each Page section can be 1, 2, or 3 columns wide. Sections can be collapsed, themed (background colour), and given a section title. Sections are responsive — reflow to single column on mobile.
Content Blocks
Blocks fill column slots: App Launcher (tiles), UI Integration Card (widget), Text and Image (rich content), SAP Build Apps (embedded), Feed (activity), Workflow Tasks, Video, News, and divider.
Company-Wide Spaces
Administrators create company-wide spaces visible to all users (based on role collection). Individual users cannot delete company-wide pages, but can personalise their order and visibility.
My Workspace
Each user has a personal "My Workspace" space they can freely customise — add any permitted app tiles, cards, or widgets. Not editable by admins — fully user-owned.
Content Federation
Content federation allows SAP Fiori apps defined in S/4HANA (or other ABAP systems) to appear as tiles in the Work Zone launchpad — without redeploying them. The mechanism is the CDM v3 (Content Delivery Model): an S/4HANA CDM endpoint exports a JSON manifest of all Fiori app groups, catalogues, and role assignments. Work Zone pulls this manifest via a configured Content Provider, imports it into the Work Zone Content Catalogue, and maps S/4 roles to Work Zone role collections.
1// Content Provider configuration — entered via Site Manager or REST API
2// Work Zone Site Manager → Provider Manager → Add Content Provider
3{
4 "sourceSystemId": "S4H_PRD",
5 "name": "SAP S/4HANA Production",
6 "description": "Fiori app catalogue from SAP S/4HANA 2023 On-Premise",
7 "providerType": "SAP S/4HANA",
8 "destinationName": "S4H_BACKEND",
9 "destinationType": "CF",
10 "systemType": "ABAP",
11 "runtimeTarget": "ABAP",
12 "ssoMechanism": "SAMLAssertion",
13 "contentRefreshInterval": "0",
14 "enableAutomaticContentSync": true,
15 "customParameters": {
16 "sap-system": "PRD",
17 "sap-client": "100"
18 }
19}
20
21// Required BTP Destination: S4H_BACKEND
22// BTP Cockpit → Connectivity → Destinations → New Destination
23{
24 "Name": "S4H_BACKEND",
25 "Type": "HTTP",
26 "URL": "https://virtual-s4h.on-prem.company.com",
27 "ProxyType": "OnPremise",
28 "Authentication": "PrincipalPropagation",
29 "sap-client": "100",
30 "WebIDEEnabled": "true",
31 "WebIDEUsage": "odata_abap,ui5_execute_abap",
32 "HTML5.DynamicDestination": "true"
33}1// CDM v3.2 (Content Delivery Model) — simplified structure
2// Exported from SAP S/4HANA via /sap/bc/ui2/cdm3
3// Imported into Work Zone via Content Provider synchronisation
4{
5 "_version": "3.2.0",
6 "apps": [
7 {
8 "sap.app": {
9 "id": "com.company.finance.paymentrequest",
10 "type": "application",
11 "title": "Payment Request",
12 "subTitle": "Create and manage vendor payment requests",
13 "crossNavigation": {
14 "inbounds": {
15 "PaymentRequest-manage": {
16 "semanticObject": "PaymentRequest",
17 "action": "manage",
18 "title": "Manage Payment Requests",
19 "icon": "sap-icon://payment-approval",
20 "deviceTypes": {
21 "desktop": true,
22 "tablet": true,
23 "phone": false
24 }
25 }
26 }
27 }
28 },
29 "sap.flp": { "type": "application" }
30 }
31 ],
32 "catalogs": [
33 {
34 "sap.catalog": {
35 "id": "ZFIN_AP_CATALOG",
36 "title": "Accounts Payable — Finance Catalogue"
37 },
38 "apps": [
39 { "id": "com.company.finance.paymentrequest" }
40 ]
41 }
42 ],
43 "roles": [
44 {
45 "sap.role": {
46 "id": "ZFIN_AP_PROCESSOR",
47 "title": "Accounts Payable Processor"
48 },
49 "catalogs": [
50 { "id": "ZFIN_AP_CATALOG" }
51 ]
52 }
53 ]
54}Configure Destination
Create a BTP Destination pointing to the S/4HANA system URL. Use PrincipalPropagation for SSO or BasicAuth for CDM pull. For on-premise S/4HANA, use Cloud Connector (ProxyType: OnPremise).
Register Content Provider
In Site Manager → Provider Manager, register the destination as a Content Provider of type SAP S/4HANA. Set the destination name and CDM sync schedule.
Synchronise and Map Roles
Run Fetch Content to import the CDM. Imported apps appear in the Content Catalogue. Map S/4HANA roles to Work Zone role collections in Content Manager → Roles.
Role Collections and Security Model
Work Zone access is governed by BTP Role Collections. Each role collection maps to a set of Work Zone permissions. Role collections are assigned to users either manually in BTP Cockpit or automatically via Identity Provisioning (IPS) — which syncs group memberships from Azure AD (or any LDAP source) to BTP role collections via SCIM 2.0. Users authenticate via Identity Authentication (IAS), which acts as a proxy in front of the corporate identity provider.
1// Identity Provisioning (IPS) — Transformation JSON
2// Source System: Microsoft Azure AD (SCIM 2.0)
3// Target System: SAP BTP (role collection assignment)
4// Configured in SAP Cloud Identity Services cockpit
5{
6 "user": {
7 "mappings": [
8 {
9 "sourcePath": "$.userName",
10 "targetPath": "$.userName"
11 },
12 {
13 "sourcePath": "$.emails[0].value",
14 "targetPath": "$.emails[0].value",
15 "targetVariable": "entityIdSourceSystem"
16 },
17 {
18 "sourcePath": "$.displayName",
19 "targetPath": "$.displayName"
20 },
21 {
22 "sourcePath": "$.name.givenName",
23 "targetPath": "$.name.givenName"
24 },
25 {
26 "sourcePath": "$.name.familyName",
27 "targetPath": "$.name.familyName"
28 },
29 {
30 "condition": "$.groups[?(@.display == 'WZ-Admins')].value != []",
31 "targetPath": "$.groups[0].value",
32 "transformValue": { "literal": "Workzone_Admin" }
33 },
34 {
35 "condition": "$.groups[?(@.display == 'WZ-Content-Managers')].value != []",
36 "targetPath": "$.groups[1].value",
37 "transformValue": { "literal": "Workzone_Content_Manager" }
38 },
39 {
40 "condition": "$.groups[?(@.display == 'WZ-Users')].value != []",
41 "targetPath": "$.groups[2].value",
42 "transformValue": { "literal": "Launchpad_User" }
43 },
44 {
45 "condition": "$.groups[?(@.display == 'WZ-Advanced-Users')].value != []",
46 "targetPath": "$.groups[3].value",
47 "transformValue": { "literal": "Workzone_User" }
48 }
49 ]
50 }
51}// SAP Build Work Zone — Role Collections Reference
// Assign via: BTP Cockpit → Security → Role Collections → Assign Users or Groups
// ─── Standard Edition (Launchpad Service) ────────────────────────────────────
Launchpad_Admin
- Full site management via Site Manager
- Create, update, and delete sites
- Manage content providers and CDM imports
- Manage transport packages
Launchpad_User
- Access to assigned launchpad tiles and catalogues
- Personalise home page (add/remove tiles within assigned groups)
- No admin access
Launchpad_Developer
- Access to Site Manager for development configuration
- Cannot manage users or role assignments
// ─── Advanced Edition ─────────────────────────────────────────────────────────
Workzone_Admin
- All Launchpad_Admin rights
- Manage Spaces and Pages
- Manage company-wide workspaces
- Access to analytics and adoption reports
- UI Integration Card management
Workzone_User
- Licensed seat — Advanced Edition subscription required
- Access to Spaces, Pages, and personalised portal
- Access to Workflow Inbox and notifications
- Access to Joule AI assistant button
- All Launchpad_User capabilities
Workzone_Content_Manager
- Create and manage Spaces and Pages
- Publish content to assigned spaces
- Cannot manage site settings or users
Workzone_ExternalIdP
- External Identity Provider configuration access (admin only)IAS Trust Configuration
- 1BTP Cockpit → Subaccount → Trust Configuration
- 2Add custom IdP — enter IAS tenant URL
- 3Download and upload SAML metadata (SP ↔ IDP)
- 4Enable IAS as the default identity provider
- 5Disable SAP ID Service (or keep as fallback)
IPS Provisioning Setup
- 1SAP Cloud Identity Services → Identity Provisioning
- 2Add Source System: Microsoft Azure AD (SCIM 2.0)
- 3Add Target System: SAP BTP XS Advanced UAA (SCIM)
- 4Define transformation JSON (AD groups → role collections)
- 5Run provisioning job — verify BTP role collection assignments
Work Zone with SAP S/4HANA
Work Zone is the recommended launchpad for SAP S/4HANA in all deployment models. For S/4HANA on-premise and RISE (PCE), the SAP Fiori apps are hosted inside S/4HANA but launched from the Work Zone launchpad via deep links using semantic object and action navigation (SemanticObject-Action). For S/4HANA Cloud (Public Edition — GROW), the native embedded Fiori Launchpad (SAP Start) is the primary launchpad, with Work Zone Standard as the BTP-side hub.
| Deployment | App Hosting | Launchpad | Content Federation | SSO Mechanism |
|---|---|---|---|---|
| S/4HANA On-Premise | S/4HANA ABAP | Work Zone Standard | CDM v3 via Cloud Connector | IAS → SAML → S/4 |
| RISE with SAP (PCE) | S/4HANA ABAP (PCE) | Work Zone Standard | CDM v3 via Private Link | IAS → SAML → S/4 PCE |
| GROW with SAP (Public) | SAP-managed (SaaS) | SAP Start + Work Zone | CDM v3 auto-configured | IAS (GROW-managed) |
| Custom CAP on BTP | HTML5 Repo (BTP) | Work Zone (any edition) | Direct CDM v3 registration | IAS → XSUAA JWT |
Work Zone with SAP CAP
Custom Fiori Elements applications built with SAP CAP are deployed to the HTML5 Application Repository (a managed BTP service) and registered in Work Zone via CDM v3 direct registration — without requiring an S/4HANA content provider. Work Zone acts as the shell (navigation bar, theming, SSO) while the CAP OData V4 service provides the data. Authentication flows from Work Zone → IAS → XSUAA → CAP application via JWT Bearer token propagation.
Build the Fiori app
Create a Fiori Elements app (List Report, Object Page) in BAS using the CAP OData service as the data source. Generate the manifest.json with semantic object navigation.
Deploy to HTML5 Repo
Package the Fiori app into the MTAR alongside the CAP server. The HTML5 deployer module in mta.yaml uploads the built app to the HTML5 Application Repository on BTP.
Configure the Destination
Create a BTP Destination pointing to the CAP OData service URL with OAuth2JWTBearer authentication. Enable HTML5.DynamicDestination=true and HTML5.ForwardAuthToken=true.
Register in Work Zone
In Site Manager → Content Manager → Apps, create a new app entry. Set the app URL, navigation target (semantic object/action), and assign to a catalogue and role.
1// BTP Destination — CAP backend for Work Zone app embedding
2// Work Zone uses this destination to proxy requests to the CAP OData service
3// Principal propagation: user JWT from Work Zone forwarded to CAP → XSUAA validates
4{
5 "Name": "cap-bookshop-backend",
6 "Type": "HTTP",
7 "URL": "https://bookshop-srv.cfapps.eu10.hana.ondemand.com",
8 "Authentication": "OAuth2JWTBearer",
9 "ProxyType": "Internet",
10 "tokenServiceURL": "https://my-company.authentication.eu10.hana.ondemand.com/oauth/token",
11 "clientId": "sb-bookshop-cap!t1234",
12 "clientSecret": "CLIENT_SECRET_FROM_XSUAA_SERVICE_KEY",
13 "tokenServiceURLType": "Dedicated",
14 "HTML5.DynamicDestination": "true",
15 "HTML5.ForwardAuthToken": "true",
16 "sap-platform": "CF"
17}
18
19// manifest.json — Fiori app descriptor registered in Work Zone
20// The app is hosted in HTML5 Application Repository (BTP)
21{
22 "_version": "1.65.0",
23 "sap.app": {
24 "id": "com.company.bookshop",
25 "type": "application",
26 "title": "{{appTitle}}",
27 "crossNavigation": {
28 "inbounds": {
29 "Bookshop-display": {
30 "semanticObject": "Bookshop",
31 "action": "display"
32 }
33 }
34 }
35 },
36 "sap.cloud": {
37 "public": true,
38 "service": "cap-bookshop-backend"
39 }
40}Work Zone with JouleAdvanced Edition
The Work Zone Advanced Edition embeds SAP Joule as a floating AI assistant button in the Work Zone shell header. Users access Joule by clicking the Joule icon — it opens a skill panel with natural language input. Joule in Work Zone is pre-loaded with Work Zone-aware skills: task and approval management via SAP Task Center, workspace navigation, and notification management. SAP Task Center must be subscribed and configured separately to enable the approval workflow skills.
- Query and navigate workspace pages
- Find and launch apps by description
- View and approve workflow tasks (via SAP Task Center)
- Check pending notifications and alerts
- Search content within Work Zone
- Finance skills: AP, AR, cost centre queries
- MM skills: purchase order status, goods receipt
- HCM skills: leave balances, org chart
- Triggered from Work Zone shell via principal propagation
- Identity propagated via IAS JWT token chain
- Build custom skills with SAP AI SDK (GA — Q2 2025)
- Skills integrate with any OData V4 or REST API
- Skills appear in Work Zone Joule skill panel
- Skill registration via SAP BTP AI Agent service
- Access control via Work Zone role collections
Licensing and Commercial Model
The Standard Edition is bundled into RISE with SAP and GROW with SAP contracts — no additional BTP service subscription is required. The Advanced Edition is licensed per active user per month via a standalone BTP subscription or as part of a CPEA/BTPEA allocation. An "active user" is defined as a user who has logged in to a Work Zone Advanced-enabled site at least once in the billing month.
Work Zone
A central digital workplace hub — providing a unified launchpad for SAP and non-SAP applications, personalised workpages, notifications, and workflow management.
Standard edition included. Advanced edition licensed per active user — requires separate CPEA/BTPEA allocation.
Commercial Model Notes
Standard Edition
Included with RISE with SAP and GROW with SAP. No additional BTP entitlement required. The Launchpad Service is automatically subscribed as part of the bundle onboarding.
Advanced Edition
Licensed per active user per month. Minimum commitment varies by contract. Stackable on top of Standard Edition — upgrading does not remove Standard capabilities.
SAP Task Center
Separate BTP subscription required for workflow inbox and Joule approval skills. Not included in Work Zone Advanced Edition pricing. CPEA or standalone subscription.
SAP Mobile Start
The SAP Mobile Start app (iOS/Android) is free to download. BTP Mobile Services entitlement required for the backend push notification and app distribution service.
SAP Build Work Zone — Road Map and SAP Sapphire Updates
Joule AI Assistant in Work Zone Advanced
Generally AvailableJoule AI button embedded in Work Zone Advanced Edition shell. Pre-built Work Zone skills for workspace navigation, task management, and SAP S/4HANA workflow approvals (requires SAP Task Center).
Custom Joule Skills for Work Zone
Generally AvailablePartners and customers can build custom Joule skills using the SAP AI SDK. Custom skills appear in the Work Zone Joule skill panel alongside pre-built SAP skills. Requires SAP BTP AI Agent subscription.
SAP Build Apps Embedding in Pages
Generally AvailableSAP Build Apps (no-code/low-code apps) can be embedded as content blocks within Work Zone Advanced Pages. Enables business users to build and embed custom apps without developer involvement.
Microsoft Teams Bi-directional Integration
Generally AvailableWork Zone Spaces and Pages can be pinned as a Microsoft Teams tab. Notifications from Work Zone appear in Teams. Users can approve workflows from within Teams without switching to the Work Zone browser.
Work Zone Analytics Dashboard Enhancements
PlannedEnhanced adoption analytics for Work Zone Advanced — page view heatmaps, card engagement metrics, and per-workspace usage reports. Committed on SAP Road Map. Check SAP Road Map Explorer for delivery quarter.
AI-Powered Page Content Recommendations
RoadmapJoule to recommend personalised page content and app tiles based on user role and usage patterns. Direction confirmed at SAP Sapphire 2025. No GA date confirmed as of June 2025. Do not plan implementations.
Work Zone Integration with SAP Business Data Cloud
RoadmapEmbedding Business Data Cloud (BDC) analytics widgets as UI Integration Cards in Work Zone Pages. Would enable embedded BI/planning directly in the digital workplace. No GA date confirmed as of June 2025.
Best Practices
Align Work Zone sites with landscape tiers
Create separate Work Zone sites for DEV, QAS, and PRD. Use transport packages to promote site configurations — never manually recreate changes in each tier.
Use IPS for all user provisioning — avoid manual role collection assignment
Manual role collection assignment in BTP Cockpit does not scale. Automate all provisioning via IPS from Azure AD or LDAP. This ensures consistent access and simplifies offboarding.
Use semantic object navigation for all app links
Always register apps with semantic object and action navigation targets (e.g., SalesOrder-display). This ensures deep-link stability across S/4HANA upgrades — app IDs can change, semantic objects do not.
Schedule content provider sync during off-peak hours
CDM synchronisation from S/4HANA can be resource-intensive on large systems. Schedule automatic sync outside business hours. Trigger manual sync only for emergency content updates.
Test principal propagation before go-live
Principal propagation from Work Zone to S/4HANA (IAS → SAML Assertion → S/4HANA) is complex to configure. Test with a real user account — not a technical service account — in a QAS environment before going live.
Design Spaces by role, not by department
Spaces are role-collection-based, not AD-group-based. Design your Space structure around BTP role collections and map AD groups to those collections via IPS — not the other way around.
Keep company-wide Spaces minimal and governed
Publish only essential, governed content to company-wide spaces. Avoid publishing experimental or draft content there. Create a staging Space (visible to Content Managers only) for testing before promoting.
Register CAP apps in HTML5 Repo — not as external links
CAP-based Fiori apps registered as HTML5 Repo entries in Work Zone benefit from BTP CDN, cache headers, and managed deployment. Avoid registering them as generic external URL links — that bypasses the SSO chain.
Common Pitfalls
Confusing Standard and Advanced Edition role collections
Fix: Standard Edition uses Launchpad_Admin and Launchpad_User. Advanced Edition uses Workzone_Admin and Workzone_User. Assigning Launchpad_User to an Advanced Edition site gives read-only tile access — not full workspace access. Verify the role collection names match the edition subscribed.
CDM sync fails silently after S/4HANA upgrade
Fix: S/4HANA upgrades can change CDM endpoint paths or introduce new CDM version requirements. After every S/4HANA upgrade, re-test the Content Provider sync and review the import log in Site Manager → Provider Manager.
Tile launches correctly but app shows "Access Denied"
Fix: This is almost always a principal propagation issue. The user has the Work Zone role collection but lacks the matching S/4HANA role. Ensure S/4HANA role assignments are synced from the same AD source, and verify the SAML Bearer Assertion Destination is correctly configured.
Using a single Work Zone site for all S/4HANA systems
Fix: When you have multiple S/4HANA systems (ERP, SRM, HCM), each requires its own Content Provider entry. Do not aggregate all systems into one site without proper role isolation — users from one system will see irrelevant tiles from other systems.
Ignoring the HTML5 Application Repository for CAP apps
Fix: Deploying CAP Fiori apps as standalone Cloud Foundry applications (not via HTML5 Repo) results in separate URLs, broken SSO chains, and no Work Zone tile integration. Always use the html5-app-deployer module in mta.yaml.
Assuming Work Zone Advanced features are available in RISE/GROW bundles
Fix: RISE and GROW with SAP include Standard Edition only. Spaces, Pages, Workflow Inbox, and Joule require the Advanced Edition subscription — a separate line item in the BTP contract. Verify with your SAP account executive before designing Advanced features for RISE-included scope.
SAP Official References
SAP Build Work Zone — Help Portal
Complete documentation for Work Zone Advanced Edition — site management, spaces, pages, and integration guides.
SAP Build Work Zone Standard — Help Portal
Standard Edition documentation — Fiori Launchpad configuration, content federation, and IAS setup.
SAP Discovery Center — Work Zone Advanced
Service catalogue entry with pricing, trial, and learning missions for Work Zone Advanced Edition.
Content Federation Guide
Step-by-step guide for configuring Content Providers — S/4HANA on-premise and cloud.
SAP Task Center — Help Portal
SAP Task Center documentation — setup, system connectivity, and Work Zone integration for workflow inbox.
Identity Provisioning for BTP
IPS documentation — connector configuration, transformation JSON, and Azure AD to BTP provisioning.
SAP Build Work Zone Road Map
Official SAP Road Map for Work Zone — GA, Planned, and Roadmap features.
SAP Mobile Start — Help Portal
SAP Mobile Start configuration guide — BTP Mobile Services setup for Work Zone mobile launchpad.