The aim of the document is to list daily and monthly checks to do and following actions.
Daily checks are split between BW DynaSys team menbers of us following this planning
| Period | Responsible |
|---|---|
| 1 to 10 of each month included | Ismail Ammor |
| 11 to 20 of each month included | Julien Agasse |
| 21 to 30 or 31 of each month included | Nathalie Perrillat-Collomb |
Please register all production issue in following google spreasheet
with transaction ST13 / BW-Tools, use the variants DYNASYS_INTERF and DYNASYS_REPORT to have all the chains of interface and reporting
Check following chains has run, and ended ok.
| Chain | Type | Description | Frequency | Criticity |
|---|---|---|---|---|
PC_DPS_DYNASYS_01 | Interface | DPS DynaSys: META PART1 - D - Daily Meta-Chain Part 1 | Daily after Global sales chains (Not on week-ends or certains bank holidays ) => starter = EVENT Z_EVT_END_GL006 | HIGH |
PC_DPS_DYNASYS_25 | Interface | DPS DynaSys: META PART2 - D - Daily Meta-Chain Part 2 | Daily after Global sales chains (Not on week-ends or certains bank holidays ) => starter = EVENT Z_EVT_END_GL003 | HIGH |
| PC_DPS_DYNASYS_03 | Interface | DPS Dynasys: META - W - Weekly Meta-Chain | Weekly on saturdays à 9am CET | HIGH Certain GBUs are weekly refreshed on DynaSys => In case of issue, inform DynaSys team on Monday CAUTION : This chain should not be repaired on mondays as daily chain is replacing it |
If both daily chains have not finished by 7 am, identify the root cause and estimate the ended time (if possible)
Inform Dynasys team before by 9:15 am CET
Email address: SBS-IS-DynaSys-team@solvay.com + nathalie.perillatcolomb-ext@solvay.com + Ismail.ammor-ext@solvay.com + julien.agasse-ext@solvay.com
If only PC_DPS_DYNASYS_25 is late => adapt object and content of the email refering to DP
if both chains are late => adapt object and content of the email refering to both DP / DiP-PP
Email Object : /!\ [DP/DIP-PP] Dynamic import will be late today
Email Content (to be adjusted according to impact DP and / or DiP-PP):
"Hello,
Due to an issue on BW side, data files will not be available for Dynasys integration before 11:00 CET.
The integration in Dynasys will be ended approximatively between 12:00 (DIP1/DIP2) and 13:00 CET (DP1/DP2/DP3).
Regards,"
* give more details about the issue (Global Sales delay, Global Sales error, DynaSys chain issue, Source System PF1/WP1 issue...)
Check the process chain from the night before 6pm until current day 7am.
| Chain | Type | Description | Frequency | Criticity | Comment |
|---|---|---|---|---|---|
PC_DPS_DYNASYS_15 | Reporting | DPS Dynasys: META - D - 6.Reporting DynaSys (Dynamic KPIs) | Daily at 7am , 2pm , 6pm , 11pm (Not on week-ends or certains bank holidays ) | HIGH | |
| removed from scheduling 07/07/2020 (Special Chem Go-Live) | ||||
PC_DPS_DYNASYS_09 | Reporting | DPS Dynasys: META - M - 6.Reporting DynaSys (Snapshots) | Every 6th of month at 6am | HIGH | |
| removed from scheduling 07/07/2020 (Special Chem Go-Live) |
If chain PC_DPS_DYNASYS_15 has not run at 6pm CET previous night or 11pm CET previous night
=> inform etienne.ribet-ext@solvay.com + pablo.prieri-contractor@solvay.com + nathalie.perillatcolomb-ext@solvay.com + Ismail.ammor-ext@solvay.com + julien.agasse-ext@solvay.com
If chain PC_DPS_DYNASYS_15 has not run at 7am CET or 2pm CET
=> get last timestamp in DPS DPDYN39 / DYN - Table SYS_TIMESTAMP ( Write-Optimized ) by running IP "IP: DTS_SYS_TIMESTAMP (Dynasys) - Full with filters"
=> check time stamps date + time
=> inform etienne.ribet-ext@solvay.com + pablo.prieri-contractor@solvay.com + nathalie.perillatcolomb-ext@solvay.com + Ismail.ammor-ext@solvay.com + julien.agasse-ext@solvay.com
=> inform users by using last received emails called (or create new message)
Add distribution list :
$DynaSysDP2-KeyUsers (DP2 = CM Aero) => for CM Aero message
$DynaSysDP3-KeyUsers (DP3 = Novecare) => for others GBUs
$DynaSysDP-KeyUsers (DP = rest of GBUs) => for others GBUs
Change Email Object
Demand planning BW report => Not up to date or Not available => for others GBUs
CM Aero-Demand planning BW report => Not up to date or Not available => for CM Aero
Put Email content
"Hello,
Due to an issue, Demand planning BW reports are not up to date or not available
I will keep you informed when report are available."
=> inform QV team if necessary guillaume.viaux-exterieur@solvay.com
Check impact on QV - Demand Review for SBS Dashboard - All except CM (Aero)
Check following chain or check you have received the automatic email called "Demand planning BW report successfully update"
| Chain | Type | Description | Frequency | Criticity |
|---|---|---|---|---|
PC_DPS_DYNASYS_15 | Reporting | DPS Dynasys: META - D - 6.Reporting DynaSys (Dynamic KPIs) | Daily at 7am , 2pm , 6pm , 11pm (Not on week-ends or certains bank holidays ) | HIGH |
if no, refer to action described for morning reporting checks.
Uppasettyraghava Harsha : harsha.uppasettyraghava-ext@solvay.com
Yeturu, Amareshwar : amareshwar.yeturu-ext@solvay.com
Radha Eepuri : radha.eepuri-ext@solvay.com
Generic email address (caution 23 members) : SBS-IS-Appli-Techno-Report-BW.CGI@solvay.com
Pablo Prieri : pablo.prieri-contractor@solvay.com
Etienne Ribet : etienne.ribet-ext@solvay.com
Richard LAUTH (if Etienne is out) : richard.lauth@qad.com
Mathieu Ursprung (if Etienne is out) : m8u@qad.com
See Connection with UD CONNECT
DynaSys DP = Weekly release all Mondays from 12pm to 12h45pm + Monthly release every 1st Thursday of month
DynaSys DIP = Monthly Release every 2nd Thurdays of month
Note that during the days of the monthly release, Demand Planning BW report is not updated at 2pm and sometimes also 6pm.
Below, an example of email to inform users:
"Hello,
Due to Release on DynaSys side, Demand Planning BW report will not be updated at 2pm CET. The next update is scheduled today at 6pm CET.
Thanks for your understanding.
Regards,"