Launchpad, spaces and roles
Full lesson currently free to read · AI practice limits apply separately
Business roles and catalogs determine available content, while spaces and pages organize the experience. Intent resolution selects a target for a semantic object and action. Diagnose navigation entitlement separately from the service permissions required after the application opens.
Visual overview
Explanation
Tutorial outcome
Business roles and catalogs determine available content, while spaces and pages organize the experience. Intent resolution selects a target for a semantic object and action. Diagnose navigation entitlement separately from the service permissions required after the application opens.
Prerequisites
Complete chapters 1–7 in this module. Use synthetic fixtures or an authorized sandbox.
Worked case — fictional
A test user sees a page but an order intent cannot resolve to its intended target.
Step-by-step investigation
1. Identity
Compare the affected test user's intended business role with the content assignment.
Expected evidence: User BuyerDemo has the buyer role only.
2. Content
Find the semantic object/action in the relevant catalog and inspect its target mapping.
Expected evidence: PurchaseOrder-display has a valid target.
3. Layout
Confirm the intended space/page exposes the content in the selected landscape.
Expected evidence: The page placement exists independently of service access.
4. Service
Open with the test role and verify the backend business operation separately.
Expected evidence: Intent resolves; unauthorized company code still fails.
Try it yourself
Reproduce the synthetic input from the example below in a local fixture or authorized sandbox. Follow each step, record the observed result, and explain any mismatch before continuing. Do not treat the expected evidence as a result observed in your SAP tenant.
Acceptance check
The intended role resolves the target; backend restrictions remain effective.
Common failure to avoid
Do not cure a target-mapping or service permission problem by assigning unrestricted administration roles.
Self-check
Does placing an app on a page authorize its backend data?
Expected reasoning: No; service and business authorization remain separate.
Edition and release scope
Content tools and role models differ across embedded launchpad, private edition, public edition and SAP Build Work Zone. Follow the applicable product guide rather than assuming one transaction exists everywhere.
SAP references
References checked 2026-10-30. SAP material supports the named concepts; the case, fixture and acceptance checks are original ERPClimb teaching material. No SAP tenant execution or certification is claimed.
[SAP Learning — UI development foundations](https://learning.sap.com/courses/learning-the-basics-of-sap-fiori/explaining-user-interfaces_c2d82120-6a0c-49d2-b872-8b5352c0dfad) — UI technologies, MVC, development responsibilities
Code example
{"semanticObject":"PurchaseOrder","action":"display","testRole":"BuyerDemo"}Launchpad, spaces and roles: evidence walkthrough
Simulated training case. These observations are authored fixtures, not screenshots or results from a customer SAP system.
A test user sees a page but an order intent cannot resolve to its intended target.
Before you start
- Complete chapters 1–7 in this module. Use synthetic fixtures or an authorized sandbox.
Content tools and role models differ across embedded launchpad, private edition, public edition and SAP Build Work Zone. Follow the applicable product guide rather than assuming one transaction exists everywhere.
Identity
Compare the affected test user's intended business role with the content assignment.
Expected evidence · simulated
User BuyerDemo has the buyer role only.
Automatic playback is disabled by your reduced-motion preference. All steps remain available.
Try it, then verify
The intended role resolves the target; backend restrictions remain effective.
Watch for: Do not cure a target-mapping or service permission problem by assigning unrestricted administration roles.
Open the ERPClimb lesson diagram at full sizeSAP references and release scope
References checked 2026-10-30. The linked SAP material supports the named concepts; the scenario, fixtures and acceptance checks are original ERPClimb teaching material. This is not an SAP certification or a tenant-execution claim.
- SAP Learning — UI development foundations
UI technologies, MVC, development responsibilities
Real project scenario
A test user sees a page but an order intent cannot resolve to its intended target.
Common mistakes
Do not cure a target-mapping or service permission problem by assigning unrestricted administration roles.
Best practices
The intended role resolves the target; backend restrictions remain effective. Content tools and role models differ across embedded launchpad, private edition, public edition and SAP Build Work Zone. Follow the applicable product guide rather than assuming one transaction exists everywhere.
Interview angle
Does placing an app on a page authorize its backend data? No; service and business authorization remain separate.
Practice this lesson
Original educational case studies for SAP consultants, not official SAP certification exam questions. Verify product edition and implementation details against the current SAP documentation.
Quick check
0 of 3 questions attempted
1. What controls which apps a user sees in the Fiori launchpad?
2. What is the purpose of spaces and pages in the launchpad?
3. A user sees a tile but gets an authorization error when opening it. What is likely?
Interview questions
1. How does launchpad content relate to authorizations?
Answer it in your own words first, then compare.
2. How would you design launchpad spaces for a finance team?
Answer it in your own words first, then compare.
Check before use: lesson examples are educational, not a guarantee of correctness for your SAP edition or release. Sample code has not been executed on your SAP system. Confirm API availability, syntax, authorizations and business impact in an approved development or test environment.