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 | Elina Krastina |
| 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: Employee Central (EC) |
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.
The report addresses the following business requirements:
The report enables users to answer questions such as:
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.
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
Application scope
Data scope
Regional scope
Usage limitations
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.
Provide a consolidated operational view of all workflow requests with status Pending, enabling effective follow‑up and prioritization by GBS teams.
| 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 |
Standard workflow input controls provided by the SAP standard story.
Standard SAP Story layout including:
Standard charts provided by the SAP standard Open Workflow Requests story, supporting analysis of workflow processing and pending approvals.
Workflow Requests Table
Includes:
| Report Field Name | Mandatory / Optional | Prompt Type | Default Value / Restrictions |
|---|---|---|---|
| Workflow Status | Mandatory | Selection option | Pending |
| 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 |
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.
None identified.
| 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 |
None identified.
