General presentation

The aim of the document is to list daily and monthly checks to do and following actions.

Daily checks are done by CGI team.

BW DynaSys Team will carry on to supervise the checks, and help CGI in case of issue/question

Depending of the period please contact : 

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 detailled information

Every day by 9.15 am CET

with transaction ST13 / BW-Tools,  use the variants DYNASYS_INTERF and DYNASYS_REPORT to have all the chains of interface and reporting

Check Interfaces chains - Steps to follow & Actions to do

Check following chains has run, and ended ok.

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 Reporting chains - Steps to follow & Actions to do

Check the process chain from the night before 6pm until current day 7am.

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 

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

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 have to be noticed.

=> If no timestamp at all,  inform users by using last received emails called (or create new message)

• "Demand planning BW report successfully update"
• "CM Aero-Demand planning in BW successfully updated"

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 (this action will be done by BW DynaSys team because it depends of the issue)

Check impact on QV - Demand Review for SBS Dashboard - All except CM (Aero)

Every day by 2.45 pm CET

Check following chain or check you have received the automatic email called "Demand planning BW report successfully update"

if no, refer to action described for morning reporting checks.

Contacts 

CGI team for WBP Chains Issues

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

DynaSys team for DYNASYS PROD Issues 

Etienne Ribet :              etienne.ribet-ext@solvay.com

Pablo Prieri (if Etienne is out):                 pablo.prieri-contractor@solvay.com

Richard LAUTH (if AERO issue) :           richard.lauth@qad.com

Know Issues

Field XXX is not a member of XXX

See Connection with UD CONNECT

Weekly and Monthly release days for DynaSys team (impact on loadings)

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,"  

Issue on APD => Dump on ST22 : TSV_TNEW_PAGE_ALLOC_FAILED

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 :

• Goto => performance Setttings

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.