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 | UPADHYAY-ext, Anjali |
| Stakeholders | |
| Jira Request ID | |
| Jira Development (Build) ID | |
| Lean IX App Link | To be added when development reaches UAT |
| Business Process Reference (L4) | 10.01.02.01. Develop Portfolio Plans and Budgets |
| Parameter | Value |
|---|---|
| Application System (Delivery Tool) | SAC Story |
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.
Portfolio Buckets will allow planning of below in separate forms
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.
| 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. |
Input from: Reporting & Analytics Consultant
N/A -
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 |
N/A
This section will contain a wire-frame of the page indicating the widgets on it. The wire-frame can be a draw-io diagram or a screenshot of e.g. an excel mock-up.
If there are multiple data models in the story, indicate which data models the widget takes data from at page or widget level.
Widget level details such as filters, dimensions, hierarchy usage, history, comparatives, targets, thresholds, top N etc can also be included. N.B. This level of detail is not mandatory and often changes through the iterative development process. For tables, indicate the number of expected rows.
If multiple datasources consumed by story:
Widget | Data Model | Field | 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) | none |
| Financial Year | Mandatory | Internal Selection (From - To) | none |
| Currency | Mandatory | Single Value | Default to EUR |
This section lists the data models consumed by the story and links to the functional specification describing them.
| Data Model Technical Name | Data Dodel Description | Jira Development ID | Link to Data Model Functional Specification |
|---|---|---|---|
| (Filled when available) | Text for data model | ||
Business users/Positions who have been assigned Portfolio Owner role will be able to access the planning forms.
Content Ownership: Functional Consultant, Input from: Reporting & Analytics Consultant
Describe any assumptions that have been made in the process of completing this design. What functionality is expected of configuration or other developments that pass information to this development and/ or retrieve the information processed by it (performance, triggers, exceptions, etc)
Indicate any dependencies or constraints that may impact development, in terms of requirements from internal or external applications or teams, limited access to legacy system, time constraints or data restrictions. Also, please specify schedule dependencies e.g. interface or batch jobs that must run prior to execution.
Specify any special requirements or considerations that may impact the development based on specific locations, regulatory compliance or system limitations. Clearly outline requirements e.g. localization rules for countries like China
If the development interacts with third-party systems such as Icertis, describe any additional integration, security or authentication considerations that must be taken into account.
Provide information regarding report run frequency like ad-hoc, monthly analysis, weekly, yearly analysis etc.
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.
Please provide some guidance and/or test data to help the developer unit test the report. Please include both positive and negative testing (to validate error situations handling)
List any considerations essential for application test planning (e.g., test this before ABC along with DEF separate from GHI).
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.
| ID | Condition | Expected Results |
|---|---|---|
List any considerations essential for application test planning (e.g., test this before ABC along with DEF separate from GHI). If the development encompasses a user interface, explain how to test it. List any insights as to how this component could be tested the most efficiently.
Description of requirements not covered by topics above
Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.
