The aim of the document is to list daily and monthly checks to do and following actions.
All checks are done by CGI team.
In case of BW assistance, contact Felipe Rodrigues (Competence Center / SCMS domain)
In case of DynaSys assistance, contact DynaSys.Interface.Team@solvay.com
In case of MFT/Webservice assistance, contact support.xml@solvay.com
Please register all production issue in following google spreasheet
Due to several complaints from DynaSys Team and DynaSys users, it is important to fill the document with detailed information
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 Interface Team before by 9:15 am CET => DynaSys Interface Team : Interface 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 | |
PC_DPS_DYNASYS_09 | Reporting | DPS Dynasys: META - M - 6.Reporting DynaSys (Snapshots) | Every 6th of month at 6am | HIGH | |
| PC_DPS_DYNASYS_23 | Reporting | DPS Dynasys: META - M - 6.Reporting DynaSys (MasterData) | Daily at 10pm (Not on week-ends or certains bank holidays ) | MEDIUM | |
| PC_DPS_DYNASYS_33 | Reporting | DPS Dynasys: TD - D - Reporting Dynasys (DIP Inventory KPIs) | Daily at 10am (or 11am), 2pm , 6pm , 11pm (Not on week-ends or certains bank holidays ) | MEDIUM | |
| removed from scheduling 07/07/2020 (Special Chem Go-Live) | ||||
| 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 DynaSys.Interface.Team@solvay.com
If chain PC_DPS_DYNASYS_15 has not run at 7am 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 DynaSys.Interface.Team@solvay.com
If timestamp is over 7am, BW DynaSys Team will analyse if it is worth it to force an intermediate upload.
In case of intermediate load, no need to inform users. Otherwise users will be noticed by DynaSys.Interface.Team@solvay.com => DynaSys Interface Team : Reporting Issue
If no timestamp at all, inform DynaSys.Interface.Team@solvay.com => DynaSys Interface Team : Reporting Issue
If chain PC_DPS_DYNASYS_33 has not run at 6pm CET previous night or 11pm CET previous night
=> inform DynaSys.Interface.Team@solvay.com
If chain PC_DPS_DYNASYS_33 has not run at 10am CET or 11am CET
=> get last timestamp in DPS DPDYN39 / DYN - Table SYS_TIMESTAMP ( Write-Optimized ) by running IP "IP: DTS_SYS_TIMESTAMP (Dynasys) - Full with filters"
Daynasys Source = BW
Dynasys - Table Name = EXP_DIP_BW
Dynasys - Type = TECH : EXPORT BW
=> check time stamps date + time
=> inform DynaSys.Interface.Team@solvay.com
If timestamp is over 11am, BW DynaSys Team will analyse if it is worth it to force an intermediate upload.
In case of intermediate load, no need to inform users. Otherwise users will be noticed by DynaSys.Interface.Team@solvay.com => DynaSys Interface Team : Reporting Issue
If no timestamp at all, inform DynaSys.Interface.Team@solvay.com => DynaSys Interface Team : Reporting Issue
Check following chain or check you have received the automatic email called "Demand planning BW report successfully update" (for PC_DPS_DYNASYS_15) and "DiP-PP reporting in BW successfully updated" (PC_DPS_DYNASYS_33).
| 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 |
| PC_DPS_DYNASYS_33 | Reporting | DPS Dynasys: TD - D - Reporting Dynasys (DIP Inventory KPIs) | Daily at 10am (or 11am), 2pm , 6pm , 11pm (Not on week-ends or certains bank holidays ) | Medium |
if no, refer to action described for morning reporting checks.
Email address: DynaSys.Interface.Team@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 round 12:00 CET for DiP1/DiP2/DiP3 and 12:30 CET for DP1/DP2/DP3.
Regards,"
* give more details about the issue (Global Sales delay, Global Sales error, DynaSys chain issue, Source System PF1/WP1 issue...)
email or tchat DynaSys.Interface.Team@solvay.com with DPDYN39 contain
Message to users by using last received emails called (or create new message)
Add distribution list :
$SBS-IS-DynaSys team => IS Team
$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
=> inform QV team if necessary guillaume.viaux-exterieur@solvay.com (depending of the issue)
Check impact on QV - Demand Review for SBS Dashboard - All except CM (Aero)
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."
$DynasysDP1-KeyUsers
$DynasysDP2-KeyUsers
$DynasysDP3-KeyUsers
$DynasysUsersDiP1 (Silica Soad Perox) <DynasysUsersDiP-PP@solvay.com>
$DynaSysUsersDiP2 (TS - Aroma) <DynaSysUsersDiP-PP2@solvay.com>
$DynaSysUsersDiP3 (Novecare) <DynasysUsersDiP3@solvay.com>
If there is a requirement for follow-up (on incident status), a wiki or google doc could be
Generic email address (caution 23 members) : SBS-IS-Appli-Techno-Report-BW.CGI@solvay.com
DynaSys.Interface.Team@solvay.com
See Connection with UD CONNECT
DynaSys DP = Weekly release all Mondays from 12pm to 12h45pm + Monthly release every 1st Thursday of the month
DynaSys DIP = Monthly Release every 2nd Thurdays of the 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,"
Sometimes it can be possible to have an issue at APD level when there is no more memory available.
ST22 Dump log :
When it's happened, try to modify the Performance settings at APD Level :
By default the flag is active.
TODO :
Uncheck the Process Data in Memory, activate the APD and repeat the step in issue at the process chain level.
If WBP in not available during saturday morning, you have to manually generate weekly files
Run temporally chain PC_PP_BOM_06 to update BOM (until PF1 bug fixing) + reload ADSO ABDPDY50 then generate BOM file