Data, Analytics & AI Platform

Page tree


Versions Compared

Old Version 2

changes.mady.by.user Sianska, Vendula

Saved on

compared with

New Version Current

changes.mady.by.user POLOSSON-ext, Damien

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

See also file maintained by Authorization team : BW Catalog of Roles / link: https://drive.google.com/open?id=10GEfKYqrT1eeTO_uHYAheL1GX7L5y_pvH0KQU64qh5Ifile/d/19gsedRH8SCaqIORz4YziPsYuNAFx0q_ElE9uSBBzWQk/view

Authorization objects

Reporting is limited to authorized GBU (Global Business Unit)

...

Company Code also, it will be added ( item #39)

 

 

FORECAST ACCURACY - End of Month View (C_FCSTMTH)

...

    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 201707.201707.2017M
6th of August 201707.201708.2017M-2
6th of August 201707.201702.2019M-20
6th of August 201707.201708.2016N/A

...

The list of the different Datafields loaded from Dynasys and their respective RKF is available here.

To know if the Datafield type is a quantity (assignment of the value to K_DYN_021) or an amount (assignment of the value to K_DYN_021), we're using Global filters entries.

...

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
  • 4 times a day
  • Whole chain last arount 30 to 45 minutes (06/08/2020)

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

DR for CM or DR for All GBU block


Change C_LOW by "Y" if loading has to be bypassed

 

Load AERO-Prog/market from DynaSys ?

Chain 15 is running 4 times a time, but Aero Prog/Market needs to be loaded only once a day, at 2pm.

Decision block is checking time, and also check the timestamp date = today's date



 

Email Messages send at chain's end to inform DynaSys Team + list of Users + BW DynaSys Team when data is up to date

see procedure for details of message

=> Modify email message for DR data disponibility sent to users (All GBU except CM (aero))

=> Modify email message for DR data disponibility sent to users (GBU CM (aero)


DPS Dynasys: META - M - 6.Reporting DynaSys (MasterData)PC_DPS_DYNASYS_23MAIN
  • Daily at 22.15pm

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 6.15 am (changed 21/11/2017)
 Temporarly schedulling! this chain has to be added in Obas chain or launched via an Obas event
DPS Dynasys: TD - D - Reporting Dynasys (DIP Inventory KPIs)PC_DPS_DYNASYS_33MAIN
  • 4 times a day
  • Whole chain last arount 20 mintutes (April 2022)

Based on Table EXP_DIP_BW_SKU_SITE_BW,  EXP_DIP_BW_SKU_BW & EXP_DIP_BW_MD_SKU_BW.



 

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 3


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 (tableSYS_TIMESTAMP / info for EXP_DIP_BW)

If timestamps between 2 loadings, the chain has to carry on

Block only Master Data DIP/PP (view EXP_DIP_BW_MD_SKU_BW)

Change value of the following global filter variable to by-pass the step :

Block only SKU DIP/PP (view EXP_DIP_BW_SKU_BW)

Change value of the following global filter variable to by-pass the step :

Block only SKU SITE DIP/PP (view EXP_DIP_BW_SKU_SITE_BW)

Change value of the following global filter variable to by-pass the step :


 

Email Messages send at chain's end to inform DynaSys Team + list of Users + BW DynaSys Team when data is up to date

see procedure for details of message

=>Modify email message for DIP/PP data disponibility sent to users

=>Add or remove email address in distribution list for DiP-PP reporting





 


Loading frequency

Average performance

...

A snapshot reload by flat file has to be validated in WBQ first


File structure to use

https://docsdrive.google.com/spreadsheetsfile/d/11v1GZUu8w7Sg7RSG2O1pTETTzabr6bHN1UvK276FIGP4U3PmRtaytZbmxYO0zntcG/edit#gid=1857575871view


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
  • file should not contain ANY prospects (otherwise data activation is not possible)

...

Many reloads have been done to correct FA data or after organization changes

Details of manual corrections (2017 - 2024)

  • April 2017 - SILICA - End of March snapshot reloading
    View file
    nameReprise EXP_FORE SILICA.csv
    height250

...

  • July 2023 - PO2 Project - transcodification of PF1 DFU to new WP1 DFU

list of DFU to be transcoded (source DynaSys team)


  • January 2024 – Annual cleaning – Year 2020 removed

    Cleaning done to have less data to rework

    Full year deletion is done manually by selective deletion.

    First for DBDYN13, then DPDYN01

    First for a single period to make sure all is working fine, then for the full year

...

2 materials/PEROX where also manually deleted due to remaining GH € for other periods

65392S

PEROX

68350S

PEROX

  • January February 2024 – Mass cleaning:

Objective: delete useless lines in FA DSOs to reduce volume (space gain, loading time gain and less record to rework

...

in case of structure change)    
It is concerning lines with concerned month = N/A, M-9, M-8    
1) DBDYN13 : for each month, identified the list of end of month concerned. This is done via a query on the DSO (see tab DBDYN13)    
    For each month proceed to following steps
    A) Get nb of records in active table of DBDYN13 for the month + list of end of month (for check)
    B) Do a selective deletion in DBDYN13 for the month + list of end of month concerned
    C) Get nb of records in active table DBDYN13 to make sure only the wanted records have been deleted
    D) Do a selective deletion in DPDYN01 with the same selection
    E) Refresh the query on DBDYN13
    F) repeat from step A) for next month
IMPORTANT : always do first deletion in DBDYN13 and do checks. In Case of issue, data are still in the lower level DPDYN01    

File with details:

View file
nameFA mass cleaning.xlsx
height250

  • January 2024 – rework of snapshot for H2O2 EG moved from CH to PEROX (structure change)

    This rework is necessary for PF1 This rework is necessary for PF1 records to align forecasts & Gross History on same line (same key) : 

    • Future periods : forecast M-1 to M-7 were collected with key CHELC. Gross history will be received with key PEROX
    • Past periods : forecasts and GH are already aligned, but masterdata Material/Ship-to/CHELC are not maintain anymore so to be sure to get last attributs (ex sales rep) on PEROX, past periods have also to be migrated to PEROX

    1)   Extraction DPDYN01 with selection on listed Materials

    2)   Check that no PEROX are remaining (otherwise delete lines first)

    3)   Create 4 files :

    -           One with data for PEROX, source system SDK_DYNASY

    -           One with data for PEROX, source system WBP_HANAIV

    -           One with data for SPE CHEM, source system SDK_DYNASY and set all figures with 0

    -           One with data for SPE CHEM, source system WBP_HANAIV and set all figures with 0

    NB: as lines were existing for End of Month view = previous month with only GH €, these have been removed from files otherwise it will erase forecasts & GH recorded with last snapshot

    4)   Load DPDYN01 with PEROX data (with changing global filter in between)

    5)   Make sure results with PEROX are same as the SPE CHEM ones

    6)   Load DBDYN03 with PEROX data

    7)   Make sure results with PEROX are same as the SPE CHEM ones

    8)   Do same loading with SPE CHEM

    9)   Make sure all SPE CHEM line are with null values

    10)   Run loop on DBDYN03

    11)   Several checks can be done

    ð   For previous month, M to M-7 forecast and GH should be filled

    ð   For future month, M should be empty (except GH € which exists for unknown reason)

    ð   For future month, M-2 should be filled

...

Link to Google drive with the files:

Google Drive Live Link
urlhttps://drive.google.com/drive
/u
/
0/
folders/
1qYwjTa088q9yEkMrv--fWIoDJY_X8wBk
1oCor2Za-GEB7VX6qj2K9XmCKhK8nx7cz




1) prepare DFU file : split DFU new by Material/Ship-to/DC + split DFU old by Material/Ship-to/DC

...

2 )  manually schedule again PC_DPS_DYNASYS_09 for next month

To do this, first, transaction RSPC, menu execution>remove from schedule (steps will become grey instead of green), then change starter by right click


Image Modified


Image Modified

 change the dates to next month

Image Modified

Execution > Schedule


3 ) If the recover is not done the 6th of the month, you have to inform Tableau's team to reload the application (Tableau should be uploaded the 7th of the month, as it was for the QV application)

*** Service one ticket *** to be updated with an example

...


Oil&Gas (OG):

 

Digital Technology :

...

Do not forget to r ecord your modifications in that paragraph.

 

Clean Forecast Accuracy for all GBU except CM-AERO (ABAP ZBW_DYN018)

...

2021 was wrongly filled with oct 2022 datadata MTP snapshot flat file 2021 - 1 - only CH DCs.zip

2022 was manually archived the 19th of April 2023, re-captured in Dec2023 MTP 2022 - NEW EXTRACT adj - clean.zip


Ship-to/Forecast Customer descriptions onshot loading for CM-AERO and BAAN/PE1 cases

...

Step 3- Store informations in a google sheet (link) to follow decommissioning

...


Powered by Atlassian Confluence and Brikit Theme Press