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 required financial years. Planning form will store following financial data per GBU/Function at L2 and L3 Buckets.
- FY Budget Allocation which is the Top down Budget allocations for following financial year split into Capex and Opex
- Run Rate which is Future year allocation advice for multiple years 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 future years (from and to) as per the selection screen
A tile will be required to access the SAC planning forms 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 Tile "Portfolio Bucket Planning" | The tile is available in the SAP launchpad |
| 2. | Overview Page is Launched with links to the planning pages "Enter FY Bucket Allocation" "Enter Run Rate" | Links to the pages appear with instructions on the overview page |
| 3. | If the User selects "Enter FY Bucket allocation" user is prompted to enter Bucket ( ID and Description) | Version defaults to "FY Budget Allocation" Fiscal Year is default to CY +1 Currency default to EUR Hierarchical search for Bucket is available |
| 4. | If the User selects "Enter Run Rate", user is prompted to enter Bucket ( ID and Description) Fiscal Year ( From and To) | Version defaults to "Run Rate" Currency default to EUR Hierarchical search for Bucket is available |
| 5. | Financial Values for relevant bucket is updated and data is saved | If L2 Bucket is selected automatically subordinate bucket will open and will be available for data entry. If L3 Bucket is selected , only L3 bucket is available for entry Portfolio owners restricted to their GBUs can only update the data for their L2 /L3 buckets and not L2/L3 bucket of different GBU |
| 6. | Financial Values entered at L3 Buckets should sum up with the value at L2 Bucket | Based on Page filter. Values entered at L2 bucket should be equal to the sum of values entered in subordinate bucket |
Solution Overview
Story Definition
Overview Page
Overview page will include the instructions as per below
This planning form allows update of the financial data for GBU Buckets in project portfolio
- Use "FY Budget Allocation" page to update the Top down Budget allocations for following financial year for your GBU and distribute to respective functions
- Use "Run Rate" page to update Future year allocation advice for required future years for your GBU and distribute to respective functions
GBU Portfolio owners are responsible for updating the financial values for their own GBU. All values entered are in EURs
| FY Bucket Allocation |
|---|
| Run Rate |
|---|
Story filter
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) | If L1 Bucket is selected all subordinate buckets open If L2 Bucket is selected automatically subordinate bucket will open and will be available for data entry. If L3 Bucket is selected , only L3 bucket is available for entry Portfolio owners restricted to their GBUs can only update the data for their L2 /L3 buckets and not L2/L3 bucket of different GBU |
| Financial Year | Mandatory | From - To | If the Version = FY budget Allocation, From and To FY = Default CY+1 If the Version = Run Rate, From FY = Default CY +2 , To FY = User to enter |
| Version | Mandatory | Drop down - single Value | FY Budget Allocation or Run Rate |
| Currency | Mandatory | Single Value | Default to EUR |
Page 1
This page covers the planning input form for the FY Bucket Allocation.
Header of the story will display the selected data as defined in Page Filters
Page level input controls
Calculations
N/A
Layout
Widget | Data Model | Field | Filter |
|---|---|---|---|
| Widget-001 | PPM_Bucket | /RPM/BUCKET_D-EXTERNAL_ID | If L1 Bucket is selected all subordinate buckets open If L2 Bucket is selected automatically subordinate bucket will open and will be available for data entry. If L3 Bucket is selected , only L3 bucket is available for entry Portfolio owners restricted to their GBUs can only update the data for their L2 /L3 buckets and not L2/L3 bucket of different GBU |
| Widget-001 | PPM_Bucket | CGPL_TEXT-TEXT1 | |
| Widget-001 | PPM_Bucket | /RPM/FIN_B_PLAN-PLAN TYPE | Default to FY Budget Allocation |
| Widget-001 | PPM_Bucket | /RPM/FIN_B_CAT-CATEGORY | Capex, Opex |
| Widget-001 | PPM_Bucket | Financial Year | Current year + 1 |
Page 2.
This page covers the planning input form for the Run Rate
Page level input controls
Calculations
N/A
Layout
Widget | Data Model | Field | Filter |
|---|---|---|---|
| Widget-001 | PPM_Bucket | /RPM/BUCKET_D-EXTERNAL_ID | If L1 Bucket is selected all subordinate buckets open If L2 Bucket is selected automatically subordinate bucket will open and will be available for data entry. If L3 Bucket is selected , only L3 bucket is available for entry Portfolio owners restricted to their GBUs can only update the data for their L2 /L3 buckets and not L2/L3 bucket of different GBU |
| Widget-001 | PPM_Bucket | CGPL_TEXT-TEXT1 | |
| Widget-001 | PPM_Bucket | /RPM/FIN_B_PLAN-PLAN TYPE | Default to "Run Rate" |
| Widget-001 | PPM_Bucket | /RPM/FIN_B_CAT-CATEGORY | Capex, Opex |
| Widget-001 | PPM_Bucket | Financial Year | Based on Page filter. Values entered at L2 bucket should be equal to the sum of values entered in subordinate bucket |
Data models
| Data Model Technical Name | Data Model Description | Jira Development ID | Link to Data Model Functional Specification |
|---|---|---|---|
| (Filled when available) | PPM_Bucket | ERP-672 | ERP-672 Data Model - PPM |
Business Roles
Business users/Positions who have been assigned Portfolio Owner role will be able to access the planning forms. This is aligned with S/4 security restrictions
Design Rationale
Input from: Reporting & Analytics Consultant
Assumptions
- Single SAC Planning instance will be available for all S/4 instances ( ROW, CUI and China)
- Portfolio Bucket Hierarchy Master data will be available in SAC Planning tool to allow planning
- Financial Year determination such as what is current FY will be automatically determined in SAC based on Financial Calendar
Dependencies
- Portfolio Bucket Hierarchy Master data will be available in SAC Planning tool
- Financial Category/Group/Views are configured in S/4 and used in SAC Planning tool
Special Requirements
Frequency of Analysis/Report Run
Typically both Planning forms (Page 1 and 2) will be run on yearly basis. But there may be a change to update the financial data during the year as well. Note - changes are tracked via snapshots
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 |
|---|---|---|
| 1. | Launch the tile "Portfolio bucket Planning" | Overview Page with instructions and link to pages (FY budget allocation and Run rate) will appear |
| 2. | User clicks on the Page = FY budget allocation | User is prompted to enter the Bucket |
| 3. | User enters the Bucket using hierarchy search | Planning form with defined layout is updated |
| 4. | User Enters the value at L2 and L3 buckets and save the form | Financial Value gets saved, Sum of values of L3 bucket should be equal to or less than Parent L2 bucket |
| 5. | User clicks on the Page = Run rate | User is prompted to enter the Bucket and FY (From and To) |
| 6. | User enters the Bucket and FY From and TO | Planning form with defined layout is updated |
| 7. | User Enters the value at L2 and L3 buckets and save the form | Financial Value gets saved, Sum of values of L3 bucket should be equal to or less than Parent L2 bucket |
Testing Considerations / Dependencies
- Ensure the Portfolio Bucket master data is available in SAC
If L1 Bucket is selected all subordinate buckets open, If L2 Bucket is selected automatically subordinate bucket will open and will be available for data entry. If L3 Bucket is selected , only L3 bucket is available for entry
Portfolio owners restricted to their GBUs can only update the data for their L2 /L3 buckets and not L2/L3 bucket of different GBU
- Data entered in L3 bucket must equal to the value in L2 Bucket
Other Requirements