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.

Status

Functional Specification OwnerBILLING-ext, Anoop 
StakeholdersGuillaume Decarsin/Ruben Beeck
Jira Request ID

Jira Development (Build) ID

Lean IX App LinkTo be added when development reaches UAT 
Business Process Reference (L4)11.11.01.02. Create & Distribute Custom Reports

High-Level Specification

ParameterValue
Application System (Delivery Tool)

SuccessFactors – Story Report

Module: Compensation (COMP) and Employee Central (EC)

Functional Overview

This report is required to identify employees eligible for the Merit process by consolidating Employee Central (EC) and Compensation data.

It addresses the need to:

The report ensures eligibility determination is consistent, auditable, and transparent, reducing manual validation across multiple data sources.

Scope

Functional Scope

Data Scope

Eligibility is derived using:

Special Populations in Scope

 


Solution Overview

Content ownership: BILLING-ext, Anoop 
Input from: Guillaume Decarsin, Ruben Beeck

The solution delivers a custom Story Report enabling users to:

Story Definition

Overview Page

Story Page 1 – Merit Eligibility Overview

Page Objective

Provide a consolidated and visual overview of employee eligibility for the Merit process, including validation of exceptions and special scenarios.

Page Filters

Report Field NameMandatory / OptionalPrompt TypeDefault Value / Restrictions
GradeOptionalSelection optionNone
New Hire StatusOptionalSelection optionNone
Last Date WorkedOptionalIntervalNone
Employee ClassOptionalSelection optionNone
Employment TypeOptionalSelection optionNone
Merit Eligibility ExceptionOptionalSelection optionNone

Page Level Input Controls

As defined by the page filters above.

Calculations

(All complex eligibility logic is derived from Compensation eligibility rules, not calculated in the story.)

Layout

Standard layout following provided mockup:

Dashboards / Charts

Chart 1 – Eligibility Status Distribution

Chart 2 – Eligible Employees by Org Dimensions

Tables / Lists

Employee‑level Eligibility Table

Key fields / columns include (non‑exhaustive):

The table must include:

Expected rows: All active employees evaluated for Merit eligibility.

Story Filters (Global)

Report Field NameMandatory / OptionalPrompt TypeDefault Value / Restrictions
Employee StatusMandatorySelection optionActive employees only

Data Models

Data Model Technical NameData Model DescriptionJira Development IDLink to Data Model FS
To be confirmedEC + Compensation eligibility datasetERP‑2793To be added

Business Roles

Design Rationale

The design reuses standard SuccessFactors Story capabilities while extending them with Compensation eligibility logic and EC attributes, ensuring:

Assumptions

Dependencies

Special Requirements

Frequency of Analysis / Report Run

Testing Considerations / Dependencies

How to Test

Test Conditions & Expected Results

IDConditionExpected Result
1Employee eligible per Compensation rulesShown as eligible in report
2Employee with eligibility exceptionException clearly visible
3Contingent → Permanent conversionIncluded correctly
4International relocation in scopeIncluded correctly

Other Requirements

None identified.

Screenshots

This report will follow the following format:

See also

Change log