Please see the SAP Analytics Approach document, section 'Documentation' for more information about the context of this document.
| Status | Approved |
|---|---|
| Functional Specification Owner | UPADHYAY-ext, Anjali |
| Stakeholders | |
| Jira Request ID | ERP-57 - Getting issue details... STATUS |
| Jira Development (Build) ID | ERP-124 - Getting issue details... STATUS |
| Lean IX App Link | |
| Business Process Reference (L4) | 10.01.02.01. Develop Portfolio Plans and Budgets |
High-Level Specification
| Parameter | Value |
|---|---|
| Application System (Delivery Tool) | SAC Story |
Functional Overview
SAC Planning forms are required to capture planning and budgeting data at Portfolio Bucket. This will enable the portfolio Buckets to store the financial data which is used to plan and monitor the Project portfolio and prioritize projects for a given financial year. Planning form will store below per GBU/Function at L2 and L3 Buckets.
- Top down Budget allocations for following financial year split into Capex and Opex
- Future year allocation advice for multiple years in future split into Capex and Opex
Scope
Portfolio Buckets will allow planning of below in separate forms
- "FY Budget allocation" for CY + 1 against L2 and L3 Buckets representing GBU and function respectively
- "Run Rate" which is the future year allocation advice for multiple years in future as per the selection screen
A Fiori tile will be required to access the planning form and update the FY budget allocation and Run rate by the Portfolio owners of respective GBUs.
Process Flow Diagram
| 1. | Portfolio Owner will launch the Fiori tile "Enter FY Budget Allocation | The Fiori tile is available in the SAP launchpad |
| 2. | SAC Planning form/story selection screen will open with selection parameters such as Bucket hierarchy (ID and description) FY (From) - FY (To) | The selection screen will open |
| 3. | Portfolio Owner will enter the selection parameters | Planning Page for FY Budget allocation will be launched as per selected parameter |
| 4. | Portfolio Owner will update the FY Budget allocation in EUR at Level 2 and Level 3 buckets as per selected bucket node. and save | If L2 is selected then L3 Bucket should appear in the planning form. so the FY budget allocation can be distributed down to L3 Bucket. Its is noted that the sum of the L3 bucket allocation must be equal to the Parent L2 Bucket. Data gets saved |
| 5. | Portfolio Owner will Launch the Fiori tile " Enter Run Rate for future years" | The Fiori tile is available in the SAP launchpad |
| 6. | Repeat steps 2, 3, 4. |
Solution Overview
Input from: Reporting & Analytics Consultant
Story Definition
Overview Page
N/A -
Story 1
This story covers the planning input form/screen for the FY Bucket Allocation
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) |
|---|---|---|---|
| Portfolio Bucket | Mandatory | Hierarchy ( ID and Description) | none |
| Financial Year | Mandatory | Single Value | Default to current FY |
| Currency | Mandatory | Single Value | Default to EUR |
Page level input controls
Calculations
N/A
Layout
draw.io
Diagram attachment access error: cannot display diagram
draw.io
If multiple datasources consumed by story:
Widget | Data Model | Field | Filter |
|---|---|---|---|
Story 2.
This story covers the planning input form/screen for the Run Rate
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) |
|---|---|---|---|
| Portfolio Bucket | Mandatory | Hierarchy ( ID and Description) | none |
| Financial Year | Mandatory | Internal Selection (From - To) | none |
| Currency | Mandatory | Single Value | Default to EUR |
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
Business users/Positions who have been assigned Portfolio Owner role will be able to access the planning forms.
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