Page tree


You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

1.0 Overview




Business Context and Application Overview

Provide an overview of the app (e.g Domain, key processes, purpose of the app, etc)

Application User Profile

Describe the key User profiles that exist for the application. 

General role/Viewer role:

Approver role:

Target Users:

As examples: Controllers / Accountants

VERSION

DATE

MODIFIED BY 

DESCRIPTION

0.01

dd.mm.yyyy

Azadeh Nasiri

Initial draft









Application Type


Data Product Type 
  • Dashboard
  • Report
  • Advanced analytics
  • AI 
  • Others <specify which one>
Technologies
  • BW
  • Tableau
  • Qliksense
  • Talend
  • Dataiku
  • Others <specify which one>

Data Sources 

Note: list of all applications and various environment

  • SAP PF1 (Production environment)
  • SAP WP1
  • SAP PI1
  • BW (versions)
  • iCare CRM 
  • CORE CRM
  • Others <specify the name of the source> 

2.0 Business Process


Capture the business process that the application supports . This can be describe through a process diagram or a business capability model


3.0 Application Feature Overview


Historical data in the global sales folder of  BW include more than 40 workbooks that provide overview on sales orders and purchased orders at detailed as well as aggregated level. The reports cover historical data over the last 3 years generated in SAP.

There are both aggregated and detailed categories of reports that draw from a single source of data from BW, providing similar insights but at different levels of granularity.

The detailed reports provide the finest level of granularity, offering in-depth information on sales orders, order lines, and even schedule lines. Conversely, the aggregated reports take a different approach by summarizing data based on regions or other factors, without going into transactional-level details.

Both type of reports are based on the same prompt BW. It's important to clarify that the month in the report corresponds to the month of the document's creation date, which is indicated in the title of the reports. For example, when a user opens a report on 'Sales Order Invoiced' and specifies 'OCT' in the prompt, the report includes sales orders for which the invoice documents have been created in October.

It is imp

ReportsDefinitionPromptsBW Workbook QueryQuery Technical Name
Aggregated reports 



Detailed reports 








4.0 Functional Specification


4.1 General Data/Calculations 

This section will approach the concepts/definitions that will be used in all the reports and required to understand the data from the reports.

Could be specific fields, closing activities, additional information to work and understand the reports.


4.2 Process Detail 

4.2.1.  Report/Process Definition 

Domain<insert name>
Application>insert name>
Provider<insert name>
Existing Documentation

<insert link>


This section represents the process with detail information for the application. Can include specific or special cases, complex logics , calculations, flows, among others.



5.0 Non-functional Descriptions 


5.1 Usability

5.2 Regulatory Compliance

5.3 Security

5.4 Performance

5.5 Reliability

5.6 Scalability

5.7 Compatibility

5.8 Availability

5.9 Refresh of the Data