BW Demand Planning Scheduling (DPS)
<describe in a few words the content of application + link with functional or technical specifications (google links) done with during the project or linked with PPMO>
Tool Leader
IT leader of the application:
Name of project: Dynasys
PMO Project: 6046 S&OP with Dynasys - Core model and pilot
UR335513 DYNASYS Sales Forecast
UR333365 DYNASYS Demand Planning
Main leader for the application
Reporting Coordinator: GONZALEZ-ROUX, Célia <celia.gonzalez-roux@solvay.com>
< How many users? Which user category ? Is there critical period ? Which geographical perimeter?
Describe in one sentence: around 50 users, worldwide or 200 users / European Site>
InfoArea:
Process chain Display Component:
| Role Id | ||
|---|---|---|
| ZR_RCS_CA_M52 | DP - Demand Planning | Role Menu Dynasys |
| ZBI_RCS_DP_A02 | Demand Planning - Dynasys | Role utilisateur Dynasys |
| ZBI_RCS_DP_A03 | Demand Planning - Dynasys Keyuser | Role Key user Dynasys, accès aux transactions
|
n/a
<detail of main topics with explanations of the rules and only the main + special rules about queries to run and use in the correct way
+ dependencies with other application (BW, QV, Externals tools like PVelocity or Dunasys etc...>
General presentation: most DSO / Cubes are used to extract data to the Dynasys tool.
Data are extracted from a source outside BW dynasys (it could be another BW application, ECC table, query etc), loaded into DSO and/or Cubes. Then data are transformed through an APD and loaded into flat files which are loaded into the Dynasys tool.
Stream: DPS
< detail of process chain, list + link between or special event done for the loading >
Daily: launched by the LO_DAILY_MASTER_DATA process chain around 6:00 AM each day.
Weekly: launched on saturday, 9:00 AM
Yearly: launched the 15th of January at 9:00 AM
<if possible, give some information on average process chain duration, amount of data loaded and total data volume example: daily process chain loaded in 30 min, weekly chain loaded in 1h15, with around 2k to 10k lines in DELTA mode for a total of 10M lines in cube
The purpose is to give a general overview of the volume of data managed y the application>
<Give details if any historization is done, example: keep only data greater than beginning of Y-3>
<to be done on customer wiki : SBS IS - Customer Support Knowledge Base>
If not covered by queries documentation
<list most important and/or complex queries only>
<give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts>
<give some detail on broadcast settings>
<list recurring bugs and demand from users>
< list recurring procedure >
<Detail planned major evolution if already known, example: complete decommissioning of application is planned in 2017 / Extension to solvay perimeter planned in 2nd semester of 2016>