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.
Specification are available in the following spreasheet:
In the 
The ZWPPTDYS is loaded on ECC side through the transaction ZWPPTMRPOUT (which load the ZWPPMRPOUT program)
This table is loaded from PF1/WP1 into WBP in the DPDYN02 DSO (Propagation) and then in the DBDYN14 (Propagation).
Stream: DPS
Main filter : C_PFCTR2 (BU) and PLANT
These 2 filter may be extended regularly due to the extension of Dynasys perimeter (RCS en january 2016, Soda in june 2016)
Other filters: C_MGN_ACC, DEL_TYPE, ITEM_CATEG, MATL_TYPE, REASON_REJ, REC_TYPE
Loading frequency
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
Flag end of process chain: For both daily and weekly process chain, at the end of APD execution, a command is sent to the Dynasys tool. This command must be executed in productive environnement only and is not effective in other environnement (it will raise an error). The Decision process prevent execution of the command in non productive environnement.
Most DSO & Cubes are loaded in full mode due to the low amount of data and/or calculation rules.
Exception:
DPDYN21: 2,1 M lines loaded in delta mode
DPDYN22: 2,2 M lines loaded in delta mode
Daily chain usually run for 25 to 45 minutes.
Weekly chain usually run for 40 minutes to 1,5 hour
Remark: on going evolution will transfer most process in the weekly chain to the daily one (increasing duration of daily chain and decreasing weekly chain).
No data below 3 year before beginning of current year are kept. Ex: in Aprl 2016, only data greater than or equal to 01.01.2013 are loaded in Dynasys.
Reporting
No dedicated documentation on queries
only one queries (5/2016). To be updated with the Sales Follow Up evolution (Anne-Laure Bouchet) and the Forecast Accuracy evolution (Laressa Moretti)
Main functionnalities
n/a
Broadcast
n/a
Maintenance
Recurring procedure
n/a
Several minor evolution