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

Main filter : BU & Plant

Other filters: xxxxxxxx

Usage of error stack

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

Most DSO & Cubes are loaded in full mode to the low amount of data and/or calculation rules.

Exception:

DPDYN21

DPDYN22

<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

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

Queries Documentation or user guide

No dedicated documentation on queries

Main 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

Known bugs

• Customer Sales empty or inexact: due to loading routine in the 

Recurring procedure

n/a

Planned Evolution

Several minor evolution