SAP Build Work Zone
BTP & Integrationbeginner

BTP Build Work Zone Part 1: Standard vs Advanced Edition

Key takeaway

SAP Build Work Zone provides central sites for business users: standard edition for launchpad-style access to apps (successor of the SAP Launchpad service), advanced edition for digital workplaces with workspaces, content, cards and collaboration. Learn sites, roles, content (apps, cards) and how users get the right tiles.

Explanation

📌 KEY POINTS
✅ Standard edition: launchpad sites with apps from BTP and back ends (S/4HANA, others).

✅ Advanced edition: adds workspaces, content pages, knowledge and collaboration features.

✅ Content manager organizes apps into roles, groups and catalogs; roles decide what users see.

✅ UI integration cards show key information directly on the home page.

⚠️ Building separate launchpads per department fragments the user experience and duplicates maintenance.

━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS

Part 1: Editions and building blocks

Part 2: Architecture — identity, content federation, operations

━━━━━━━━━━━━━━━━━━━━
▶ 1. EDITIONS

  • Standard vs advanced.

━━━━━━━━━━━━━━━━━━━━
▶ 2. SITES

  • Site settings, themes.

━━━━━━━━━━━━━━━━━━━━
▶ 3. CONTENT

  • Apps, cards, groups, catalogs.

━━━━━━━━━━━━━━━━━━━━
▶ 4. ROLES

  • Role → content visibility.

━━━━━━━━━━━━━━━━━━━━
▶ 5. USERS

  • Role collections via IdP groups.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

  1. Create a site in the site manager.
  2. Add apps to a role and group.
  3. Assign the role to a test user.

✅ CHECKPOINT: user sees only the intended tiles.

Code example

ABAP Code
===== CONTENT MODEL =====Content provider (BTP HTML5 repo, S/4 federated) → Content manager: apps, cards → Groups (visual) + Catalogs → Role → assigned via role collection → Site ===== EDITION CHOICE =====Launchpad for apps only → Standard | Digital workplace with workspaces/collaboration → Advanced

Real project scenario

A company created separate launchpads for sales, finance and HR; users juggled bookmarks. Consolidating into one Work Zone site with role-based content simplified access.

Common mistakes

  • Many sites.
  • Roles for all.
  • No cards.
  • Manual content per site.
  • Wrong edition.

Best practices

  • One central site.
  • Role-based content.
  • Useful cards.
  • Federated content.
  • Edition by need.

Interview angle

Questions: "Standard vs advanced edition?", "How do roles control content?", "What are UI integration cards?"
Strong answer: editions, sites, content, roles, users.

Practice this lesson

Quick check

1. What are UI integration cards used for in Work Zone?

2. What does the SAP Build Work Zone advanced edition add compared with the standard edition?

3. What determines which tiles a user sees in a Work Zone site?

Interview questions

1. What are the most important concepts in SAP Build Work Zone, and how do they connect to Build Work Zone Architecture: Identity, Content Federation, Task Center and Governance in a real SAP landscape?

Answer it in your own words first, then compare.

2. A project team is working on SAP Build Work Zone. Using the SAP Build Work Zone Fundamentals: Standard vs Advanced Edition scenario, how would you approach the requirement from design through validation?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.

More lessons in this topic

Interview questions on this topic

Related SAP topics