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

Compare with Current View Page History

« Previous Version 15 Next »


General presentation

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

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.

ChainTypeDescriptionFrequencyCriticity

PC_DPS_DYNASYS_01

InterfaceDPS 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

InterfaceDPS 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



If both 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

If only PC_DPS_DYNASYS_25 is late => adapt Object and Content refering to DP
if both chains are late => adapt Object and Content 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/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.

ChainTypeDescriptionFrequencyCriticity

PC_DPS_DYNASYS_15

ReportingDPS Dynasys: META - D - 6.Reporting DynaSys (Dynamic KPIs)Daily at 7am , 2pm , 6pm , 11pm (Not on week-ends or certains bank holidays )HIGH

PC_APO_17

ReportingMETA - D - APO - Current period and future periodsDaily at 1am (Not on week-ends or certains bank holidays )LOW

PC_DPS_DYNASYS_09

ReportingDPS Dynasys: META - M - 6.Reporting DynaSys (Snapshots)Every 6th of month at 6amHIGH

PC_APO_18

ReportingMETA - M - APO - SnapshotsEvery 6th of month at 9amLOW



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


If chain PC_DPS_DYNASYS_15 has not run at 7am CET,

=> get last timestamp in DPS DPDYN39 / DYN - Table SYS_TIMESTAMP ( Write-Optimized )

=> inform  etienne.ribet-ext@solvay.com + pablo.prieri-contractor@solvay.com + nathalie.perillatcolomb-ext@solvay.com + Ismail.ammor-ext@solvay.com

=> inform users by using last received email called "Demand planning BW report successfully update"

Change Email Object by Demand planning BW report => Not available

Put Email content 

"Hello, 

Due to an issue, Demand planning BW reports are not available.
I will keep you informed when report are available."


=> inform QV team if necessary  guillaume.viaux-exterieur@solvay.com

Check impact on BW - DP - Demand Review for SBS Dashboard (QV)

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"

ChainTypeDescriptionFrequencyCriticity

PC_DPS_DYNASYS_15

ReportingDPS 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.

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 

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


Know Issues

Field XXX is not a member of XXX

See Connection with UD CONNECT


To be completed



  • No labels