General presentation

Objective of the application

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>

Usage information

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

• Demand Planning Scheduling
  IA_DPS
  

Process chain Display Component:

• 127 - PROJECT - DPS - Demand Planning Scheduling
  COMP_DPS_PC
  

Roles & Access

Roles and access

Authorisation objects

n/a

Dataflow presentation

Overview

Functional and Technical rules on Workbench

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

Conversion in KG unit

Transformation from ZWPPTDYS ECC table

Global Filter C_GLBFILT

Stream: DPS

Data loadings

Info providers and objects loaded

< detail of process chain, list + link between or special event done for the loading  >

Loading frequency

Daily: launched by the LO_DAILY_MASTER_DATA process chain around 6:00 AM each day.

• PC_DPS_DYNASYS_01
  DPS Dynasys: META - D - Daily Meta-Chain
  

Weekly: launched on saturday, 9:00 AM

• PC_DPS_DYNASYS_03
  DPS Dynasys: META - W - Weekly Meta-Chain
  
• Remark: Dynasays tool is awaiting data between 6:00 AM and 8:00 AM

Yearly: launched the 15th of January at 9:00 AM

• DPS Dynasys: META - Y - Cleaning Historical Data
  PC_DPS_DYNASYS_04
  

Average performance

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

Historization

<Give details if any historization is done, example: keep only data greater than beginning of Y-3>

Reporting

Queries Documentation or user guide

<to be done on customer wiki :  SBS IS - Customer Support Knowledge Base>

If not covered by queries documentation

Main queries

<list most important and/or complex queries only>

Main functionnalities

<give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts>

Broadcast

<give some detail on broadcast settings>

Maintenance

Known bugs

<list recurring bugs and demand from users>

Recurring procedure

< list recurring procedure >

Planned Evolution

<Detail planned major evolution if already known, example: complete decommissioning of application is planned in 2017 / Extension to solvay perimeter planned in 2^nd semester of 2016>