| 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.
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.
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)
WARNING: For the PO part the notion of sales offices doesn't exist. The restriction in sales offices will not be considered for the reports PO and PO+SO. |
Data flow
Overview
The quote report gives the details of quote at the level of sales order/item.
The data flow is based on the LSA method. The data visualization is done on the Composite Provider CPSDAE01(SD: Quote) .
Global Sales data layers:
- Propagation Layer
- Business Layer
- Reporting Layer
- Virtual Layer
Please see the data flow of the Composite Provider CPSDAE01(SD: Quote) generated from Performer Suite.
Propagation layer
| DSO tech. name | DSO description | Data source | source DSO description |
|---|---|---|---|
| AASDAE01R | SD: Conditions | DTS_VBAP_KONV | Conditions |
Business layer
List of DSOs used in the business layer:
| DSO tech. name | DSO description | source DSO tech. name | source DSO description |
|---|---|---|---|
| ABSDAE01R | Aero - Quote | DBSDSO51 | SO Global: Sales Document Item Data (Rhodia) |
| AASDAE01R | SD: Conditions |
Reporting layer
The reporting layer is the same than the business layer.
Virtual layer
List of infoproviders in the virtual layer:
MP tech. name | MP description | source CUBE tech. name | source CUBE description |
|---|---|---|---|
CPSDAE01 | SD: Quote | ABSDAE01R | Aero - Quote |
Reporting
Core queries
The core queries are based on the Composite Provider CPSDAE01:
Workbook | Query | ||
|---|---|---|---|
| Quote report | BW_WBK_CPSDAE01_SD001 | BW - Quote report (Core Query) | BW_QRY_CPSDAE01_0001 |
Data loading
| Main Process Chain | Final Info Provider | Frequency | Start Time | Duration |
|---|---|---|---|---|
| PC_SD_AE_01 | ABSDAE01R | Daily(Not on Sundays or Public Holidays(Calendar ID:14) | ~5:00am CET | ~5min |
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