Please see the SAP Analytics Approach document, section 'Documentation' for more information about the context of this document.

 It is to be populated by the story owner and the reporting functional consultant collaboratively.  

It does NOT describe business logic e.g. KPI definitions delivered by the data models (e.g. analytic models) that it consumes. This is covered in the Data Model Functional Specification  

If a requirement is for a flat table, then this will be delivered as a story and this document may simply show the order of the columns.  Where more detailed requirements for a story layout are known, this template will capture these requirements. 

 As story building is an iterative and agile process, it is expected that this document will be updated through the development process.

High-Level Specification

Functional Overview

Why the report is needed

This report is required to monitor the progress of merit forms and identify which routemap step each form is currently in, in order to assess merit allocation, budget spend, and adherence to pay‑for‑performance principles.

Business requirements addressed

• Monitor merit form progress by routemap status
• Support analysis of merit allocation and budget usage
• Enable drill‑down from summary views to individual employee and manager details

Business questions answered

• How many merit forms are in each routemap step?
• Which managers’ forms are pending or completed?
• How is merit allocation progressing across the organization?

Business value

The report enables Total Rewards and SBPs to track compensation cycle progress, ensure governance of merit processes, and support timely decision‑making on budget and reward adjustments.

Scope

In Scope

• Merit forms for the current year
• Routemap status tracking
• Employee‑level and manager‑level visibility
• Compensation‑related indicators linked to merit forms

Out of Scope

• Historical merit cycles outside the current year

Solution Overview

Content ownership: Anoop Billing
Input from: Guillaume Decarsin, Ruben Beeck

• Security: Standard SuccessFactors Role‑Based Permissions (RBP) apply. Visibility depends on user role and authorized scope (Global vs Entity).

Story Page 1 – Merit Forms Status

Page Objective

Provide a consolidated view of merit form status by routemap step, with interactive charts and the ability to drill down to individual employee and manager details.

Page Filters

Page Level Input Controls

• Interactive filtering driven by chart selections (clicking on a chart segment filters all other charts and tables).

Calculations

The report includes the following calculated metrics:

• Total number of forms
• Total number of completed forms
• Total number of employees
• Count of forms by routemap status

Layout

• Filters pinned at the top of the page
• Syensqo logo in the top‑left corner
• Summary KPIs aligned horizontally
• Charts (pie and bar)
• Detailed table

Dashboards / Charts

Summary KPIs (Numerical):

• Total number of forms
• Total number of completed forms
• Total number of employees

Charts:

• Merit Form Status by Routemap Step – Pie Chart
• Number of Forms by Business Unit / Department / Legal Entity / Country – Bar Chart

All charts and KPIs are interactive and linked to the detailed table.

Tables / Lists

Table 1 – Merit Form Details (Employee Level)

Story Filters (Global)

Data Models

Business Roles

Design Rationale

No standard report or catalog solution meets the business requirement to track merit form progress by routemap step with drill‑down capability. A custom SuccessFactors Story Report is required.

Assumptions

• Only active employees are included
• Merit forms relate to the current compensation cycle
• Routemap status is consistently maintained

Dependencies

• Availability and quality of Compensation module data
• Final confirmation of RBP roles and scopes

Special Requirements

• Charts and tables must be fully interactive (click‑to‑filter behavior).
• Drill‑down from chart segments to employee‑level details is required.

Frequency of Analysis / Report Run

Testing Considerations / Dependencies

• Validate routemap status distribution
• Validate drill‑down behavior from charts to table
• Validate compensation values before and after campaign
• Validate role‑based access by user type

Test Conditions and Expected Results

Other Requirements

None identified.

Screenshots

Similar to this:

See also

Change log