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

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.

Useful file to understand dataflow from APD to source, and check filters applied all along the dataflow:

Conversion in KG unit

Only conversion in two steps are managed (UOM then T006; conversion in Three or more steps are not managed in Dynasys and should be updated by the business)

Transformation from ZWPPTDYS ECC table

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

>>>>>>>>>> To be detailed

Global Filter C_GLBFILT

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

Usage of error stack

>>>>>>>>>> To be detailed

Specific table

ZMATPLANT

ZMATVENDOR

>>>>>>>>>> To be detailed

"UD connect" connection

WDCCLSLBV01\SLV1_DBPRD

WDCCLSLBV01\SLV1_DBDEV

Data loadings

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
  

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.

Average performance

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

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 (C_CUSTSAL or 0CUST_SALES)

Due to loading routine in the propagation level of DPSDSO05 / DSO_SD02 which are loaded in delta mode, this field is not correctly updated

Customer Sales attributes empty or inexact (0CUST_SALES)

Modification on ZZ fields are not taken by the delta. Only full loading can fix this problem.

Update of UD Connect datasource

Data loaded from Dynasys tool are using "UD connect" connection type (Java).

Datasource updated in Udconnect can encounter problem in WBQ / WBP due to Metadata cache (whereas everything is ok in WBD)

S:RSSDK:300 Field GHFF_QUANTITY is not a member of /BIC/CADTS_ EXP000010000001

Message no. RSSDK300

Ask Addagio team for a « cache clearance for quality / production system on this JCO connection” 

Recurring procedure

n/a

Planned Evolution

Several minor evolution