...
| Status |
| ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Functional Specification Owner | |||||||||||||
| Stakeholders | Elina Krastina | ||||||||||||
| Jira Request ID |
| ||||||||||||
| Jira Development (Build) ID |
| ||||||||||||
| Lean IX App Link | |||||||||||||
| Business Process Reference (L4) | 11.11.01.02. Create & Distribute Custom Reports |
High-Level Specification
| Parameter | Value |
|---|---|
| Application System (Delivery Tool) | SuccessFactors – Story Report Module: Employee Central (EC) |
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:
...
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
...
- 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
| Report Field Name | Mandatory / Optional | Prompt Type |
|---|---|---|
| Termination Date | Optional | Date |
| Country | Optional | Multi‑select |
| GBU | Optional | Multi‑select |
| Division | Optional | Multi‑select |
| Department | Optional | Multi‑select |
| Cost Center | Optional | Multi‑select |
| Employment Type (Regular / Temporary) | Optional | Multi‑select |
| Employment Status | Optional | Multi‑select |
| Event Reason | Optional | Multi‑select |
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):
...
- 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
| Field |
|---|
| User ID |
| Employee First and Last Name |
| Legal Entity |
| GBU |
| Country |
| Division |
| Cost Center |
| Department |
| Regular / Temporary |
| Employment Status |
| Termination Date |
| Hire Date |
| Event |
| Event Reason |
| FTE |
| Location |
| Person ID |
| Username |
| Formal Name |
| Gender |
| Date of Birth |
| Email Address |
| National ID Type |
| National ID |
| Marital Status |
| IBAN |
| Home Address (Lines 1–3) |
| City |
| Zip Code |
| Original Start Date |
| Contract Type |
| Contract End Date |
| Job Function |
| Job Classification |
| Position |
| Supervisor Name |
| Supervisor Email Address |
| Workforce Category |
| Local Pay Grade |
| Pay Grade |
| Amount |
| Currency Code |
| Frequency |
Story Filters (Global)
| Report Field Name | Mandatory | Default |
|---|---|---|
| Termination Date | Mandatory | Not blank |
| Employee Status | Mandatory | Active users only |
Data Models
| Data Model | Description | Jira Development ID |
|---|---|---|
| EC Employee & Termination Data Model | Employee Central termination and employment data | Not specified |
Business Roles
| Role |
|---|
40-GBS People Services Specialist |
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
| Frequency |
|---|
| Daily |
Testing Considerations / Dependencies
- Validate termination date filtering logic
- Validate RBP access restrictions
- Validate KPI accuracy (counts, age calculation)
Test Conditions and Expected Results
| ID | Condition | Expected Result |
|---|---|---|
| TC01 | Open report as HR user | Upcoming terminations displayed |
| TC02 | Filter by termination date | Charts and table update correctly |
| TC03 | Filter by event reason | Correct termination subset shown |
| TC04 | Access by non‑HR user | No access / data restricted |
Other Requirements
None identified.
Screenshots
This is how the standard template looks like:
See also
| Embedded Google Drive File | ||||||
|---|---|---|---|---|---|---|
|
| Attachments | ||||||
|---|---|---|---|---|---|---|
|
Change log
| Change History | ||
|---|---|---|
|