General presentation
Objective of the application
This application extract the forecasts from tool DynaSys prepared in dedicated DynaSys tables :
- table EXP_FORE_DR for dynamic forecasts to provide reporting Demand Review (DR) / Sales Follow-up
- table EXP_FORE for monthly snapshots to provide reporting Forecast Accuracy
.Tool Leader + IT leader of the application: Celia Gonzales
Usage information
History
Roles & Access
Roles and access
| Role Id | Role Title | Explanation |
|---|---|---|
| ZR_RCS_CA_M52 | DP - Demand Planning | Role Menu Dynasys Currently (Nov 2016), only 2 queries published in this role
|
| ZBI_RCS_DP_A02 | Demand Planning - Dynasys | Role utilisateur Dynasys Authorization object ZBI_DPS
|
| ZBI_RCS_DP_A03 | Demand Planning - Dynasys Keyuser | Authorization object ZBI_DPS_K
|
See also file maintained by Authorization team : BW Catalog of Roles / link: https://drive.google.com/open?id=10GEfKYqrT1eeTO_uHYAheL1GX7L5y_pvH0KQU64qh5I
Authorization objects
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
GBU (CPFCTR1_2) | ZR_*_CA_P05 |
Dataflow overview
Functional and Technical rules on Workbench + Reporting
Rules & Explanations
IECRA determination (implemented since 13/11/2017)
RCS notion, IECRA is only determined for RCS records.
- Retrieve the division (0DIVISION) from material (C_MATNR2)
Get IECRA (0G_CWWE01) from masterdata C_CDSA which is distribution channel (0DISTR_CHAN) compounds with division (0DIVISION).
Determination done at Business Level (EndRoutine)
BU (C_DYN_010) / GBU (CPFCTR1_2) determination
Both BU and GBU are determined at Business Level (EndRoutine) by reading mastersdata C_DYN_005 / Material with System Extension.
The link Material / BU is given by DynaSys interface part : DSO DBDYN02.
The link BU/GBU is given by C_SUBACT2 / Sub-Activity 2
BU = ERP Group of activities (C_PFCTR2)
GBU = BFC Global Business Unit (CPFCTR1_2)
Rule for RCS records was changed the 13/11/2017 (item #58). BU/GBU is now determined reading IECRA (0G_CWWE01)
Sold-to (C_SOLDID) determination
The Sold-to is determined at Business Level (EndRoutine) by reading mastersdata C_DYN_014 / Ship-to with System Extension.
The link Ship-to / Sold-to is given by DynaSys (table EXP_DP_SHIPTO) and stored daily in masterdata C_DYN_014.
Commercial Product (C_PROD) determination
The commercial product is needed to be able to use attributs of masterdata C_GBR14 / GBR: Customer end-use Mat Grp (Ship-to)
The commercial product is determined by reading masterdata C_MATNR2 / Material
Sales Office (C_SAL_OFF) / Sales Document Type (C_DOCTYP2) / Company Code (C_COMPCDE) determination
Sales Office, Sales Document Type, Company code can not be determined for DynaSys, they are set by constant DYN because axis are needed in reporting Sales Follow-up.
Caution Sales Office is autorization relevant for Sales Reporting (Obas, Global Sales), it has been added in Application role, auhorization object ZBI_SD
Company Code also, it will be added ( item #39)
Dependencies with other applications
Data loadings
Info providers and objects loaded
| Process Chain | Code | Type | Frequency | Comments |
|---|---|---|---|---|
| DPS Dynasys: META - M - 6.Reporting DynaSys (Snapshots) | PC_DPS_DYNASYS_09 | MAIN |
| Based on Table EXP_FORE (daily update, by 1.45am even if BW loading is monthly) The SnapShot month (End of Month View/C_FCSTMTH) is automatically set to previous month. Global filter variable (C_GLBFILT) DPS/PHOTO_MTH can be used to fix another SnapShot month. Caution : do not launch this chain several times a month without cleaning previous loadings Info : started at 3am changed to 6am on DynaSys Team request (07/07/2017). EXP_FORE was not ready at 3am due to longer treatments on DynaSys side |
| DPS Dynasys: META - D - 6.Reporting DynaSys (Dynamic KPIs) | PC_DPS_DYNASYS_15 | MAIN |
| Based on Table EXP_FORE_DR (daily update, by 2.45am) 05/01/2017: On DynaSys side, the treatment which prepares table EXP_FORE_DR takes more time, and now finishes around 2.45 (previously 1.45) => BW chain starter changed 2.30 am => 3.00 am 23/01/2017: The chain is planned hourly (with Calendar 14), but the loading will apply only for following time intervals (Decision Block)
run of 3 am has been cancelled (21st of February 2017) because the DynaSys table was frequently empty when BW was collecting the data Without issue a message is send to following users :
Message detail
NB : message has been settled in WBP. Waiting for group email adress to manage it from WBD NEXT EVOLUTION => loading will run only if table has been updated on DynaSys side (By march 2017)
|
| DPS Dynasys: META - M - 6.Reporting DynaSys (MasterData) | PC_DPS_DYNASYS_23 | MAIN |
| Not YET PLANNED A remaining issue :
Issue solved :
|
| DPS Dynasys: META - D - 6.Reporting DynaSys (Obas data) | PC_DPS_DYNASYS_20 | MAIN |
| Temporarly schedulling! this chain has to be added in Obas chain or launched via an Obas event |
Loading frequency
Average performance
| Key Figure | Estimation |
|---|---|
| ~ Average Process Chain Runtime | |
| ~ Average nb of rows loaded per load | |
| ~ Total nb of rows loaded (if full) | |
| ~ Average Runtime for 10k lines |
Record Keeping
Reporting
Queries End User Documentation
Main queries
| Query | Description | Type | Role Menu | Comments |
|---|---|---|---|---|
| BW_QRY_MVDYN11_0005 | BW - DP - Forecast Accuracy (Core query) | QRY | DP - Demand Planning |
|
BW_QRY_MVDYN11_0006 | BW - DP - Demand Review (Core query) | QRY | DP - Demand Planning |
|
| QVSBS_BW_QRY_MVDYN11_0001 | BW - DP - Demand Review for SBS Dashboard (QV) | QRY | This query is used to provide Qlik View Forecast informations from APO / DynaSys and Logility. QV application : CRM Analytics |
Main functionalities
Broadcast
Maintenance
Known bugs
Recurring procedure
Planned Evolution