General presentation
Objective of the application
This application extract the forecasts from tool DynaSys prepared in dedicated DynaSys tables :
- view EXP_FORE_DR_BW for dynamic forecasts to provide reporting Demand Review (DR) / Sales Follow-up
- view EXP_FORE_BW for monthly snapshots to provide reporting Forecast Accuracy
.Tool Leader + IT leader of the application: Vendula Siamska / Diogo Paiva based in Lisbon
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
DynaSys source view used
| DynaSys View | MasterData/Transactionnal | Content | Comments | |
| EXP_DP_SHIPTO_BW | MD | |||
| EXP_DFU_DR_BW | MD | |||
| EXP_SHIPTO_DC_SR_MANUAL_BW | MD | |||
| EXP_MATSHIPTO_BW | MD | |||
| EXP_SF_CRM_BW | MD | |||
| EXP_DC_BU_BW | MD | Not used in Reporting but Interface part | ||
| EXP_FORE_BW | Transac | data for Forecast Accuracy (including Gross History) | All GBU except CM | |
| EXP_FORE_DR_BW | Transac | data for Demand Review | All GBU except CM | |
| SYS_TIMESTAMP | System | |||
| EXP_SAP_PROG_BW | MD | Program/Market Assignement | CM (Aero) | |
| EXP_MAIN_SPEC_BW | MD | Main Spec Assignment | CM (Aero) | |
| EXP_AERO_SKY_BW | MD | Skyline by Program/Month | CM (Aero) | |
| EXP_SHIPTO_INFO_BW | MD | Ship-to info (RCS+BAAN) | CM (Aero) | |
| EXP_MATERIAL_BAAN_BW | MD | BAAN Material info | CM (Aero) Temporary | |
| EXP_AERO_BW | Transac | data for Forecast Accuracy (including Gross History) | CM (Aero) | |
| EXP_AERO_DR_BW | Transac | data for Demand Review (including Gross History) | CM (Aero) |
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)
End of Month View (C_FCSTMTH)
For daily dynamic flow, it corresponds to current month/year
For snapshot flow, it corresponds to previous month of the snapshot
date of the SnapShot | End of Month View (C_FCSTMTH) |
|---|---|
| 6th of May 2018 | 04.2018 |
| 6th of May 2018 | 11.2018 |
In case of a manual reload the value can be changed by using Global Filter
Concerned Period (C_FCGMTH)
For daily dynamic flow, it is set with 'M' (mean view of the month 0CALMONTH
For snapshot flow, it is calculated :
1) If period (0CALMONTH) = end of month view (C_FCSTMTH) => Concerned Period (C_FCGMTH) is set to 'M' means value of the month
2) If period (0CALMONTH) < end of month view (C_FCSTMTH) => Concerned Period (C_FCGMTH) is set to 'N/A' means Not Applicable, SnapShot done after period
3) If period (0CALMONTH) > end of month view (C_FCSTMTH) =>
a) compute NB Month = (period (0CALMONTH) - end of month view (C_FCSTMTH) ) - 1
b) if NB Month between -999 and -1 => concatenate 'M' with NB Month into Concerned Period (C_FCGMTH)
else Concerned Period (C_FCGMTH) is set to 'N/A'
Caution : Concern period M-1 does not exists.
Concern period M for Forecast is considered as M-1 in BW queries.
Examples:
| date of the SnapShot | End of Month View (C_FCSTMTH) | Calendar Year/Month (0CALMONTH) | Concerned Period (Flag) (C_FLGMTH) |
|---|---|---|---|
| 6th of August 2017 | 07.2017 | 07.2017 | M |
| 6th of August 2017 | 07.2017 | 08.2017 | M-2 |
| 6th of August 2017 | 07.2017 | 02.2019 | M-20 |
| 6th of August 2017 | 07.2017 | 08.2016 | N/A |
Dependencies with other applications
Data loadings
Process Chains
| 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 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) 21/02/2017: Run of 3 am has been cancelled because the DynaSys table was frequently empty when BW was collecting the data 31/10/2017: Still 4 runs a day, but whole loading will be done ONLY is DynaSys table EXP_FORE_DR has been updated (timestamps in table SYS_TIMESTAMP) 08/01/2018: 4 runs a day. Run of 10am has been changed to 7am Decision block explanation : Block 1 1) Check if Decision Block has to be bypassed Variable can be activated If chain has to be forced to run 2) Else get loading times Block 2 1) Check if Decision Block has to be bypassed Variable can be activated If chain has to be forced to run 2) Else get loading times. And check timestamps loaded from DynaSys (table SYS_TIMESTAMP / info for EXP_FORE_DR) If timestamps between 2 loadings, the chain has to carry on Message send at chain's end see procedure for details |
| 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_0006 | BW - DP - Demand Review (Core query) | QRY | DP - Demand Planning | This query will be replaced by Budget Review when BR will be simplified |
| BW_QRY_MVDYN11_0001 | BW - DP - Budget Review (Core query) | QRY | DP - Demand Planning | |
| BW_QRY_MVDYN11_0005 | BW - DP - Forecast Accuracy (Core query) | QRY | DP - Demand Planning |
|
| BW_QRY_MVDYN11_0007 | BW - DP - Segmentation Report (Core Query) | QRY | DP - Demand Planning | Asked by EP (Emmanuel Hatt) |
| 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 | |
| QV_BW_QRY_MVDYN11_0005 | BW - DP - Forecast Accuracy (QV query) | QRY | This query is used to provide Qlik View FA QV application 1 : Novecare Suply Chain dashboard QV application 2 : Global Supply Chain | |
Obsolete query. It has been replace by :
| ||||
| BW_WBK_DPS_0001 | BW - DP - Budget Review AROMA (Workbook) | WRK | Workbook is based on query BW - DP - Budget Review (Core query) /BW_QRY_MVDYN11_0001 | |
| BW_WBK_DPS_0002 | BW - DP - Budget Review SA&D (Workbook) | WRK | Workbook is based on query BW - DP - Budget Review (Core query) /BW_QRY_MVDYN11_0001 | |
| BW_QRY_CPDYN11_0006 | BW - DP - Demand Review for CM (Core query) | QRY | DP - Demand Planning | project Solstice Aero in progress, not yet available |
| BW_QRY_CPDYN11_0005 | BW - DP - Budget Review for CM (Core query) | QRY | DP - Demand Planning | project Solstice Aero in progress, not yet available |
Main functionalities
Broadcast
Maintenance
Known bugs
Wrong amounts in Local Currency Yen (Currency JPY) - Issue closed
For low currency like JPY, SAP has its own internal format to store amounts.
Transformation has been adapted.
See routine
Caution this internal format has to be applied ONLY to keyfigures type Currency (CURR)
For keyfigures type Float (FLTP) routine has been removed as amounts in JPY where divided by 100. Check keyfigure definition.
Example to check
Material 32787 / Ship-to 88719 / Distrib Channel 7K / Source System RCS / GBU Aroma PA
Material 135918 / Ship-to 2066945 / Distrib Channel 7F / Source System RCS / GBU Aroma PA
Recurring procedure
Reload a monthly snapshot from flat file
A reload has been done in April 2017 for End of March snapshot for SILICA.
Caution, the flow is always changing. The current mapping might not be up-to date and need to be adapted.
A snapshot reload by flat file has to be validated in WBQ first
Below example of file used.
Particularities :
- decimal point has to be used
- GH quantity has to be up-to date, as it will then be considered as the more accurate one.
Upload manually DPDYN01 / DYN - Reporting (SnapShots)
Then follow upper steps as in the process chain "DPS Dynasys: META - M - 6.Reporting DynaSys (Snapshots)" / PC_DPS_DYNASYS_09
Reload a monthly snapshot from DynaSys table EXP_FORE
Snapshot to reload has to be previously removed from all level :
- CRDYN11 / DYN - Reporting
- DBDYN13 / DYN - Reporting (SnapShots)
- DPDYN01 / DYN - Reporting (SnapShots)
- PSA for DataSource DTS_EXP_FORE
If reload is done the same month than the deleted snapshot, just run chain PC_DPS_DYNASYS_09
If much later, change Global Filter to set the wanted month and activate the line, and run chain PC_DPS_DYNASYS_09
Caution variable has to be unactivate afterwards, otherwise following snapshot will be fix to that month!
For info, the variable is used to fix "End of Month View" (C_FCSTMTH)
Increase/decrease DR upload from DynaSys
Change values in Global Filter (C_GLBFILT)
Put Active = 'N' to unactive an existing loading.
Add a new line for an extra loading. Please keep the same logic, all loading times are recorded chronologically to make reading easier.
Do not forget to record your modifications in paragraph "Process Chains" in PC_DPS_DYNASYS_15 comments
Add or remove email adress in distribution list for DR data availability (All GBU except CM (aero))
NB: Distribution list exists on all systems, but user list is only maintained in production system WBP
Transaction SO23
Name DL_DP_001
Add or remove email adresses.
List of user email :
- nicholas.barrett@solvay.com => SD
- carlos.lau@solvay.com => SD
- alessandro.caleffi@solvay.com => added 25/01/2018
- alessandro.marconcini@solvay.com => added 25/01/2018
- geert.schodts@solvay.com => added 25/01/2018
- marie.pereira@solvay.com => added 28/05/2018 => Silica
- anne.delrue@solvay.com=> added 21/06/2018 => TS
stacey.walker-robertson-contractor@solvay.com => added 21/06/2018
adele.fleming@solvay.com=> added 21/06/2018 => TS
john.hodges@solvay.com => added 21/06/2018
- teresa.hipsley@solvay.com => added 27/02/2019
- irina.piticas@solvay.com => added 15/07/2019
- laure.pichot-plasse@solvay.com => added 05/12/2017
- pablo.prieri-contractor@solvay.com => added 13/02/2018
diogo.paiva@solvay.com => added 18/10/2018
vendula.sianska@solvay.com => added 06/02/2018
- nathalie.perillatcolomb-ext@solvay.com
- laura.labbadi-ext@solvay.com => added 15/07/2019
- bhaskar.patil@solvay.com => added 07/08/2019
- maggie.ma@solvay.com => added 07/08/2019
- min.yu@solvay.com => added 07/08/2019
- pablo.prieri@solvay.com => added 29/08/2019
- etienne.ribet-ext@solvay.com => added 02/01/2020
Removed
ann.bailly-ext@solvay.comremoved 12/02/2019mark.langston@solvay.comremoved 12/02/2019krystle.medina@solvay.com=> removed 13/02/2018marion.baggio@solvay.com=> removed 28/02/2017emmanuel.hatt@solvay.com=> removed 05/12/2017fabien.piret@solvay.com=> removed 29/10/2018pablo.prieri-ext@solvay.com => added 05/12/2017removed 13/02/2018Celia.gonzalez-roux@solvay.com=> removed 18/10/2018
pablo.prieri@solvay.com => added 05/12/2017removed 13/02/2018haixiang.song1@solvay.com=> removed 01/04/2019pablo.prieri-contractot@solvay.com=> removed 30/08/2019
Do not forget to record your modifications in that paragraph
Add or remove email adress in distribution list for DR data availability (GBU CM (aero))
NB: Distribution list exists on all systems, but user list is only maintained in production system WBP
Transaction SO23
Name DL_DP_002
Add or remove email adresses.
List of user email :
- ander.beain@solvay.com => CM => added 02/01/2020
- kevin.anderson2@solvay.com=> CM => added 02/01/2020
- kp.nagabhushana@solvay.com=> CM => added 02/01/2020
- patricia.harrison@solvay.com=> CM => added 02/01/2020
- amanda.pullen@solvay.com=> CM => added 02/01/2020
- laure.pichot-plasse@solvay.com => added 02/01/2020
- pablo.prieri-contractor@solvay.com => added 02/01/2020
diogo.paiva@solvay.com => added 02/01/2020
vendula.sianska@solvay.com => added 02/01/2020
ismail.ammor-ext@solvay.com => added 02/01/2020
- nathalie.perillatcolomb-ext@solvay.com => added 02/01/2020
- laura.labbadi-ext@solvay.com => added 02/01/2020
- bhaskar.patil@solvay.com => added 02/01/2020
- maggie.ma@solvay.com => added 02/01/2020
- min.yu@solvay.com => added 02/01/2020
- pablo.prieri@solvay.com => added 02/01/2020
- romain.clerc@solvay.com => added 02/01/2020
- etienne.ribet-ext@solvay.com => added 02/01/2020
Do not forget to record your modifications in that paragraph
Removed
Modify email message for DR data disponibility sent to users (All GBU except CM (aero))
Email message has to be modified in WBD and moved to WBQ, then WBP.
RSA1 / Chain PC_DPS_DYNASYS_15
Change to 'change' mode
right click => maintain message => Successful => Edit Document
Do not forget to record your modifications in that paragraph.
Modify email message for DR data disponibility sent to users (GBU CM (aero)
Email message has to be modified in WBD and moved to WBQ, then WBP.
RSA1 / Chain PC_DPS_DYNASYS_15
Change to 'change' mode
right click => maintain message => Successful => Edit Document
Do not forget to record your modifications in that paragraph.
Planned Evolution


























