HR884 – SAP SuccessFactors People Analytics Story Reporting — Lesson 2: Pages, Widgets, Filters, and Calculated Measures

Learning Objectives

• Explain how Pages, Widgets, Filters, and Calculated Measures supports trusted interactive people analytics.
• Complete the workflow and produce a reviewable interactive story design evidence pack.
• Evaluate the condition where a calculated headcount measure changes when an unrelated filter is selected and select a supported response.

Detailed Topics

• story pages: business purpose, responsible roles, and SAP objects that establish the operating scope.
• charts and tables: configuration choices, master-data dependencies, and determination logic shaping the result.
• input controls: transaction flow, status behavior, integration effects, and reviewable operational evidence.
• calculated measures: control points, exception paths, testing needs, and release criteria protecting the outcome.

Instructor Demonstration

Using the scenario, the instructor demonstrates story pages, charts and tables, input controls, calculated measures and highlights object relationships, determination behavior, integration effects, and approval evidence. The demonstration deliberately introduces the exception where a calculated headcount measure changes when an unrelated filter is selected.

Hands-On Exercise

Complete a controlled activity covering story pages, charts and tables, input controls, calculated measures and preserve the result in interactive story design evidence pack.

1. Review prerequisites, dependencies, authorizations, and acceptance criteria before starting the activity.
2. Complete the configured or transactional scenario and preserve the resulting document and status trail.
3. Compare the normal result with the controlled exception and identify the strongest root-cause evidence.
4. Document the selected response, retest result, residual risk, and future review trigger.

Scenario Analysis

• Which SAP object, rule, record, or process step most strongly influences Pages, Widgets, Filters, and Calculated Measures?
• What evidence separates configuration, data, authorization, integration, and timing causes in this scenario?
• How should the interactive story design evidence pack be approved, retained, monitored, and updated after handover?

Troubleshooting Guidance

Start at the earliest point where expected behavior differs from the observed result. Review process sequence, relevant data, configuration, authorization, integration, and timing as separate hypotheses. Treat “a calculated headcount measure changes when an unrelated filter is selected” as unconfirmed until settings, documents, logs, reports, and focused retesting support the cause.

Validation Checklist

• Required roles, structures, data, settings, and dependencies for Pages, Widgets, Filters, and Calculated Measures are present.
• The interactive story design evidence pack links each conclusion to objective and reviewable SAP evidence.
• Normal processing, the stated exception, integration behavior, and access boundaries were tested.
• Corrections, retest criteria, ownership, monitoring, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply Pages, Widgets, Filters, and Calculated Measures, explain the resulting SAP behavior, and defend the outcome through interactive story design evidence pack.