General presentation

Objective of the application

In Fixed costs analysis add budget information.

The objective is to upload budget from excel files.

History

Rtr team is the requester of this project (june 2018).

Roles & Access

Roles and access

List of application role + menu role  and explanation if we have several applications role with specials rules.

Role CodeRole DescriptionExplanation
ZR_RCS_CA_M531Fixed costs budget managementTo have the transaction to upload budgets






Authorization objects

List of autorisation objects mandatory for the application.

Authorization objectExplanation






Dataflow overview

Use the google presentation below as a template. This google presentation must be saved in the Reporting GDrive folder under the corresponding application. Then post the link to the document here.

Dataflow :


Datasource on a flat file →  DSO  → Infocube


Functional and Technical rules on Workbench + Reporting

Rules & Explanations

A Datasource on a flat file.

Mockup of source file : 

https://drive.google.com/file/d/17FQBOrU6IobBHEX7in5Emvg-WfGECvFBnBsMzzPW28k/view


DSO DBBUDG01 :

Be careful : in the key, they are BFC Global Business Unit and BFC Group of activities : in the mockup, only one line with one GBU but more BFC Group of activities.


Transformation between datasource DTS_CO_BUDGET_FIXED_COSTS  and DSO DBBUDG01 :

It's an expert routine :  - read table company for fiscvarnt

                                     - add one line in DSO for each activity group not initial   (to put a budget to 0 add  activity group with value 0)

Transformation between  DSO DBBUDG01 and Infocube CUB_FB001 :

Only direct mapping except : 0CALMONTH (Time characteristic conversion)

                                               0CALQUARTER (Time characteristic conversion)

                                               C_INFOPRO (constant  name of DSO : DBBUDG01)


Multiprovider :
The Infocube CUB_FB001 is added on on the multiprovider MPR_FC003 (Fixed costs Analysis (Multi Systems))
Query:
BW_QRY_MPR_FC003_0008 is modified : add Calculated and Restricted key-figures.

Dependencies with other applications

Dependencies with other application (BW, QV, Externals tools like PVelocity or Dynasis etc...

Data loadings

Info providers and objects loaded

The loading run the process chaîn PC_FIXED_COST_BUDGET. This process chain is a direct scheduling with event "PC_FIXED_COST_BUDGET".


Loading frequency

 Loading on demand with transaction : ZBW_BUDGET_LOAD (program ZBW_LOAD_FLAT_FILE_BUDGET).

The user must create or modify a file data and chosse this file in the transaction.

Average performance

if possible, give some information on average process chain duration, amount of data loaded and total data volume example: daily process chain loaded in 30 min, weekly chain loaded in 1h15, with around 2k to 10k lines in DELTA mode for a total of 10M lines in cube. The purpose is to give a general overview of the volume of data managed y the application


Key FigureEstimation
~ Average Process Chain Runtime
~ Average nb of rows loaded per load
~ Total nb of rows loaded (if full)
~ Average Runtime for 10k lines

Record Keeping

Give details if any historisation is done, example: keep only data greater than beginning of Y-3

Reporting

Queries End User Documentation

Query end user documentation should be created in the public "Customer Support Wiki" space under the corresponding BW application page : BW - Application. Technical query query documentation, if necessary should be added as a sub-page of this documentation using the BW Technical Query Documentation template.


Main queries

List the most important and complex queries only with a link to the documentation

Main functionalities

Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts

Broadcast

Indicate if there are broadcasts and give some details on the broadcast settings.

Maintenance

Known bugs

Give the list and explanation on the known, not-solved, bugs.

Recurring procedure

List recurring procedures

Planned Evolution

Detail planned major evolution if already known. Example: complete decommissioning of application is planned in 2017 / Extension to solvay perimeter planned in 2nd semester of 2016