Access Management
Role Code | Role Description | Explanation |
|---|---|---|
ZBI_RCS_SD_A01 | Application role for Global Sales project / SD data / Orderbook | Role for the application |
ZR_RCS_CA_M49 | SD - Sales and Distribution | Role menu for the application |
List of authorization objects mandatory for the application.
Authorization object | Explanation |
|---|---|
CPFCTR1_2 | GBU |
C_COMPCDE | Legal company |
C_SAL_OF | Sales office |
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
This application shows the time taken to confirm an order in SAP by comparing the order line creation date and the confirmation date. The target is to be less than 2 business days.
The data flow is based on the LSA method. The data visualization is done on the composite provider CPSDCH01(SO - Order confirmations changes) .
Core Rules
The rule is implemented in the routine of TRCS IB_SD_CH_02 → ADSO ABSDCH02( ZCL_SDCH_BUSN=>ME_ABSDCH02 ) and DPSDCH05, DPSDSO16, DPSDCH15, DPSDSO56 → IB_SD_CH_02
Reporting
Core queries
The core queries are based on the composite provider CPSDCH01:
Workbook | Query | ||
|---|---|---|---|
| Order Promising | BW_WBK_CPSDCH01_0001 | Changes Sales Orders - Order promising (core query) | BW_QRY_CPSDCH01_0001 |
Data loadings
| Main Process Chain | Final Info Provider | Frequency | Start Time | Duration |
|---|---|---|---|---|
| PC_SD_CHANGE_DOC | ABSDCH02 | Daily | ~9:00am CET | ~1h |
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)>