Please see the SyWay 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 required financial years. Planning form will store following financial data per GBU/Function at L2 and L3 Buckets.
Portfolio Buckets will allow planning of below in separate forms
A tile will be required to access the SAC planning forms and update the FY budget allocation and Future Year Guidance by the Portfolio owners of respective GBUs.
| 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 Future Year Guidance" | 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 Future Year Guidance", user is prompted to enter Bucket ( ID and Description) Fiscal Year ( From and To) | Version defaults to "Future Year Guidance" 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 |
Overview page will include the instructions as per below
This planning form allows update of the financial data for GBU Buckets in project portfolio
GBU Portfolio owners are responsible for updating the financial values for their own GBU. All values entered are in EURs
| FY Bucket Allocation |
|---|
| Future Year Guidance |
|---|
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 = Future Year Guidance, From FY = Default CY +2 , To FY = User to enter |
| Version | Mandatory | Drop down - single Value | FY Budget Allocation or Future Year Guidance |
| Currency | Mandatory | Single Value | Default to EUR |
Header of the story will display the selected data as defined in Page Filters
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.
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 |
N/A
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 "Future Year Guidance" |
| 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 |
This section lists the data models consumed by the story and links to the functional specification describing them.
| 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 Bucket |
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
Content Ownership: Functional Consultant, Input from: Reporting & Analytics Consultant
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.
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
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 |
|---|---|---|
| 1. | Launch the tile "Portfolio bucket Planning" | Overview Page with instructions and link to pages (FY budget allocation and Future Year Guidance) 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 = Future Year Guidance | 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 |
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
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.
