You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

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 IdRole TitleExplanation
ZR_RCS_CA_M52 DP - Demand Planning

Role Menu Dynasys

Currently (Nov 2016), only 2 queries published in this role

ZBI_RCS_DP_A02Demand Planning - Dynasys

Role utilisateur Dynasys

Authorization object ZBI_DPS

  • gives access to Application Area IA_DPS_DYNASYS
  • authorization limited on GBU (CPFCTR1_2) (in WBP since 14/03/2017)
ZBI_RCS_DP_A03Demand Planning - Dynasys Keyuser

Authorization object  ZBI_DPS_K

  • gives access to transaction ZMAINT_MATPLANT + ZMAINT_MATVENDOR
  • gives access to Application Area IA_DPS_DYNASYS 
  • authorization limited on GBU (CPFCTR1_2) (in WBP since 14/03/2017)

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 objectExplanation

GBU (CPFCTR1_2)

ZR_*_CA_P05

Dataflow overview

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

IECRA determination (To be implemented => Item #58):

  1. Retrieve the division from the material
  2. Find the IECRA (0G_CWWE01) in MD C_CDSA which is the distribution channel with the division as compound.
  3. If the IECRA is not found, use MD C_MATPNT2 which is the material with the source system and the plant as compound.

BU/GBU determination

Sold-to 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.

Dependencies with other applications

Data loadings

Info providers and objects loaded

 

Process ChainCodeTypeFrequencyComments
DPS Dynasys: META - M - 6.Reporting DynaSys (Snapshots)PC_DPS_DYNASYS_09 MAIN
  • Monthly, the 6th of the month at 6am
  • Whole chain last around 10 minutes (07/10/2016)

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_15MAIN
  • 5 times a day
  • Whole chain last arount 15 minutes (17/11/2016)

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_23MAIN
  • Daily (to be planned after Dynasys loading ex DBDYN33, DBDYN12, DBDYN02)

Not YET PLANNED

A remaining issue :

  • DTP DBDYN33 -> C_DYN_017 - Full => dupplicates on Ship-to 703581S / SDSOA
    cause : the DC is not filled for all loadings (subject in progress Julien/Emmanuel)
    solution : the DTP has to handle dupplicates (done only in WBP as solution is temporarly

Issue solved :

 

  • DTP DBDYN12 -> C_DYN_018 - Full => dupplicated on Ship-to 66946R
    cause: specific rule for plant 8000 is not applied for Ship-to with extension (subject in progress Julien/JC)
    solution: in DSO DBDYN12 delete line with Ship-to 66946R / Plant 8000


DPS Dynasys: META - D - 6.Reporting DynaSys (Obas data)PC_DPS_DYNASYS_20MAIN
  • Daily at 5 am
Temporarly schedulling! this chain has to be added in Obas chain or launched via an Obas event

Loading frequency

Average performance

 

Key FigureEstimation
~ 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

QueryDescriptionTypeRole MenuComments
BW_QRY_MVDYN11_0005BW - DP - Forecast Accuracy (Core query)QRY

DP - Demand Planning

 

BW_QRY_MVDYN11_0006

BW - DP - Demand Review (Core query)QRYDP - Demand Planning

 

QVSBS_BW_QRY_MVDYN11_0001BW - 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

 

  • No labels