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 Owner | BILLING-ext, Anoop |
| Stakeholders | Guillaume Decarsin/Ruben Beeck |
| Jira Request ID | |
| Jira Development (Build) ID | |
| Lean IX App Link | To be added when development reaches UAT |
| Business Process Reference (L4) | 11.11.01.02. Create & Distribute Custom Reports |
| Parameter | Value |
|---|---|
| Application System (Delivery Tool) | SuccessFactors – Story Report Module: Compensation (COMP) and Employee Central (EC) |
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.
Eligibility is derived using:
Content ownership: BILLING-ext, Anoop
Input from: Guillaume Decarsin, Ruben Beeck
The solution delivers a custom Story Report enabling users to:
Provide a consolidated and visual overview of employee eligibility for the Merit process, including validation of exceptions and special scenarios.
| Report Field Name | Mandatory / Optional | Prompt Type | Default Value / Restrictions |
|---|---|---|---|
| Grade | Optional | Selection option | None |
| New Hire Status | Optional | Selection option | None |
| Last Date Worked | Optional | Interval | None |
| Employee Class | Optional | Selection option | None |
| Employment Type | Optional | Selection option | None |
| Merit Eligibility Exception | Optional | Selection option | None |
As defined by the page filters above.
(All complex eligibility logic is derived from Compensation eligibility rules, not calculated in the story.)
Standard layout following provided mockup:
Chart 1 – Eligibility Status Distribution
Chart 2 – Eligible Employees by Org Dimensions
Employee‑level Eligibility Table
Key fields / columns include (non‑exhaustive):
The table must include:
Expected rows: All active employees evaluated for Merit eligibility.
| Report Field Name | Mandatory / Optional | Prompt Type | Default Value / Restrictions |
|---|---|---|---|
| Employee Status | Mandatory | Selection option | Active employees only |
| Data Model Technical Name | Data Model Description | Jira Development ID | Link to Data Model FS |
|---|---|---|---|
| To be confirmed | EC + Compensation eligibility dataset | ERP‑2793 | To be added |
The design reuses standard SuccessFactors Story capabilities while extending them with Compensation eligibility logic and EC attributes, ensuring:
| ID | Condition | Expected Result |
|---|---|---|
| 1 | Employee eligible per Compensation rules | Shown as eligible in report |
| 2 | Employee with eligibility exception | Exception clearly visible |
| 3 | Contingent → Permanent conversion | Included correctly |
| 4 | International relocation in scope | Included correctly |
None identified.
This report will follow the following format:

