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 | Guillaume Decarsin, Ruben Beeck |
| Jira Request ID | ERP-2568 - Getting issue details... STATUS |
| Jira Development (Build) ID | ERP-2794 - 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: Compensation (COMP) |
Functional Overview
Scope
Process Flow Diagram
Step | Description | Comment |
|---|---|---|
Solution Overview
Input from: Reporting & Analytics Consultant
Story Definition
Overview Page
Story Page N
Page Objective
Page filters
Report Field Name | Mandatory/Optional | Prompt Type (Single Value, Multiple Single Values, Interval, Selection Option, Hierarchy) | Default Value(s) or Restrictions (please provide default value) |
|---|---|---|---|
Page level input controls
Calculations
Layout
draw.io
Diagram attachment access error: cannot display diagram
draw.io
If multiple datasources consumed by story:
Widget | Data Model | Field | Filter |
|---|---|---|---|
Story Page N+1 (etc.)
Story Filters
Report Field Name | Mandatory/Optional | Prompt Type (Single Value, Multiple Single Values, Interval, Selection Option, Hierarchy) | Default Value(s) or Restrictions (please provide default value) |
|---|---|---|---|
Data models
| Data Model Technical Name | Data Dodel Description | Jira Development ID | Link to Data Model Functional Specification |
|---|---|---|---|
| (Filled when available) | Text for data model | ||
Business Roles
Design Rationale
Input from: Reporting & Analytics Consultant
Assumptions
Dependencies
Special Requirements
Frequency of Analysis/Report Run
Testing Considerations / Dependencies
N.B. Unless this is a planning story, the testing should cover layout and user experience NOT data values for metrics created in the data model. Data model values will be tested in conjunction with the data model specification.
How to test
The developer will need to test repeatedly, so where appropriate provide instructions to reverse the actions performed so the test may be run again, or explain how to create new input data to the test. In particular, the developer will need logons for test users representing the various roles within the approval process.
Test Conditions and Expected Results
| ID | Condition | Expected Results |
|---|---|---|
Testing Considerations / Dependencies
Other Requirements