|
List of authorization objects mandatory for the application.
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. |
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:
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 |
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 |
| 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 comes from SAP system. To compare data between BW and sources systems, check propagation layers.
<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)>
<Describe the scheduling in place for the application (eg. existing jobs, trigger time/event based, dependencies)>
<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)>
<Describe how to handle errors (eg. error codes, description and respective resolution, alert users)>
<List the existing bugs, its criticality, workarounds and resolution plan.>
<List past & future evolutions for the application (including links to MED/FSD/TSD)>