| Table of Content Zone | ||||
|---|---|---|---|---|
|
Access Management
1.0 Access Management| Panel | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| List of application role + menu role and explanation if we have several applications role with specials rules.|||||||||||||||||||||
ZR_RCS_CA_M09 PS - Project Costs Role menu for all project costs queries ZBI_RCS_PS_A02 Project Costs and Structures Analysis - End User role Application Role:
ZBI_RCS_CO_A21 CBS Project costs Reporting Analysis - End User role Application Role:
|
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
List of authorization objects mandatory for the application.
0COMP_CODE;C_COMPCDE;C_PMORDER__0COMP_CODE | Company, role: ZR_*_CA_P01 | 0PROFIT_CTR__CPFCTR1_2; 0PROFIT_CTR__C_PFCTR1;CPFCTR1_2;C_AGRITM__CPFCTR1_2; | C_ASSET2__C_PFCTR1;C_ASSET__C_PFCTR1;C_MATPLNT__CPFCTR1_2; C_MATPLNT__C_PFCTR1;C_MATPNT2__CPFCTR1_2;C_PFCTR1; C_PMORDER__C_PFCTR1;C_PMORDR__C_PFCTR1;C_PRDEQUI__CPFCTR1_2; C_RECONTR__CPFCTR1_2;C_RESP_CC__CPFCTR1_2;C_SUBACT2__CPFCTR1_2 C_TECMAT__CPFCTR1_2;C_WBS_EL2__CPFCTR1_2;C_WBS_EL2__C_ZSECT;C_WBS_ELE__CPFCTR1_2; C_WBS_ELE__C_ZSECT;C_ZSECT GBU, role: ZR_*_CA_P05 | C_FAMIL;C_WBS_EL2__C_FAMIL;C_WBS_ELE__C_FAMIL | Family, role: ZR_*_CA_P04 | |
2.0 DataFlow
2.1 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.
Reporting documentation drive folder:
https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE
Exemple of dataflow overview :
Template Application name DataFlow
2.2 Technical Rules on Workbench
Explanation for the process on the technical side. Can be specific cases or general rules depending on the scope.
2.2 Dependencies with other applications
We should have the information where the application is sending or receiving information (e.g. APD open hub)
|
Data flow
Overview
The objective of the application is to upload forecast data (BFR and Budget) using an excel file. Data are later combined into Global Sales.
The data flow is based on the LSA method. The data visualization is done on the multiproviders MVSDSO61 (SO: Financial Forecast) .
How to use the program:
How to upload Forecast
- Access the program via transaction code ZBW_SD_PC
Inform GBU / Year / Version and select the forecast file on your PC, which has to be excel and with correct format (template below).
- Click on Preview in order to check the authorization of content and data correction. It may take some time.
- Click on Check File to get the summary of the data correction.
- If data is incorrect, it will tell how many error and what line is incorrect on the file. Correct the file and try step 2 again.
- If data is OK, the Load File button will be available
- Click on Load File, it will save the data into BW system and run process chain PC_GL_SALES_PROP_99 in order to load from file to PSA and DSO DPSDFC01
How to download Forecast from BW system
In case, user wants to see the last forecast in order to make the next forecast. User can download the file that already loaded into BW to his PC in order to revise and upload again.
Guidelines to upload the BDG / MTP (Update Feb 2021)
However, in order to download the file, user must be the owner of the file (perform upload the file).
- Access the program via transaction code ZBW_SD_PC
- Click on History in order to see the list of the file that loaded into BW (it will display only last 10 files)
- After click on History, there are 2 input fields available:
- Source Filename is to enter name of the system file that user want to download. It can be seen at the first column. It is case sensitive.
- Target Filename is the path and file name that user want to save into the PC. For example, C:\Users\th30085\Downloads\Test .xls .
- The folder to download, user must have authorization to save file as well (eg. C:\ or C\WINDOWS do not allow normal user to save the file)
- Filename must end with .xls If save to .xlsx, the file may not be opened.
- Click on Download
- In order to upload again, it is recommend to:
- Save as to format excel 2010 (.xlsx)
- Change the format of the Calmonth to YYYYMM
- Close excel before loading
Note: The user who upload the file can download the file only. It is checked by user ID. Therefore, other users will not allow to download other user file to see the content.
File Template for Upload.
Core Rules
- Authorization of file content will be checked base on GBU and Company code, which get from roles of user on BW system.
- The data will be replaced with the same keys (combination of all fields). If the same key are in the same file, it will be replaced by the last record.
If a user is loading data and it is not completed yet, another user will not allow to click on 'Load Data'. The user need to wait until the process chain loading complete.
Reporting
Core queries
The core queries are based on the multiproviders MVSDSO61:
Workbook | Query | ||
|---|---|---|---|
| Financial Forecast | BW_WBK_MVSDSO61_0001 | Financial Forecast | BW_QRY_MVSDSO61_0001 |
Data loadings
| Main Process Chain | Final Info Provider | Frequency | Start Time | Duration |
|---|---|---|---|---|
| PC_GLOBAL_SALES_FORECAST | CRSDFC01 | Daily | ~3:00am CET | ~3 minutes |
| PC_GL_SALES_PROP_99 | AASDFC01 | triggered by ZBW_SD_PC |
Data Quality Controls
Data comes from SAP system. To compare data between BW and sources systems, check propagation layers.
Operational Documentation
Procedures
<Describe the recurring procedures needed to operate the application (eg. start/pause/terminate/restart the app processes, data preparation, data ingestion, ETL, data visualization, data export, other manual activities)>
Scheduling
<Describe the scheduling in place for the application (eg. existing jobs, trigger time/event based, dependencies)>
Monitoring
<Describe the monitoring checks to confirm the application is performing well (eg. check the overall status, check performance metrics like runtime/data volume/memory/disk/CPU, maintain and react to alerts/notifications)>
Error Handling
<Describe how to handle errors (eg. error codes, description and respective resolution, alert users)>
Known Bugs
<List the existing bugs, its criticality, workarounds and resolution plan.>
Roadmap
<List past & future evolutions for the application (including links to MED/FSD/TSD)>
3.0 Data Loading
3.1 Info Providers and objects loaded
Detail of process chain, list + link between or special event done for the loading

