Page tree


Access Management

Roles & Access

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

Authorization Objects

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

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. nameCUBE description

source CUBE tech. name

source CUBE description
CRAPO002APO - Global (Dynamic)DBAPO002APO - Special Chemicals / Rare Earth (Dynamic)
DBAPO004APO - Special Chemicals (Dynamic)
DBAPO006APO - Novecare (Dynamic)
DBAPO008APO - Polyamide Downstream (Dynamic)
DBAPO010APO - Polyamide Upstream (Dynamic)
CRDYN11DYN - ReportingDBDYN13DYN - Reporting (SnapShots)
DBDYN20DYN - Reporting (Dynamic)
CRSDSO58Global Sales: Delivery (PO+SO) (Rhodia)DBSDSO9OGlobal sales: Delivery (PO+SO) (Rhodia)
CRSDSO56Global Sales: Delivery (PO+SO) (Solvay)DBSDSO9NGlobal sales: Delivery (PO+SO) (Solvay)
CRSDSO60Global Sales: Invoice aggregated (PO+SO) (Rhodia))DBSDSO9QGlobal sales: Invoice (PO+SO) (Rhodia)
CRSDSO59Global Sales: Invoice aggregated (PO+SO) (Solvay)DBSDSO9PGlobal sales: Invoice (PO+SO) (Solvay)
CRSDSO55Global Sales: Order line (PO+SO) (Rhodia)DBSDSO9MGlobal sales: Order line (PO+SO) (Rhodia)
CRSDSO49Global Sales: Order line (PO+SO) (Solvay)DBSDSO9LGlobal sales: Order line (PO+SO) (Solvay)
DBSDSO7AAPD: P&L Netback SalesDPSDSO7AAPD: P&L Netback Sales (prop) ( Direct Update )
DBSDSO9DSO+PO: ORDER BOOK -OPEN ORDER (Rhodia)DBSDSO56SO: SHIPPED NOT INVOICED (Rhodia)
DBSDSO57SO: OPEN ORDER WITH DLV DOC (Rhodia)
DBSDSO58SO: OPEN ORDER W/O DLV DOC (Rhodia)
DBSDSO68PO: OPEN Transfers orders (Rhodia)
DBSDSO97SO: OPEN ORDER NOT SCHEDULED (Rhodia)
DBSDSO9CSO+PO: ORDER BOOK -OPEN ORDER (Solvay)DBSDSO16SO: SHIPPED NOT INVOICED (Solvay)
DBSDSO17SO: OPEN ORDER WITH DLV DOC (Solvay)
DBSDSO18SO: OPEN ORDER W/O DLV DOC (Solvay)
DBSDSO28PO: OPEN Transfers orders (Solvay)
DBSDSO96SO: 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 DetailedBW_WBK_MVSDSO54_0001Sales Follow Up - Current Year Detailed (core query)BW_QRY_MVSDSO54_0001
Sales Follow Up - Historical and ForecastBW_WBK_MVSDSO54_0002Sales 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 ChainFinal Info ProviderFrequencyStart TimeDuration
PC_GLOBAL_SALES_MAINCRSDSO41, 42...Daily~1:30am CET~3.5h
PC_SD_MAINCRSDSO01, 02...Daily~2:00am CET~1h
PC_GL_SALES_MAIN_POCRSDSO51, 52...Daily~6:00am CET~1h
PC_OBAS_TRANSFERS_MAINCRSDSO11, 12...Daily~6:00am CET~0.5h
PC_DPS_DYNASYS_15CRDYN11Hourly0am 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)>