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-2589 - Getting issue details... STATUS |
| Jira Development (Build) ID | ERP-2797 - 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
Why the report / analytics is needed
The Workflow Request Analysis report is required to provide analytical visibility into workflows processed in SuccessFactors Employee Central.
It enables HR and GBS stakeholders to analyze workflow activity beyond operational follow‑up, focusing on patterns, reasons, and processing durations.
Business requirements addressed
The report addresses the following business requirements:
- Analyze processed workflow requests over a selected time period
- Provide visibility into workflow reasons
- Enable analysis of workflow processing durations, including start and end dates
- Support understanding of workflow execution and completion efficiency
Business questions answered
The report enables stakeholders to answer questions such as:
- How many workflow requests have been processed during a given period?
- What are the most frequent workflow reasons?
- How long do workflows typically take to complete?
- Are there trends or patterns in workflow processing duration?
- Where potential inefficiencies or bottlenecks may exist in workflow execution?
Why it is important to the business
This report is important to support process analysis and continuous improvement of workflow handling in Employee Central.
Without an analytical view of processed workflows, stakeholders lack insight into workflow performance, making it more difficult to identify trends, inefficiencies, or opportunities to optimize workflow design and execution.
Scope
Functional scope
- The report provides analytical insights into processed workflow requests.
- It supports analysis of workflow reasons and processing durations.
- It focuses on completed/processed workflows, not open or pending requests.
- No new business logic or calculations are introduced beyond SAP standard capabilities.
Application scope
- The report is based on the SAP standard Story Report “Workflow Request Analysis”.
- No custom report development is required; the scope is limited to enabling and configuring the standard report.
Data scope
- Data is sourced exclusively from Employee Central workflow data.
- The report includes:
- Processed workflow requests
- Workflow reasons
- Start and end dates
- Duration‑related metrics
- Data is analyzed within a user‑selected time range.
Regional scope
- The report has a global scope, subject to Role‑Based Permissions.
- Users can only access workflow data for populations they are authorized to view.
Usage limitations
- The report is intended for analytical and monitoring purposes.
- It is used on an ad‑hoc / on‑demand basis.
- It is not intended for transactional workflow management or approval actions.
Scope of Solution
This request does not require custom development.
The solution consists of:
- Enabling the SAP standard Workflow Request Analysis Story Report
- Configuring access so HR and GBS stakeholders can analyze workflow activity
Solution Overview
Content Ownership: Anoop Billing
Input from: Elina Krastina
The solution leverages an existing SAP standard report to deliver analytical insights into workflow processing, minimizing development effort while meeting business needs.
Story Definition
Overview Page
- Summary KPIs related to workflow processing
- Charts showing workflow distribution and processing patterns
- Detailed list of processed workflow requests
Story Page 1 – Workflow Request Analysis
Page Objective
Provide an analytical view of processed workflow requests to support monitoring of workflow reasons, durations, and processing patterns.
Page Filters
| Report Field Name | Mandatory / Optional | Prompt Type | Default Value / Restrictions |
|---|---|---|---|
| Time Range | Mandatory | Interval | User‑selected |
| Standard workflow filters | Optional | Selection option | SAP standard filters |
Page Level Input Controls
Standard input controls provided by the SAP standard Workflow Request Analysis story.
Calculations
- Workflow duration based on start and end dates
- Aggregated counts of processed workflow requests
(All calculations are standard and delivered by SAP.)
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 Workflow Request Analysis SAP standard report, supporting:
- Analysis of processed workflows
- Distribution by workflow reason
- Workflow duration analysis
Tables / Lists
Processed Workflow Requests Table
Includes:
- Processed workflow request list
- Workflow reasons
- Start dates
- End dates
- Duration‑related information
Story Filters (Global)
| Report Field Name | Mandatory / Optional | Prompt Type | Default Value / Restrictions |
|---|---|---|---|
| Standard workflow filters | Optional | Selection option | SAP standard |
Data Models
| Data Model Technical Name | Data Model Description | Jira Development ID | Link to Data Model FS |
|---|---|---|---|
| SAP Standard EC Workflow Model | Employee Central processed workflow data | ERP‑2797 | Not applicable |
Business Roles
- 40-GBS People Services Specialist
Design Rationale
A custom report is not required, as SAP provides a standard Workflow Request Analysis report that fulfills the analytical needs.
Using the standard report ensures consistency, scalability, and reduced maintenance effort.
Assumptions
- Workflow data in Employee Central is complete and accurate
- Start and end dates are correctly captured for workflows
- Users have appropriate Role‑Based Permissions
Dependencies
- Correct configuration of SAP standard workflow reporting
- Finalization of user access for HR and GBS stakeholders
Special Requirements
None identified.
Frequency of Analysis / Report Run
- Ad‑hoc / On‑demand
Testing Considerations / Dependencies
How to Test
- Validate that only processed workflows are displayed
- Validate workflow reasons and duration calculations
- Confirm correct behavior of time‑range filters
- Confirm access for authorized users only
Test Conditions and Expected Results
| ID | Condition | Expected Result |
|---|---|---|
| 1 | Processed workflow exists | Displayed in report |
| 2 | Workflow duration available | Correctly calculated |
| 3 | Authorized user | Can access report |
| 4 | Unauthorized user | Access restricted |
Other Requirements
None identified.
