Please see the SAP Analytics Approach document, section 'Documentation' for more information about the context of this document.
| Status | Revision in progress |
|---|---|
| Functional Specification Owner | CONNELLY-ext, Delia |
| Stakeholders | |
| Jira Request ID | [ERP-125] Business Case form to capture Project Financial Indicators - Jira |
| Jira Development (Build) ID | [ERP-263] Business Case form to capture Project Financial Indicators - Jira |
| Lean IX App Link | |
| Business Process Reference (L4) | 10.01.03.01. Manage Initiatives and Items | Signavio |
High-Level Specification
| Parameter | Value |
|---|---|
| Application System (Delivery Tool) | SAC Story |
Functional Overview
The Project Business Case captures key financial information about a project in a simplified and standardized format to enable comparable financial reporting across a Project Portfolio.
The Business Case includes:
- Capturing financial information such as Sales Prices, Sales Volumes
- Calculation of financial measures such as Sales Forecast, Contribution Margin
- Calculation of financial indicators, such as NPV, MIRR and VCI
The financial indicators are further input to the Project Scoring calculation, which supports the Project Prioritization process.
Scope
The Project Business Case must be completed for all financially driven projects.
Process Flow Diagram
Step | Description | Comment |
|---|---|---|
| 1. | Enter Project Cost | |
| 2. | Complete Business Case | |
| 3. | Trigger Project Scoring |
Solution Overview
Input from: Reporting & Analytics Consultant
The Project Business Case incorporates data drawn from the following sources:
- Centrally maintained Master Data
- Project Costs maintained in a separate Planning form
- Data inputs directly in the Business Case
- Calculations
Story Definition
Overview Page
TBD how this will relate, or be tied to input of Project Cost / Forecast
Story Page N
Page Objective
Input of Business Case
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) |
|---|---|---|---|
| Item Id | Mandatory | Single Value Select from Hierarchy or by Item attributes such as Person Responsible | |
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