Access Management
|
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. |
Data flow
Overview
The sales follow-up is a report which mix data from Global Sales, APO, Dynasys and P&L. The report give a complete view of the forecast and the sales.
The data flow is based on the LSA method. The data visualization is done on the composite provider CPSDSO54 (MP: Order book & Forecast & historical (PO & SO)), previously multiprovider MVSDSO54 .
Global Sales data layers:
- Propagation Layer
- Business Layer
- Reporting Layer
- Virtual Layer
Please see the data flow of the composite provider CPSDSO54(MP: Order book & Forecast & historical (PO & SO)) generated from Performer Suite.
Besides the BW 13 objects mentioned in the dataflow downwards, the composite provider has another 3 calculation views:
- CV_SD_SO_ORDER_LASTR
- CV_SD_SO_CPSDSO54_0001
- CV_SD_SO_CPSDSO54_0002
Propagation layer
The propagation layer used is the propagation of Global sales, Dynasys, APO. The data from P&L are extracted with APDs.
APD:
APD_PL_GS_0030 (Netback Sales P&L), based on the query APD_QRY_MVCOPA01_NBACK_0001 (BW COPA Netback query APD (Core Query))
APD_PL_GS_0031 (Netback Sales P&L (w/o interval)), based on the query APD_QRY_MVCOPA01_NBACK_0002 (BW COPA Netback query APD w/o month (Core Query))
Business layer
The propagation layer used is the propagation of Global sales (historical data, order book), Dynasys and APO.
Reporting layer
List of infoproviders used in the reporting layer:
| CUBE tech. name | CUBE description | source CUBE tech. name | source CUBE description |
|---|---|---|---|
| CRAPO002 | APO - Global (Dynamic) | DBAPO002 | APO - Special Chemicals / Rare Earth (Dynamic) |
| DBAPO004 | APO - Special Chemicals (Dynamic) | ||
| DBAPO006 | APO - Novecare (Dynamic) | ||
| DBAPO008 | APO - Polyamide Downstream (Dynamic) | ||
| DBAPO010 | APO - Polyamide Upstream (Dynamic) | ||
| CRDYN11 | DYN - Reporting | DBDYN13 | DYN - Reporting (SnapShots) |
| DBDYN20 | DYN - Reporting (Dynamic) | ||
| CRSDSO58 | Global Sales: Delivery (PO+SO) (Rhodia) | DBSDSO9O | Global sales: Delivery (PO+SO) (Rhodia) |
| CRSDSO56 | Global Sales: Delivery (PO+SO) (Solvay) | DBSDSO9N | Global sales: Delivery (PO+SO) (Solvay) |
| CRSDSO60 | Global Sales: Invoice aggregated (PO+SO) (Rhodia)) | DBSDSO9Q | Global sales: Invoice (PO+SO) (Rhodia) |
| CRSDSO59 | Global Sales: Invoice aggregated (PO+SO) (Solvay) | DBSDSO9P | Global sales: Invoice (PO+SO) (Solvay) |
| CRSDSO55 | Global Sales: Order line (PO+SO) (Rhodia) | DBSDSO9M | Global sales: Order line (PO+SO) (Rhodia) |
| CRSDSO49 | Global Sales: Order line (PO+SO) (Solvay) | DBSDSO9L | Global sales: Order line (PO+SO) (Solvay) |
| DBSDSO7A | APD: P&L Netback Sales | DPSDSO7A | APD: P&L Netback Sales (prop) ( Direct Update ) |
| DBSDSO9D | SO+PO: ORDER BOOK -OPEN ORDER (Rhodia) | DBSDSO56 | SO: SHIPPED NOT INVOICED (Rhodia) |
| DBSDSO57 | SO: OPEN ORDER WITH DLV DOC (Rhodia) | ||
| DBSDSO58 | SO: OPEN ORDER W/O DLV DOC (Rhodia) | ||
| DBSDSO68 | PO: OPEN Transfers orders (Rhodia) | ||
| DBSDSO97 | SO: OPEN ORDER NOT SCHEDULED (Rhodia) | ||
| DBSDSO9C | SO+PO: ORDER BOOK -OPEN ORDER (Solvay) | DBSDSO16 | SO: SHIPPED NOT INVOICED (Solvay) |
| DBSDSO17 | SO: OPEN ORDER WITH DLV DOC (Solvay) | ||
| DBSDSO18 | SO: OPEN ORDER W/O DLV DOC (Solvay) | ||
| DBSDSO28 | PO: OPEN Transfers orders (Solvay) | ||
| DBSDSO96 | SO: OPEN ORDER NOT SCHEDULED (Solvay) |
Virtual layer
List of infoproviders used in the virtual layer:
MP tech. name | MP description | source CUBE tech. name | source CUBE description |
|---|---|---|---|
CPSDSO54 | MP: Order book & Forecast & historical (PO & SO) | CRAPO002 CRDYN11 CRSDSO58 CRSDSO56 CRSDSO60 CRSDSO59 CRSDSO55 CRSDSO49 DBSDSO7A DBSDSO9D DBSDSO9C CV_SD_SO_ORDER_LASTR CV_SD_SO_CPSDSO54_0001 CV_SD_SO_CPSDSO54_0002 | APO - Global (Dynamic) DYN - Reporting Global Sales: Delivery (PO+SO) (Rhodia) Global Sales: Delivery (PO+SO) (Solvay) Global Sales: Invoice aggregated (PO+SO) (Rhodia) Global Sales: Invoice aggregated (PO+SO) (Solvay) Global Sales: Order line (PO+SO) (Rhodia) Global Sales: Order line (PO+SO) (Solvay) APD: P&L Netback Sales SO+PO: ORDER BOOK -OPEN ORDER (Rhodia) SO+PO: ORDER BOOK -OPEN ORDER (Solvay) View created to provide the last requisition date ICM (Detailed) ICM (Consolidated) |
CV_SD_SO_ORDER_LASTR - View created to provide a different last requisition date dynamically for the report.
ICM information are split between detailed and consolidated and treated by the normalized view to have allocated and unallocated data at same level of invoices.
CV_SD_SO_CPSDSO54_0001:
The P&L data is linked to APD process APD_PL_0006 from query APD_QRY_MVCOPA01_0007 into table DPSDSO75
CV_SD_SO_CPSDSO54_0002:
The consolidate view uses DPSDSO95 as target and a different variable from the same query mentioned above by the APD APD_PL_0007
Reporting
Workbook | Query | ||
|---|---|---|---|
| Sales Follow Up - Current Year Detailed | BW_WBK_MVSDSO54_0001 | Sales Follow Up - Current Year Detailed (core query) | BW_QRY_MVSDSO54_0001 |
| Sales Follow Up - Historical and Forecast | BW_WBK_MVSDSO54_0002 | Sales Follow Up - Historical and Forecast (core query) | BW_QRY_MVSDSO54_0002 |
Important: a selection is done on the billing type and sales document type. The master data C_BILLTYP and C_DOCTYP2 with the attribute "Relevant for sales follow-up" contains the selection.
Data loading
| Main Process Chain | Final Info Provider | Frequency | Start Time | Duration |
|---|---|---|---|---|
| PC_GLOBAL_SALES_MAIN | CRSDSO41, 42... | Daily | ~1:30am CET | ~3.5h |
| PC_SD_MAIN | CRSDSO01, 02... | Daily | ~2:00am CET | ~1h |
| PC_GL_SALES_MAIN_PO | CRSDSO51, 52... | Daily | ~6:00am CET | ~1h |
| PC_OBAS_TRANSFERS_MAIN | CRSDSO11, 12... | Daily | ~6:00am CET | ~0.5h |
| PC_DPS_DYNASYS_15 | CRDYN11 | Hourly | 0am CET | ~0.4h |
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)>