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

Syensqo needs a report to track Upcoming Employee Terminations to ensure HR teams can proactively prepare offboarding activities, including:

• Benefit roll‑off
• Access removal
• Compliance‑related actions

This is one of the most requested HR reports, widely used to ensure that employees with a scheduled termination have their access revoked and offboarding tasks initiated on time.

Business requirements addressed

• Centralized visibility of upcoming terminations
• Early preparation of offboarding tasks
• Compliance with access removal and benefits processes

Business questions answered

• Which employees have an upcoming termination date?
• When are terminations scheduled?
• Which countries, GBUs, and departments are impacted?
• What are the main reasons for upcoming terminations?

Business value

The report enables timely and compliant offboarding, reduces operational risk, and ensures HR has a single, reliable source of truth to manage upcoming exits.

Scope

In Scope

The report includes:

• All employees once a scheduled termination date is available
• Employee name (first and last)
• Direct manager
• Department and site
• Termination date
• Employment details and demographics
• Event and event reason related to termination

Additional considerations:

• Include contingent workers (clearly distinguished)
• If contingent workers cannot be handled due to process differences, a separate report may be required

Out of Scope

• Employees without a termination date
• Historical terminations already completed (unless still active in EC)

Solution Overview

Content ownership: BILLING-ext, Anoop 
Input from: Elina Krastina

• Security: Strict Role‑Based Permissions (RBP)
• Data visibility restricted to HR users with a legitimate business need

Story Page – Upcoming Terminations

Page Objective

Provide a centralized dashboard and detailed table for HR to monitor all upcoming employee terminations and prepare offboarding actions in advance.

Page Filters

Page Level Input Controls

• Dimension selector for termination analysis by country, GBU, division, or department.

Calculations

The report includes the following metrics:

• Number of users with a termination date
• FTE
• Average age of terminations

Layout

• Page filters pinned at the top
• Syensqo logo top‑left
• Summary KPIs (first tab)
• Charts (first tab)
• Detailed employee‑level table at the bottom of the page

Dashboards / Charts

Summary KPIs (Numerical):

• Number of users with termination date
• FTE
• Average age of terminations

Charts:

• Terminations by Gender – Pie chart
• Terminations by Event Reason – Bar chart
• Terminations by Country / GBU / Division / Department – Bar chart with dimension input control
• Terminations over Time (Termination Date) – Time series

Tables / Lists

Table 1 – Employee‑Level Termination Details

Story Filters (Global)

Data Models

Business Roles

Design Rationale

No existing report in the catalog provides a forward‑looking view of upcoming terminations with the required level of detail and security. A custom EC Story Report is required.

Assumptions

• Termination date is reliably populated in Employee Central
• Event reason correctly identifies termination scenarios

Dependencies

• Final RBP target population definition
• Alignment with access‑removal and benefit offboarding processes

Special Requirements

• Report contains sensitive personal and employment data
• Must strictly comply with RBP and confidentiality rules
• Real‑time or daily refresh required

Frequency of Analysis / Report Run

Testing Considerations / Dependencies

• Validate termination date filtering logic
• Validate RBP access restrictions
• Validate KPI accuracy (counts, age calculation)

Test Conditions and Expected Results

Other Requirements

None identified.

Screenshots

This is how the standard template looks like: 

See also

Change log