General presentation
The aim of the document is to list daily and monthly checks to do and following actions.
Every day by 9 am CET
Chains information
| Chain | Description | Frequency | Criticity |
|---|---|---|---|
PC_DPS_DYNASYS_23 | DPS Dynasys: META - M - 6.Reporting DynaSys (MasterData) | Daily at 22pm (Not on Sundays or publuc holidays ) | |
PC_DPS_DYNASYS_01 | DPS DynaSys: META PART1 - D - Daily Meta-Chain Part 1 | Daily after Global sales chains (Not on Sundays or publuc holidays ) | |
PC_DPS_DYNASYS_25 | DPS DynaSys: META PART2 - D - Daily Meta-Chain Part 2 | Daily after Global sales chains (Not on Sundays or publuc holidays ) | |
PC_DPS_DYNASYS_15 | DPS Dynasys: META - D - 6.Reporting DynaSys (Dynamic KPIs) | Daily at 7am , 14pm , 18pm , 23pm CET (Not on Sundays or publuc holidays ) | |
PC_APO_17 | META - D - APO - Current period and future periods | Daily at 01am (Not on Sundays or publuc holidays ) | |
PC_DPS_DYNASYS_09 | DPS Dynasys: META - M - 6.Reporting DynaSys (Snapshots) | Every 6th of month at 6am CET | |
PC_APO_18 | META - M - APO - Snapshots | Every 6th of month at 9am CET | |
Steps to follow & Action to do
with transaction ST13 / BW-Tools, use the variants DYNASYS_INTERF and DYNASYS_REPORT to have all the chains of interface and reporting
For the Reporting part, check the process chain from the day before from 18pm until current day 7am.
for the Interface part, check whether the PC_DPS_DYNASYS_25, PC_DPS_DYNASYS_01 and PC_DPS_DYNASYS_09 process (the 6 of each month) have done well.
Every day by 3 pm CET
Chains information
| Chain | Description | Frequency | Criticity |
|---|---|---|---|
PC_DPS_DYNASYS_15 |