Service offering

SAP Build Work Zone & Fiori

SAP Build Work Zone is the strategic digital workplace platform for SAP BTP — the single entry point that federates Fiori apps, business content, UI Integration Cards, tasks, and collaboration from your entire SAP landscape into one role-based launchpad. We design, configure, and govern Work Zone and Fiori implementations that drive adoption and scale with your business.

Standard EditionAdvanced EditionContent FederationSpaces & PagesUI Integration CardsSAP Task CenterFiori ElementsHTML5 App RepositoryCloud Transport MgmtUI Theme Designer

Standard Edition vs Advanced Edition

SAP Build Work Zone ships in two editions with significantly different capability scopes. Edition selection is the first architectural decision — it drives licensing, infrastructure, and the features available to your users.

Standard Edition

Fiori Launchpad on BTP

The cloud-hosted Fiori Launchpad — successor to the SAP Launchpad Service. Federates apps and content from S/4HANA, BTP, and other content providers into a unified, role-based entry point. Included in most SAP BTP subscriptions.

Spaces & Pages model for content organisation
Content federation from ABAP, S/4HANA Cloud, and BTP
BTP HTML5 App Repository hosting
UI Integration Cards on pages
SAP Task Center integration
Role-based access via IAS/IdDS groups
Custom domain & UI Theme Designer branding
Mobile via SAP Start (browser)

Advanced Edition

Enterprise Digital Workplace

Everything in Standard Edition plus a full enterprise collaboration and knowledge management layer. Powered by the Digital Workplace Service (DWS) — the successor to SAP Work Zone and SuccessFactors Work Zone.

Everything in Standard Edition
Workspaces with collaboration, blogs, forums, wiki
Workspace templates for repeatable structures
External user and guest access
Enhanced admin & content governance tools
SAP Build Process Automation deep integration
Notifications Service & Mobile Services
SuccessFactors Work Zone variant

Platform Architecture

SAP Build Work Zone is a BTP-native service that acts as the aggregation layer between your users and all content sources in your SAP landscape. Its architecture spans four distinct layers — from user access channels through to on-premise backend systems.

SAP Build Work Zone — end-to-end platform architecture

Layer 1 — User Access Channels

Desktop BrowserSAP Start (mobile)MS Teams (card embedding)MS Outlook add-inSAP GUI (Fiori on ABAP)

↕ HTTPS / SSO via IAS

Layer 2 — SAP Build Work Zone (BTP Subaccount)

Work Zone Standard / AdvancedSpaces & Pages (content model)HTML5 App RepositoryUI Integration Cards runtimeSAP Task CenterUI Theme DesignerNotifications ServiceCustom Domain ServiceDestination ServiceConnectivity ServiceSAP Cloud Identity (IAS + IdDS)

↕ OData / REST content channels · Cloud Connector tunnel (on-premise)

Layer 3 — Content Sources & Backend Systems

SAP S/4HANA Cloud (content provider)SAP S/4HANA On-Premise (via Cloud Connector)SAP NetWeaver ABAP (NW 7.x)SAP SuccessFactorsCustom BTP CAP apps (HTML5 Repo)Custom OData / REST content providers

Content Federation Architecture

Content federation is how Work Zone pulls Fiori app catalogs, tiles, spaces, and pages from backend systems and makes them available to users — without copying or duplicating the app itself. The backend remains the authoritative source; Work Zone provides the unified shell.

Content Federation: Backend → Work Zone → User

Backend SystemS/4HANA · ABAP · custom

→

Content ChannelOData content API exposed by backend

→

Content ProviderRegistered in Work Zone Admin · BTP Destination

→

Work ZoneFetches catalogs, apps, roles · assigns to Spaces

→

UserSees role-relevant apps in Spaces & Pages

Content Providers are registered in the Work Zone Administration UI, each pointing to a BTP Destination that defines the backend connection (URL, authentication, proxy type). For on-premise ABAP systems, a Cloud Connector tunnel is required — the Connectivity Service in BTP bridges the gap, and the Destination Service stores the named connection parameters.

Two content integration mechanisms are supported:

Content Providers (API-based): Work Zone actively pulls app catalogs and role assignments from the backend via an OData content channel. Changes in the backend (new app added to a role) are reflected in Work Zone on the next content sync.
Content Packages (file-based): Administrators upload pre-packaged content (pages, cards, apps) as ZIP archives — suitable for custom content or content not exposed via a content channel.

SAP Fiori Launchpad — ABAP Configuration

For organisations running SAP S/4HANA on-premise or SAP NetWeaver ABAP, the Fiori Launchpad on the ABAP stack is the primary UX entry point for ERP users. Its content model, navigation architecture, and role assignment strategy are configured directly in the ABAP system.

Content Model

Spaces & Pages (Modern Model)

The current model for S/4HANA 2022+ replaces the classic Groups and Catalogs approach with Spaces (top-level navigation areas) and Pages (content areas within a space), each containing sections and app tiles. Spaces are assigned to business roles; pages are assigned to spaces.

Fiori Configuration Cockpit (/UI2/FLPD_CONF · /UI2/FLPD_CUST) · S/4HANA business role assignment · transport via TMS

Navigation

Semantic Object & Action Targets

Fiori navigation uses intent-based routing — each app exposes a Semantic Object (e.g. SalesOrder) and Action (e.g. manage) as its navigation target. Applications link to each other via these semantic targets rather than hard-coded URLs, enabling navigation to be resolved dynamically based on the user’s available apps.

Target mapping · Inbound navigation · Cross-app navigation (CrossApplicationNavigation API) · hash-based routing

Authorisation

Business Roles & PFCG Integration

S/4HANA ships business roles (e.g. SAP_BR_SALES_MANAGER) that bundle the correct Fiori catalog access, PFCG authorization objects, and space/page assignments. Custom business roles are created by copying and adapting standard roles. PFCG authorization objects control both Fiori tile visibility and backend data access.

SAP_BR_* standard roles · Role Maintenance (PFCG) · SU24 check indicator · Fiori Apps Reference Library for role mapping

Activation & Transport

SICF Services & Change Management

Every Fiori app requires its SICF service nodes to be activated in the ABAP system (transaction SICF). OData services must also be activated in /IWFND/MAINT_SERVICE or /IWBEP/V4_ADMIN. Fiori content (spaces, pages, tiles) is transported via standard ABAP TMS change requests through your DEV → QA → PROD landscape.

SICF activation · OData service registration · /UI2/SEMOBJ transport · standard ABAP TMS · Fiori App Activation guide

UI Integration Cards

UI Integration Cards are SAP’s standard format for embedding business data snapshots directly on Work Zone pages — without navigating into a full application. Cards call backend APIs via BTP Destinations and can be embedded across Work Zone pages, Microsoft Teams channels, and the Microsoft Outlook add-in.

List Card

My Open Tasks / Recent Orders

Vertical list of items from an OData service. Ideal for task lists, notifications, and recent document overviews with navigation to the full app.

Object Card

Employee Profile / Business Partner

Displays a single business object with header, key attributes, and action buttons. Commonly used for quick-view of a specific record.

Analytical Card

KPI Charts & Trend Indicators

Connects to SAC or OData analytical services to display charts, KPI tiles with trend arrows, and bullet charts. Supports drill-down navigation.

Table Card

Purchase Orders / Open Items

Tabular view of a collection from an OData entity set. Supports column configuration, sorting, and row-level navigation to related apps.

Timeline Card

Document History / Approval Log

Chronological display of events or process steps. Ideal for approval workflows, document lifecycles, and activity streams.

Component Card

Custom SAPUI5 Micro-App

Embeds a full custom SAPUI5 component as a card — maximum flexibility for complex visualisations or interactions not covered by standard card types.

Cards are defined in a manifest.json descriptor file and deployed to the BTP HTML5 Application Repository. Work Zone administrators assign cards to pages using the Page Designer — no developer involvement required for layout changes once the card is deployed.

SAP Task Center & Process Automation

SAP Task Center aggregates workflow tasks from across your SAP landscape — S/4HANA, SuccessFactors, Ariba, Concur, SAP Build Process Automation, and others — into a single inbox surfaced directly in Work Zone. It requires a correctly configured Identity Directory (IdDS) for cross-application user correlation.

SAP Task Center — cross-application task aggregation flow

Task ProvidersSAP S/4HANA (ABAP workflows)SAP SuccessFactorsSAP AribaSAP ConcurSAP Build Process Automation

→

SAP Task Center (BTP)Connector per task providerIdDS user correlationReal-time task push / pullApprove / reject in-place

→

User in Work ZoneUnified task inbox tileFilter by system / priorityComplete tasks without leaving Work ZoneMobile via SAP Start

Prerequisite: SAP Task Center requires users to be present in the SAP Identity Directory (IdDS) with a stable user ID that matches across all task-providing systems. A correctly configured IPS provisioning flow is therefore a prerequisite for Task Center to function — not an optional add-on.

Content Transport

Work Zone content (pages, spaces, UI Integration Cards, card descriptors) follows its own transport lifecycle, separate from ABAP TMS. Two patterns are supported:

Work Zone Content Transport — DEV to PROD promotion

Content AdminWork Zone Admin UI · Page Designer

→

DEV Work ZoneAuthor pages, assign cards, test content

→

Export PackageContent ZIP or CTM node

→

Cloud Transport MgmtApproval gate · audit trail

→

PROD Work ZoneImport content · publish to users

HTML5 applications (SAPUI5 apps, UI Integration Cards) deployed to the BTP HTML5 Application Repository follow the same CI/CD and Cloud Transport Management pipeline used for other BTP content — giving one consistent transport lane for all digital workplace artefacts.

What We Deliver

Work Zone Foundation & Edition Setup

Edition selection (Standard vs Advanced), BTP subaccount subscription and entitlement configuration, IAS trust setup, IdDS group-to-role mapping, custom domain configuration, and UI Theme Designer branding aligned to your corporate design system. DEV/TEST/PROD Work Zone landscape established from day one.

Content Federation & Provider Setup

Content provider registration for S/4HANA Cloud, S/4HANA On-Premise (via Cloud Connector), and NetWeaver ABAP systems. BTP Destination configuration, content channel activation, and role-to-space assignment mapping. Content sync scheduling and validation across all registered backend systems.

Fiori Launchpad (ABAP) Configuration

Spaces and Pages model design and configuration for S/4HANA On-Premise and NetWeaver. Business role creation aligned to SAP standard roles, PFCG authorization object assignment, SICF service activation, and OData service registration. Semantic object and navigation target setup for cross-app navigation.

UI Integration Cards & Custom Apps

Card descriptor authoring (manifest.json) for List, Object, Analytical, Table, Timeline, and Component card types. SAPUI5 Fiori Elements app development (List Report, Object Page, Analytical List Page floor plans). Deployment to BTP HTML5 Application Repository and integration into Work Zone pages via Page Designer.

SAP Task Center Setup

Task Center BTP service subscription, connector configuration per task provider (S/4HANA, SuccessFactors, Ariba, SAP Build Process Automation), IPS provisioning validation for IdDS user correlation, and Work Zone integration (task inbox tile on role-relevant spaces). Mobile task access via SAP Start.

Transport, Governance & Operations

Cloud Transport Management pipeline for Work Zone content packages (DEV→TEST→PROD). Content governance model: who can author pages, publish content, and manage workspaces. Monitoring setup for content sync failures and Task Center connector health. UX analytics for measuring adoption and identifying unused content.

How Customers Benefit

1 Entry Point

For Every SAP Application

Users access S/4HANA, SuccessFactors, Ariba, BTP apps, and custom extensions from one role-based launchpad — no more navigating multiple URLs, portals, or login screens.

Federated

Content Without Duplication

Content providers pull app catalogs and role assignments directly from backend systems via the OData content channel. Work Zone reflects backend changes automatically — no manual tile management after the initial setup.

Zero

Context Switching for Task Completion

SAP Task Center aggregates approval tasks from every connected SAP system into one inbox inside Work Zone. Users approve purchase orders, leave requests, and workflows without switching applications.

Embedded

SAP Data in Teams & Outlook

UI Integration Cards embed live SAP business data — KPIs, task lists, order statuses — directly in Microsoft Teams channels and the Outlook add-in, meeting users where they already work.

Consistent

Fiori UX Across ABAP & Cloud

Spaces and Pages on both the ABAP Fiori Launchpad and Work Zone Standard Edition share the same design language (Horizon theme), giving users a unified experience whether they’re accessing on-premise or cloud apps.

Auditable

Content Transport & Change Control

Cloud Transport Management enforces gated promotion of Work Zone content packages and HTML5 apps from DEV through PROD — every page and card change tracked, approved, and reversible.

How We Work

Persona & Landscape Assessment

We map your user personas, existing Fiori adoption, backend systems in scope, and identity setup. Edition recommendation (Standard vs Advanced), content federation strategy, and Task Center feasibility are agreed before any configuration begins.

Architecture & Content Design

Space and page hierarchy design aligned to business roles, content provider topology, navigation target catalogue, UI Integration Card requirements, and transport pipeline design — all documented and reviewed before implementation.

Foundation Setup

Work Zone subscription and entitlement, IAS trust and IdDS group mapping, custom domain and theme configuration, DEV/TEST/PROD landscape provisioning, and Cloud Transport Management pipeline — before any content work begins.

Content & Integration Delivery

Content provider registration, Fiori Launchpad configuration (Spaces, Pages, roles, SICF), UI Integration Card development and deployment, Task Center connector setup, and custom SAPUI5 / Fiori Elements app delivery — iteratively via sprint.

Governance & Adoption

Content governance model (author, publisher, admin roles), UX analytics activation for adoption tracking, monitoring runbooks for content sync and Task Center health, and end-user onboarding materials per persona — your team owns the platform going forward.

Knowledge Transfer & Handover

Live workshops for Work Zone content administrators and Fiori developers, full architecture documentation, operational runbooks, and a validated checklist for onboarding new backend systems as content providers in future.

Ready to modernize your SAP user experience?

Let’s build your digital workplace.

Tell us about your current Fiori setup, backend systems, and user personas — we’ll design a Work Zone and Fiori architecture that drives adoption across your entire organisation.

Get in touch →