Please see the SAP Analytics Approach document, section 'Documentation' for more information about the context of this document.
| Status | Approved |
|---|---|
| Functional Specification Owner | BILLING-ext, Anoop |
| Stakeholders | Elina Krastina |
| Jira Request ID | ERP-2587 - Getting issue details... STATUS |
| Jira Development (Build) ID | ERP-2795 - Getting issue details... STATUS |
| 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
- Report Type: SAP standard Story Report
- Module: Employee Central (EC)
- Category: Workflows
- Population: Workflow requests with status “Pending”
- Usage: Operational follow‑up, ad‑hoc / on‑demand
- Geographical Scope: Global
- Primary Users: GBS teams and users responsible for workflow validation and approvals
Why the report / analytics is needed
The Open Workflow Requests report is required to support day‑to‑day operational workflow management in SuccessFactors Employee Central.
It provides GBS teams with visibility into workflow requests that are still pending, enabling effective monitoring and follow‑up of approvals.
Business requirements addressed
The report addresses the following business requirements:
- Provide a consolidated view of all open (pending) workflow requests
- Enable GBS teams to track and follow up on workflows awaiting approval
- Support efficient workflow validation management
- Improve transparency and control over workflow backlogs
Business questions answered
The report enables users to answer questions such as:
- Which workflow requests are currently pending?
- Which workflows are awaiting approval and require action?
- Where are approval bottlenecks occurring?
- What workflows require prioritization by GBS teams?
Why it is important to the business
This report is critical to ensure timely and efficient workflow processing in Employee Central.
Without a consolidated view of open workflows, approvals would need to be monitored manually via individual inboxes, increasing the risk of delays, missed approvals, and operational inefficiencies.
Scope
Scope
The scope of this report is limited to providing operational visibility into workflow requests with status “Pending” within SAP SuccessFactors Employee Central (EC).
Functional scope
- The report supports monitoring and follow‑up of open workflow requests.
- It enables users to identify workflows awaiting approval and manage approval backlogs.
- The report does not support historical analysis or closed/completed workflows.
- No new business logic or calculations are introduced beyond what is available in the SAP standard story.
Application scope
- The report is based on the SAP standard Story Report “Open Workflow Requests” delivered by SuccessFactors.
- No custom report development is included; the scope is limited to enabling, configuring, and using the standard report.
Data scope
- Data is sourced exclusively from Employee Central workflow data.
- Only workflow requests with status = Pending are included.
- Workflow metadata available in the SAP standard report is displayed as‑is.
Regional scope
- The report has a global scope, subject to Role‑Based Permissions.
- Users can only view workflow data for populations they are authorized to access.
Usage limitations
- The report is intended for ad‑hoc, operational use.
- It is not scheduled and is not intended for analytical trend reporting or KPI tracking over time.
- Access is restricted to GBS teams and users responsible for workflow validation and approvals.
Solution Overview
Content Ownership: Anoop Billing
Input from: Elina Krastina
The solution leverages an existing SAP SuccessFactors standard Story Report to provide operational visibility into workflow requests with status Pending, minimizing custom development while meeting business needs.
Story Definition
Overview Page
- Summary KPIs related to workflow processing
- Charts providing visibility into workflow status
- Detailed list of open workflow requests
Story Page 1 – Open Workflow Requests
Page Objective
Provide a consolidated operational view of all workflow requests with status Pending, enabling effective follow‑up and prioritization by GBS teams.
Page Filters
| Report Field Name | Mandatory / Optional | Prompt Type | Default Value / Restrictions |
|---|---|---|---|
| Workflow Status | Mandatory | Selection option | Pending |
| Other workflow filters | Optional | Selection option | Standard SAP filters |
Page Level Input Controls
Standard workflow input controls provided by the SAP standard story.
Calculations
- Counts of workflow requests by status
(All calculations are standard and provided by the SAP standard story.)
Layout
Standard SAP Story layout including:
- Page filters pinned at the top
- Syensqo logo in the top‑left corner
- Summary KPIs
- Charts
- Detailed workflow table
Dashboards / Charts
Standard charts provided by the SAP standard Open Workflow Requests story, supporting analysis of workflow processing and pending approvals.
Tables / Lists
Workflow Requests Table
Includes:
- Workflow request list
- Approval status (Pending)
- Workflow metadata provided by the SAP standard story
Story Filters (Global)
| Report Field Name | Mandatory / Optional | Prompt Type | Default Value / Restrictions |
|---|---|---|---|
| Workflow Status | Mandatory | Selection option | Pending |
Data Models
| Data Model Technical Name | Data Model Description | Jira Development ID | Link to Data Model FS |
|---|---|---|---|
| SAP Standard EC Workflow Model | Employee Central workflow data | ERP‑2795 | Not applicable |
Business Roles
- 40-GBS People Services Specialist
Design Rationale
A custom report is not required as SAP provides a standard Story Report that meets the business need.
The selected approach minimizes development effort while ensuring operational efficiency and transparency in workflow management.
Assumptions
- Workflow data is correctly maintained in Employee Central
- Users have appropriate Role‑Based Permissions to access workflow information
Dependencies
- Correct configuration of SAP standard workflow reporting
- Finalization of access rights for GBS teams
Special Requirements
None identified.
Frequency of Analysis / Report Run
- Ad‑hoc / On‑demand
Testing Considerations / Dependencies
How to Test
- Verify that only workflows with status Pending are displayed
- Validate visibility of workflow details and metadata
- Confirm access for GBS teams and approvers
Test Conditions and Expected Results
| ID | Condition | Expected Result |
|---|---|---|
| 1 | Workflow status = Pending | Displayed in report |
| 2 | Workflow status ≠ Pending | Not displayed |
| 3 | Authorized GBS user | Can access report |
| 4 | Unauthorized user | Access restricted |
Other Requirements
None identified.
