UX100 – SAP Fiori Foundation — Lesson 1: SAP Fiori Strategy, Design Principles, Personas, User Experience, and App Types

Learning Objectives

• Interpret the SAP structures, data, settings, roles, and dependencies shaping this lesson.
• Perform the workflow and create a reviewable Fiori persona and user-experience map.
• Evaluate the condition where a launchpad page includes applications unrelated to the user persona and choose proportionate follow-up.

Detailed Topics

• SAP Fiori Strategy applied to the course scenario, SAP behavior, and expected evidence.
• Design Principles applied to the course scenario, SAP behavior, and expected evidence.
• Personas applied to the course scenario, SAP behavior, and expected evidence.
• User Experience applied to the course scenario, SAP behavior, and expected evidence.
• and App Types applied to the course scenario, SAP behavior, and expected evidence.

Instructor Demonstration

The instructor traces a scenario involving a transformation team planning role-based SAP Fiori experiences for business users. The walkthrough connects SAP navigation, process logic, settings, system messages, and the evidence captured in Fiori persona and user-experience map. It also tests the condition where a launchpad page includes applications unrelated to the user persona.

Hands-On Exercise

Complete a controlled activity covering SAP Fiori Strategy, Design Principles, Personas, User Experience, and App Types. Preserve the final result in Fiori persona and user-experience map.

1. Confirm the process objective, required roles, source data, and expected system outcome.
2. Perform the SAP workflow while recording documents, settings, messages, and observations.
3. Introduce the stated exception and isolate the first point where expected behavior changes.
4. Document corrective action, ownership, retest evidence, and operational handover.

Scenario Analysis

• Identify the SAP object, rule, setting, or process step with the strongest influence on the outcome.
• Compare two defensible responses and explain their business, technical, control, and evidence trade-offs.
• Decide how the Fiori persona and user-experience map should be approved, retained, retested, and updated.

Troubleshooting Guidance

Begin where expected SAP behavior first differs from the observed result. Check organizational assignments, master data, configuration sequence, authorization, integration, and transaction evidence separately. Treat “a launchpad page includes applications unrelated to the user persona” as a testable hypothesis until relevant settings, logs, documents, and outcomes confirm the cause.

Validation Checklist

• Required SAP structures, master data, roles, settings, and dependencies are present.
• The Fiori persona and user-experience map connects the conclusion to objective, reviewable system evidence.
• Normal processing, the stated exception, integration behavior, and follow-up were tested.
• Corrections, ownership, retest criteria, documentation, and operational handover are complete.

Lesson Outcome

Learners can perform SAP Fiori Strategy, Design Principles, Personas, User Experience, and App Types, explain the SAP behavior, and defend the result through Fiori persona and user-experience map.