The new wiki link for this data flow is here:

BW OTC - Supply Chain- DPS (WBP) 

Please update the new doc there and no longer here.

General presentation

Objective of the application

BW Demand Planning Scheduling (DPS)

Image Modified

Tool Leader: Antoine Roy Alexandre Eliane

IT leader of the application: Guillaume Thevenet  Laura Labbadi (DynaSys DP), Alexandre Eliane (DiP-PP), Mario Simonelli (BW), Craig Wanamaker (BW backup)

Name of project: Dynasys DynaSys

PMO Project: 6046 S&OP with Dynasys - Core model and pilot

UR: UR335513 DYNASYS Sales Forecast / UR333365 DYNASYS Demand Planning

Reporting Coordinator: GONZALEZ-ROUX, Célia <celia.gonzalez-roux@Reporting Coordinator: PAIVA Diogo <diogo.paiva@solvay.com>

Usage information

Number of users: tbd

Critical period: none

Geographical perimeter: worldwide

InfoArea:

• Demand Planning Scheduling
  IA_DPS
  Image Removed

Process chain Display Component:

• 127 - PROJECT - DPS - Demand Planning Scheduling
  COMP_DPS_PC
  Image Removed

Roles & Access

Roles and access

See also file maintained by Authorization team : BW Catalog of Roles / link: https://drive.google.com/open?id=10GEfKYqrT1eeTO_uHYAheL1GX7L5y_pvH0KQU64qh5I

Authorization objects

List of autorisation objects mandatory for the application.

Dataflow presentation

Overview

Reporting Part DataFlow

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:

Image Removed

Conversion in KG unit

Image Removed

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

The different step of the routine are the following:

Creation of internal table

Creation of internal table between T006and T006D (T006D provide the fields MSSIE, base unit of a dimension DIMID)
Creation of internal table for DSO UOMCMAT2, filled with both conversion from UOM to UNIT and UNIT to UOM and joined with T006 to get Dimension DIMID

Conversion in KG (if possible)

Quantity needs to be converted to KG.

The routine check:

1. if Quantity is already in KG, nothing is done
2. if Quantity is equal to 0, Unit is set to KG
3. if Unit is in dimension MASS (the same dimension as the one for KG), then conversion is done in KG using T006
4. if Unit is not in MASS, we check in UOMCMAT2 if we have a direct conversion from UNIT to KG
5. if no direct conversion exists, we check if there is a conversion from Unit to any MASS unit and after conversion we apply another conversion from MASS to KG using T006

If no conversion exists, Unit remains empty and will be manage as an error (see below)

Catch missing conversion

The flow uses Error DTP. When Unit can't be converted, the routine raise an exception "cx_rsrout_skip_val". The error is loaded in the error queue with text from the message class ZDYN_CONV_ERROR

Not all error will be fixed. Most of these error are linked with BU outside of Dynasys perimeter.

Transformation from ZWPPTDYS ECC table

Documentation

Functional specification are available in the following spreadsheet:

In the following tabs:

Image Removed

ECC process

The ZWPPTDYS is loaded on ECC side through the transaction ZWPPTMRPOUT (which load the ZWPPMRPOUT program)

This transaction use the program RMDMRPEXTRACT01 which create a list of material to extract.

Then, for each material, the program RMDMRPEXTRACT01 run through the exit ZCL_PP_IM_MD_SR_LIST_EXTRACT.

This exit reads the database for each material and loads in memory several table among which is table IT_MDPSX.

Then, through specific code, the table ZWPPTDYS is loaded from IT_MDPSX using method IF_EX_MD_SR_LIST_EXTRACT~EXTRACT_SR_LIST_INFOS

BW Process

This table is loaded from PF1/WP1 into WBP in the DPDYN02 DSO (Propagation) and then in the DBDYN14 (Propagation).

All rules are available in the following transformation

ODSO DPDYN02 -> ODSO DBDYN14

See short description of this rules below

 Begin of global

1. Declaration of types
2. Declaration of table & variable

Begin of routine

1. Declaration of field-symbols
2. Refresh internal table
3. Clear variable
4. Get Source system using class oref_dynasys_utils, method get_source_systems
5. Get Systems extensions using class oref_dynasys_utils, method get_system_extension

Phase 0: Table preparation

Load each required table into hashed table.

Phase 1: DSO Enrichment

Depending on value of field c_delkz:

1. Step 1: Ship/Rec Shipto ID (PARTNER_CUST_ID)
2. Step 2: Ship/Rec plant ID (PARTNER_PLANT_ID)
3. Step 3: Complement ID (COMPL_ID)
4. Step 4a: BU Source
5. Step 4b: BU Destination
6. DOC_TYPE
7. ITEM_CATEG

Remarks:

• Step 1 to 4 depends on result of previous step. No simplication is done in the code.
• If in Step 1, PARTNER_CUST_ID equals source_field-X, in step we will use PARTNER_CUST_ID and not source_field-X
• This means any error in the code will raise error in further rules. This is a choice in all the routine and this logic must be kept.
• For Step 1,2,3, value are loaded without modification in variable ended by*_origin (and later in the script, these value are saved in dedicated infooject to ease debugging)
• Even useless rules are loaded to keep homogeneity in the code, example: loading a field at null even if this field is already null.

Between phase 1 and 2:

Fields are assigned for expert routine (source to result)

System extension is added to field (Material, Plant, Partner plant ID etc) and remove unneeded 0 using function conversion_exit_alpha_output. These new value are stored in dedicated infooject to e used later in Phase 2 of script

A check is done to find any correspondance with content of specific tale zmatplant and zmatvendor

...

Once Phase 1 is finished, depending on DELKZ value, several fields are loaded:

• File flag fields: these flag will be used in APD to dettermine which data needs to be loaded in flat file
• Flowid identify which rule has been applied regarding the specification
• SKU R in FS (C_FLGSRF), filled from PARTNER_CUST_ID / PARTNER_PLANT_ID / COMPL_ID depending on flow id value.

All rules are checked one after the other. Once one check is validated, the check stop

Remarks: c_pfctr2 = BU SOURCE and c_recptbu = BU DESTINATION

Global Filter C_GLBFILT

Image Removed

Stream: DPS

Image Removed

Main filter : C_PFCTR2 (BU) and  PLANT

These 2 filter may be extended regularly due to the extension of Dynasys perimeter (RCS in 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

Error stack are used in relation with Unit and Currency conversion.

Most if not all error are linked with BU outside current perimeter of project and won't be fixed.

Each DTP has the following settings:

DTP

Image Removed

Error DTP

Image Removed

Image Removed

Package Size is lower than Maximum Number of Errors per Pack as the number of error won't decrease (example in may 2016: 2567 records from DP_PUSL2 to DPDYN22, 17618 records from DPSD001 to DPDYN21  and 530 from DSO_DLV1 to DPDYN21)

Specific table

Two specific table have been created in SM30 to manage following rules

Image Removed

Image Removed

The 2 tables are:

• ZMATPLANT
• ZMATVENDOR

Two customised transaction have been created in SE93:

• ZMAINT_MATPLANT
• ZMAINT_MATVENDOR

"UD connect" connection

Dynasys is a MSSQL tool, BW WBP is on an AIX server. No ODBC driver exists between BW and MSSQL server in Linux / AIX.

This problem was solved setting an UD connect connection

User ID for Dynasys connection is Dynasys_Interface / Password  : 791hB6zi8Rk1DBSV3uNG

Main server:

• Dynasys Production server: WDCCLSLBV01\SLV1_DBPRD
• Dynasys Development server: WDCCLSLBV01\SLV1_DBDEV

Remark: contact for management of UD Connect connection is Adaggio team.

Management of file through APD

Files are created in the following folder in AL11

/exploit/depart/Dynasys

To avoid problem with quotes, routines have been added in APD to encapsulate existing quotes in description fields

Image Removed

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

Weekly: launched on saturday, 9:00 AM

• PC_DPS_DYNASYS_03
  DPS Dynasys: META - W - Weekly Meta-Chain
  Image Removed
• 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
  Image Removed

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.

Image Removed Image Removed

...

• Monthly, the 6th of the month at 3am
• Whole chain last around 10 minutes (07/10/2016)

...

Based on Table EXP_FORE (daily update, by 1.45am)

The SnapShot month (End of Month View/C_FCSTMTH) is automatically set to previous month.

Global filter variable (C_GLBFILT) DPS/PHOTO_MTH can be used to fix another SnapShot month.

Caution : do not launch this chain several times a month without cleaning previous loadings

...

• Daily for the moment at 3.15 am (Target = Every 2 hours from 8am to 6pm)
• Whole chain last arount 15 minutes (17/11/2016)

Based on Table EXP_FORE_DR (daily update, by 1.45am, even if BW loading is monthly))

05/01/2017: On dynasys side, the treatment which prepares table EXP_FORE_DR takes more time, and now finishes around 2.45 (previously 1.45) => BW chain starter changed 2.30 am => 3.15 am

List of GBU deployed in DynaSys, and live modules =>  b. GBU & BU codes, Product Group et Customer Group

Important links

Usage information

Nu mber of users: tbd

Critical period: none

Geographical perimeter: worldwide

InfoArea:

• Demand Planning Scheduling
  IA_DPS
  Image Added

Process chain Display Component:

• 127 - PROJECT - DPS - Demand Planning Scheduling
  COMP_DPS_PC
  Image Added

Roles & Access

Roles and access

See also file maintained by Authorization team : BW Catalog of Roles / link: https://drive.google.com/open?id=10GEfKYqrT1eeTO_uHYAheL1GX7L5y_pvH0KQU64qh5I

Authorization objects

Dataflow presentation

Overview

Functional and Technical rules on Workbench

General presentation

Sales, Deliveries, Stocks, BoM, Recipe...are extracted from several BW application or from SAP directly and stored in DynaSys dedicated DSO, ADSO.

Data are filtered,  reworked, and used to generae flat .csv files through APD or ABAP or Hana Application Process (soon).

Files are moved to DynaSys datahub, and loaded in DynaSys modules (DP or DiP).

Useful file to understand dataflow from APD to source, and check filters applied all along the dataflow: (not up to date)

Image Added

Interface file specifications

All interfaces flat files are documented in specification googlesheet

MasterData => Master Data Process specification

DP (used for DP module) => DP Process specification

DIP-PP (used for DiP-PP module) => DI-PP Process specification

Currency Conversions

All amounts transfered to DynaSys are in Euro (EUR).

Many discussions have been led concerning the exchange rate to use. Finally the exchange rate has been set to CAR4 (active since 2018/07/26)

CAR4 exists only on BW side, It handle begin of month rates.

it is created from exchange rate CAR2 via program ZBW_LOAD_EXCHANGE_RATES_CAR4 (old Z_CREATE_EXCHANGE_RATES_CAR4). The creating is handle via a scheduled process chain Z_TAUX_CARAT.

Image Added

TIP  : To check exchange rate on SAP side, use transaction ZRATE (available on WP1 & PF1)

Interface part

Reporting part

Conversion in KG unit

Image Added

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

The different step of the routine are the following:

Creation of internal table

Creation of internal table between T006and T006D (T006D provide the fields MSSIE, base unit of a dimension DIMID)
Creation of internal table for DSO UOMCMAT2, filled with both conversion from UOM to UNIT and UNIT to UOM and joined with T006 to get Dimension DIMID

Conversion in KG (if possible)

Quantity needs to be converted to KG.

The routine check:

1. if Quantity is already in KG, nothing is done
2. if Quantity is equal to 0, Unit is set to KG
3. if Unit is in dimension MASS (the same dimension as the one for KG), then conversion is done in KG using T006
4. if Unit is not in MASS, we check in UOMCMAT2 if we have a direct conversion from UNIT to KG
5. if no direct conversion exists, we check if there is a conversion from Unit to any MASS unit and after conversion we apply another conversion from MASS to KG using T006

If no conversion exists, Unit remains empty and will be manage as an error (see below)

Catch missing conversion

The flow uses Error DTP. When Unit can't be converted, the routine raise an exception "cx_rsrout_skip_val". The error is loaded in the error queue with text from the message class ZDYN_CONV_ERROR

Not all error will be fixed. Most of these error are linked with BU outside of Dynasys perimeter.

Transformation from ZWPPTDYS ECC table

Documentation

Functional specification are available in the following spreadsheet:

In the following tabs:

Image Added

ECC process

The ZWPPTDYS is loaded on ECC side through the transaction ZWPPTMRPOUT (which load the ZWPPMRPOUT program)

This transaction use the program RMDMRPEXTRACT01 which create a list of material to extract.

Then, for each material, the program RMDMRPEXTRACT01 run through the exit ZCL_PP_IM_MD_SR_LIST_EXTRACT.

This exit reads the database for each material and loads in memory several table among which is table IT_MDPSX.

Then, through specific code, the table ZWPPTDYS is loaded from IT_MDPSX using method IF_EX_MD_SR_LIST_EXTRACT~EXTRACT_SR_LIST_INFOS

BW Process

This table is loaded from WP1 into WBP in the DPDYN02 DSO (Propagation) and then in the DBDYN14 (Propagation).

This table is loaded from PF1 into WBP in the DPDYN05 DSO (Propagation) and then in the DBDYN14 (Propagation).

All rules are available in following transformations :

ODSO DPDYN02 -> ODSO DBDYN14

ODSO DPDYN05 -> ODSO DBDYN14

See short description of this rules below

Begin of global

1. Declaration of types
2. Declaration of table & variable

Begin of routine

1. Declaration of field-symbols
2. Refresh internal table
3. Clear variable
4. Get Source system using class oref_dynasys_utils, method get_source_systems
5. Get Systems extensions using class oref_dynasys_utils, method get_system_extension

Phase 0: Table preparation

Load each required table into hashed table.

Phase 1: DSO Enrichment

Depending on value of field c_delkz:

1. Step 1: Ship/Rec Shipto ID (PARTNER_CUST_ID)
2. Step 2: Ship/Rec plant ID (PARTNER_PLANT_ID)
3. Step 3: Complement ID (COMPL_ID)
4. Step 4a: BU Source
5. Step 4b: BU Destination
6. DOC_TYPE
7. ITEM_CATEG

Remarks:

• Step 1 to 4 depends on result of previous step. No simplication is done in the code.
• If in Step 1, PARTNER_CUST_ID equals source_field-X, in step we will use PARTNER_CUST_ID and not source_field-X
• This means any error in the code will raise error in further rules. This is a choice in all the routine and this logic must be kept.
• For Step 1,2,3, value are loaded without modification in variable ended by*_origin (and later in the script, these value are saved in dedicated infooject to ease debugging)
• Even useless rules are loaded to keep homogeneity in the code, example: loading a field at null even if this field is already null.
• For step 3, a master have been created C_PLNTCON (previously MD C_CUSTASS) to apply a specific Complement ID. This case happen only on flow "Plan consignment" :
  Image Added

Example :

If the PARNET_PLANT_ID is 8254,  normally COMPL_ID  linked to this plant is 61281 (by reading master data C_PLANT).

Image Added

But for this flow, we previously read master data C_CUSTASS to see if this plant is a specific case :

Current values in C_CUSTASS (Update 09/03/2018 manually)

Image Added

Previous values to 09/03/2018

Image Added

And if it's the case, we apply the transcodification => in the example, NDC-66852 replace NDC-61281.

For the moment this master data C_CUSTASS is maintained manually.

Between phase 1 and 2:

Fields are assigned for expert routine (source to result)

System extension is added to field (Material, Plant, Partner plant ID etc) and remove unneeded 0 using function conversion_exit_alpha_output. These new value are stored in dedicated infooject to e used later in Phase 2 of script

A check is done to find any correspondance with content of specific table ZMATPLANT and ZMATVENDOR (see below) :

Two specific table have been created in SM30 to manage following rules

Image Added

Image Added

Two customised transaction have been created in SE93:

• ZMAINT_MATPLANT (maintain table ZMATPLANT)
• ZMAINT_MATVENDOR (maintain table ZMATVENDOR)

Phase 2: Flag determination

Once Phase 1 is finished, depending on DELKZ value, several fields are loaded:

• File flag fields: these flag will be used in APD to dettermine which data needs to be loaded in flat file
• Flowid identify which rule has been applied regarding the specification
• SKU R in FS (C_FLGSRF), filled from PARTNER_CUST_ID / PARTNER_PLANT_ID / COMPL_ID depending on flow id value.

All rules are checked one after the other. Once one check is validated, the check stop

Remarks: c_pfctr2 = BU SOURCE and c_recptbu = BU DESTINATION

Phase 3: DBDYN14 data loading with process chain

DSO DBDYN14 is loaded by 4 DSO "Source" :

Image Added

DSO DPDYN02 & DPDYN05 are loaded in full mode due to modification done on table ZWPPTDYS in ECC systems (adding and deletion lines everyday).

DSO DSO_DLV1 DPSDSO71 & DPSD001 are loaded in delta mode. (DSO_DLV1 Replaced by DPSDSO71 - 15.11.2021)

To not to have to delete data everyday DSO DBDYN14 and reload it from the four sources, we'll use a flag on object C_FLGZWDY (Flag ZWPPTDYS data) wich is equal to 'X' for all data coming from DSO DPDYN02 & DPDYN05.

Program ZBW_DYN001 with variant ZBW_DBDYN14 will be launched everyday (in process chain) before DBDYN14 loading in order to delete data with flag ZWPPTDYS data = 'X'.

After that DTP full will run for DPDYN02 & DPDYN05 and DTP delta for DPSD001 & DSO_DLV1 DPSDSO71. (DSO_DLV1 Replaced by DPSDSO71 - 15.11.2021)

Specific rules on Dynasys dataflow

Nota fiscal 

Plant 7525 is not recognized on Dynasys side, deletion or modification are done on BW side following rules like below :

These rules are generally applied in transformation (by routine) before DSO source of each file.

Interco rule 

For DIP files below, delete line where "Receiving site" = "source site" :

Field with extension C_DYN_***

In Dynasys file exported, fields are generaly with an extension S or R corresponding of source system :

• *R => Rhodia (WP1)
• *S=> Solvay (PF1)

These fields are calculated and created in transformation before to be added in their DSO target.

It's also possible in specific dataflow these fields are directly calculated in APD.

Main fields with extension :

• C_DYN_001 : Plant with System Extension
• C_DYN_003 : Customer with System Extension
• C_DYN_006 : Distribution Channel with System Extension
• C_DYN_005 : Material with System Extension
• C_DYN_008 : Division with System Extension
• C_DYN_025 : Ship-to (including Prospects) with extension

Global variables stored in Global Filter (C_GLBFILT) - DynaSys scope

Image Added

Stream: DPS

Image Added

Refresh workbook to get current WBP variables => DynaSys Global Filters.xlsx

Be careful, it's forbidden to have the same filter value twice for a global filter field (Active = Y only one time).

Reload data :

• If a new line is added in Global filter, all delta data flow have to be reinitialized

See below all DSO wich are to be reload :

1. DBDYN06
2. DPDYN21
3. DPDYN22
4. DBDYN14

Refer to Paragraph Recurring Procedures for detailed process

• Concerning BU, in APD there are BU (Field C_PFCTR2) filters values "hardcoded".Some modifications have to be done to update these filters if necessary.

      => See Dynasys dataflow document (BW Layer = APD / field =*C_PFCTR2) :

https://drive.google.com/file/d/1hsxeQAMi3quJ-rs6aa0tl5neod7oz85lzBr_o8kAQmQ/view

Image Added

Usage of error stack

Error stack are used in relation with Unit and Currency conversion.

Most if not all error are linked with BU outside current perimeter of project and won't be fixed.

Each DTP has the following settings:

DTP

Image Added

Error DTP

Image Added

Image Added

Package Size is lower than Maximum Number of Errors per Pack as the number of error won't decrease (example in may 2016: 2567 records from DP_PUSL2 to DPDYN22, 17618 records from DPSD001 to DPDYN21 and 530 from DSO_DLV1 DPSDSO71 to DPDYN21. (DSO_DLV1 Replaced by DPSDSO71 - 15.11.2021)

Connection with UD CONNECT

Dynasys is a MSSQL tool, BW WBP is on an AIX server. No ODBC driver exists between BW and MSSQL server in Linux / AIX.

This problem was solved setting an UD connect connection

Main servers:

• Dynasys Production server: WDCCLSLBV01\SLV1_DBPRD  => connected to WBP
• Dynasys Development server: WDCCLSLBV01\SLV1_DBDEV => connected to WBD
• Dynasys Testing server: WDCCLSLVBV01\SLV1_DBTST => connected to WBQ
  
• Dynasys Testing server: WDCCLSLVBV01\SLV1_DBTST => connected to WBV

Important:

• Adagio Team is in charge of UD Connect connexions. Admin Change to be created by Guillaume T for any change or issue.
• Wintel Operations is in charge of DynaSys servers (Contact Abdelmôti KHABABA)

Management of file through APD (or ABAP)

Files storage (physical/logical)

All files are created in the folder /exploit/depart/Dynasys/MASTER or PART1 or PART2 (can be shown via transaction AL11)

Logical path is used (transaction FILE) : one by directory used

 Image Added

Detail for Logical path MASTER (similar for others)

Image Added

Logical file is used (transaction FILE) : one by .csv file

Image Added

Detail for Logical file Z_BW_DYNASYS_ALLSHIP_TO (similar for other .csv files)

=> put the .csv file name wanted

=> put the Logical path in which the .csv file has to be generated

Image Added

Special Format in files (negative sign, number of decimal...)

Interface between BW and DynaSys

Documentation about Dynasys process and Interface here.

Specificities for Composite Material - AERO

GBU CM has been deploied on WP1 and WBP in january 2020 (golive). The project is called Solstice.

Few major enhancements has been done for AERO :

• new key axis Specification List

C_SPECLIS / Specification List (Max 15) / CHAR 130

On WP1 side, none, one or several specifications are managed on Sales order item, tab 'Additional data B'

Example WP1 Sales Order 0002994889

Image Added

Stored in a specific table ZWOCT435 on WP1

Image Added

Store in C_ITM_SD on WBP side (part of Global Sales steam), concatenated separated by a '|'

Image Added

This axis has been added as key in several interface files. General file documentation is updated.

• new material classification Z_CM_MAT for AERO 

Example Material WP1 166422

Image Added

Stored on C_MATCLS on BW side

• lots of different material units (L, M2, GAL...) 

Lots of different Material Base UOMs, and Sales Units, most of them not mass ones

Image Added

ADSO ABDPDY52 is containing conversion factors to KG.

Most of the efforts to get conversion factor is done here

Image Added

In other files, containing quantities in KG if rule in place does not get a KG conversion, the KG conversion is read in ADSO ABDPDY52 

=> Class : ZBW_DPS_DYNASYS_UTILS + Method : GET_MATERIAL_CONVERSION_FACTOR / Get material conversion from DBDYN02

Data loadings

Loading frequency

Daily: launched by the RSP_DAILY process chain around 6am every day from Monday to Friday

• PC_DPS_DYNASYS_01 / DPS DynaSys META Part1 - D - Daily Meta-Chain Part 1
  Image Added
• PC_DPS_DYNASYS_25 / DPS DynaSys META Part2 - D - Daily Meta-Chain Part 2

         Image Added

Weekly: launched on saturdays at fixed hour 9am

• PC_DPS_DYNASYS_03 / DPS Dynasys: META - W - Weekly Meta-Chain
  Image Added

Remark: DynaSys tool is waiting for files between 6am and 5pm

Flag end of file generation

Files are splitted into 3 groups : MASTER DATA, PART1, PART2, at the end of each group file generation a flag file is generated (used to start automatique import on DynaSys side)

BW_MASTER_COMPLETE

BW_DYN_PART1_COMPLET

BW_DYN_PART2_COMPLETE

Image Added

Files transfert

After flag file generation, an ABAP step has been added to transfert files from BW to DynaSys via webmethod

ABAP = ZCA_MFT_CALL_RFC

with 3 variants : DYNASYS_MASTER / DYNASYS_PART1 / DYNASYS_PART2

Image Added

Image Added

Archive files cleaning

Flat files are archived at each run in repository /Exploit/BW/archive/DYNASYS during abap ZCA_MFT_CALL_RFC execution

A filesystem cleanup procedure is managed by Adaio based on the File_Retention_Rules file (File maintained by Adagio team)

Rule in place : clean DynaSys files older than 1 month in all BW systems (WBD, WBQ, WBP).

For any change, email Adagio team

Average performance

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

Exception:

• DPDYN21: 6,4 M lines loaded in delta mode (init)
• DPDYN22: 2,2 M lines loaded in delta mode (init)
• DBDYN06 : 150 000 lines loaded in delta mode (init)
• DBDYN14 (only from DPSD001 / DSO_DLV1 DPSDSO71) : 5 M lines loaded in delta mode (init)  -  (DSO_DLV1 Replaced by DPSDSO71 - 15.11.2021)
  
  

NB : Statistics dating March, 2017.

Average duration (March 2017):

• Daily chain usually run for approximately 1,5 hour 
• Weekly chain usually run for 40 minutes  to 1,5 hour (= Daily Run + Material data flow loading and Material.csv file generation)

Remark : On going evolution will change Daily run to take into account the various dependences of DSO source wich are out of Dynasys perimeter (Deliveries, Sales order, Stock...).

Process will be cut in various process : DI-PP / DP / Master data & Reporting. (See part Planned evolution)

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.

It involves that the volume of data loaded increase during the year, until arrived at its maximum at the end of december.

Reporting

Queries Documentation or user guide

No dedicated documentation on queries

Reporting Specification here.

Main queries

Main functionnalities

n/a

Broadcast

n/a

Maintenance

Known bugs

ShipTo missing in file ShipTo.csv

In end routine DPDYN22 => DBDYN31 & DBDYN18 => DBDYN31, only ShipTo with a filled country is loaded in target.

Image Added

To fix the issue, follow the steps bellow :

1. Check if country is correctly filled in C_CUSTOMR master data for missing ShipTo.
2. If not filled, reload this ShipTo from ECC source system.
3. Check if country is filled
4. Delete data in DSO DBDYN31 and reload it from DPDYN22 and DBDYN18.
5. Generate file ShipTo.csv, the ShipTo would be appear.

Customer Sales empty or inexact (C_CUSTSAL or 0CUST_SALES)

Due to loading routine in the propagation level of DPSDSO05 / DSO_SD02 DPSDSO45 which are loaded in delta mode, this field is not correctly updated. (DSO_SD02 Replaced by DPSDSO45 - 15.11.2021)

Image Added  

Customer Sales attributes empty or inexact (0CUST_SALES & C_CUSTSAL)

Correction done for 0CUST_SALES (see below), the same dataflow must be done for C_CUSTSAL Master data.

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

 Image Added

A specific extractor has been created based on KNVP table from WP1_400 in order to feed ZZ fields correctly.

Image Added

This data loading is done everyday with the process chain ZPC_MD_ATTR_RCS.

After that we have to retreat data stored in DSO DPDYN22 to update ZI PArtner only if we have a modification. To do that a new transformation has been created :

Image Added

A new DTP has been created too, launching it ZI partner is reading into master data 0CUST_SALES and updated in DPDYN22.

This DTP is in daily and weekly Dynasys process chain :

• PC_DPS_DYNASYS_08

• PC_DPS_DYNASYS_12

Repository /EXPLOIT in AL11 is full (Dump => Error when calculating position for open file)

If you have the following DUMP when you execute an APD :

Image Added

It means the repository where the file generated will be stored is full (/EXPLOIT).

In September 2016, ADAGIO Team added 50GB on WBP server : wbpsapr3.ibm.be.solvay.com 

If the issue appears again please contact ADAGIO Team.

File DYS_BW_PROD_HIST.csv - Ressource not filled for RCS Material/Plant

The field is linked to the process order and comes from WP1 table AUFK field ZZMDV01 (Production line)

Check the Production Version via transaction C223 is filled.

If not filled, ask 'Agent d'Ordonnancement' to update.

The value stored in table MKAL is then copied at process order level (table AUFK).

To be check if update will impact existing process orders and associated material movement or will be taken into account only for new flow

Image Added

Issue encouraged 2019/03/26 for Material 76010 / Plant 7525 => value Production Line 'AENSACAG' was missing

Maintenance

Recurring procedure

Asking an update on lists of flat files to be transfered to DynaSys server (Obsolete since 21st of June 2021)

Lists are not used anymore, a cleaning has been asked to Adagio

The lists are stored in AL11 directory /exploit/TA/programs/env

• BW_DYN_PART1_COMPLETE.filelist
• BW_DYN_PART2_COMPLETE.filelist
• BW_MASTER_COMPLETE.filelist
  
  

For info BW_DYN_COMPLETE.filelist is obsole and you have been removed from all systems.

If a flat file name need to added or removed, send a email to IS-Adagio-SAP-Operations@solvay.com

NB : Adagio does the modification on a separated server which is replicated every hours. You have to wait to see modification.

Example of message :

Image Added Image Added

Adding a plant to DynaSys scope

CAUTION : all delta loading are impacted 

Step1 ) Check the daily DynaSys chain (PC_DPS_DYNASYS_01) is finished via ST13

Image Added

Step2) Add a new line in Global Filter (C_GLBFILT) for Stream DPS / Rule PLANT

/!\  check requested Plants are not already in DynaSys scope, dupplicates records would make daily chain fails

Please indicates in the description the date and user code to track changes

Image Added

/! \  Each Rule has 999 lines (Counter), if all the counter are taken for the Rule "PLANT", it will be necessary to increment the rule "PLANT" and create a new one => Example: PLANT2 or PLANT3 etc.

Make sure there are no more counter available before creating a new Rule.

Rule PLANT is full, use PLANT2

Step3) Delete whole contain of following DSOs:

Reason : part of the loading is via DELTA mode

• • DPDYN21 / DYN - Sales Deliveries
  • DPDYN22 / DYN - Sales Orders
  • DBDYN14 / DYN - MRP Element

Step4) Launch the Process Chain PC_DPS_DYNASYS_12 (around 30 minutes).

For info, list of Plant (update of 20190412)

Adding an ERP BU to DynaSys scope

Same procedure than 'Adding a plant to DynaSys scope' but with Rule C_PFCTR2

Please indicates in the description the date and user code to track changes

Image Added

Adding a BFC BU to DynaSys scope

Step1) Check the daily DynaSys chain (PC_DPS_DYNASYS_01) is finished via ST13

Image Added

Step2) Add a new line in Global Filter (C_GLBFILT) for Stream DPS / Rule CPFCTR2_2

Please indicates in the description the date and user code to track changes

Image Added

Step3) No more action requiered as BFC BU filter is only used for DSOs loaded via FULL process 

Mass update of Global Filter (Plant / BFC BU / ERP BU ... )  via Flat file 

Step1) Check the daily DynaSys chain (PC_DPS_DYNASYS_01) is finished via ST13

Image Added

Step 2) 

Reload the IP of the global Filter with a csv file (Cf Flat file model below) + Run the DTP of the Global filter

Image Added

Global Filter flat file template:

C_GLBFLIT_YYYYMMDD.csv

Below is an example of the contents of the flat file:

Image Added

NB : The above procedure is to be carried out first in a development / quality environment and if the tests are OK, apply this in production.

If you use an existing key: "STREAM / RULE / C_GLBFILT (Counter)", then the record will be updated with the new information.

/! \  Each Rule has 999 lines (Counter), if all the counter are taken for the Rule "PLANT", it will be necessary to increment the rule "PLANT" and create a new one => Example: PLANT2 or PLANT3 etc.

Make sure there are no more counter available before creating a new Rule.

For BFC BU no more action is required. 
For Plant or ERP BU , apply step 3 and 4 below.

Step3) Delete whole contain of following DSOs:

Reason : part of the loading is via DELTA mode

• • DPDYN21 / DYN - Sales Deliveries
  • DPDYN22 / DYN - Sales Orders
  • DBDYN14 / DYN - MRP Element

Step4) Launch the Process Chain PC_DPS_DYNASYS_12 (around 3-4h).

Adding an extra currency to Exchange Rates flat file (DYS_BW_CURR)

Exchange rates are send daily to DynaSys via flat file DYS_BW_CURR.csv.

There are limited to Exchange Rate types CAR4, and several currencies (ZAR, VEF, USD, TWD...). For all, conversion to EUR only.

It is possible to add currency to the current list (From currency / FCURR).

Step1) in WBD : modify 'DTP DAFICE01 -> DBDYN10 - Full limited' / DTP_AKLI1L2RFKV5X4Z6KR11T14Y4

Step2) transport till WBP.

Image Added

CAUTION  : It is not possible to change Exchange Rate Type (KURST) or To-currency (TCURR) without impact on the loading flow, and file generation.

Adding/Changing a customer for Consignation Plant (C_PLNTCON)

Step1) Check the daily DynaSys chain (PC_DPS_DYNASYS_01) is finished via ST13

Image Added

Step2) Update C_PLNTCON / Plant for Consignation (Receiving Plant from Delivery)

a) if few values have to be modified, use transaction RSD1, add or modify lines for C_PLNTCON / Plant for Consignation (Receiving Plant from Delivery)

In case of modification, do not forget to launch Change Log.

b) if several values, you can use update by flat file. Format is :

0LOGSYS; C_PLNTCON;C_PARTCUS;C_SHIPTOF
WP1_400;8063;2016260;57295
WP1_400;8039;2013950;57300
WP1_400;8171;2031655;57641

Step3) Delete whole contain of following DSOs

Reason : part of the loading is via DELTA mode

• • DBDYN14 / DYN - MRP Element

Step4) Launch the Process Chain PC_DPS_DYNASYS_12 (around 3-4h).

Adding/Changing a material group exclusion for actuals files (C_GBLFILT).

 On Solvay flow to DBDYN06 / DYN - Actual Prod we were facing many unit conversion issues even if material were Z700 type.

These materials were not relevant for DynaSys process, so we now exclude several Material Group.

The exclusion list can be enhanced or modified changing G_GLBFILT DPS/C_MAT_GRP

caution : it is mandatory to put 'SOLVAY' in high field. Value is checked in transformation

Image Added

Steps after System landscape modification

When a system change name or mandant, when a new system is created, check variables in Global Filter (C_GLBFILT)

Variables managed for DPS :

Variables DPS/WBD... where put in place before LANDSCAPE/SOLVAY, so there are still used in DynaSys (It would be good to change it to make maintenance easier)

Image Added

Common variables (used by DPS also) :

Image Added

Adding a Material Type to DynaSys scope

CAUTION : all delta loading are impacted

Step1

• Get the list of Material from MARA table with the new Material Type to added
• Filter with this material list the VBAP table to get the associated Item Category

          Image Added

Step2) Check the daily DynaSys chain (PC_DPS_DYNASYS_01) is finished via ST13

Image Added

Step3) Add a new line in Global Filter (C_GLBFILT) for Stream DPS / Rule MATL_TYPE

Please indicates in the description the date and user code to track changes

Image Added

Step4) Delete whole contain of following DSOs:

Reason : part of the loading is via DELTA mode

• • DPDYN21 / DYN - Sales Deliveries
  • DPDYN22 / DYN - Sales Orders
  • DBDYN14 / DYN - MRP Element

Step5) Launch the Process Chain PC_DPS_DYNASYS_12 (around 1h).

Adding an item category (Sales Documents) to DynaSys scope

CAUTION : all delta loading are impacted 

Step1) Check the daily DynaSys chain (PC_DPS_DYNASYS_01) is finished via ST13

Image Added

Step2) Add a new line in Global Filter (C_GLBFILT) for Stream DPS / Rule ITEM_CATEG

Please indicates in the description the date and user code to track changes

Image Added

Step3) Delete whole contain of following DSOs:

Reason : part of the loading is via DELTA mode

• • DPDYN21 / DYN - Sales Deliveries
  • DPDYN22 / DYN - Sales Orders
  • DBDYN14 / DYN - MRP Element

Step4) Launch the Process Chain PC_DPS_DYNASYS_12 (around 3-4h).

Ask to connect file transfert from WBQ to DynaSys Test

WBQ is NOT connected to DynaSys Test for file transfer as there is only one Webmethod Test for QUAL and PRE-PROD

If you temporarly need to change contact <support.xml@solvay.com>

Don't forget to ask them to put it back when you have finished with WBQ

Planned Evolution

Several minor evolution managed by the Dynasis project team.

Process chain planning : Take into account various dependences of DSO Source wich are out of DYnasys perimeter (Deliveries, sales order, Stock...)

See the  New Dynasys dataflow to implement here.

Field C_PFCTR2 in master data C_MATPNT2

Originaly, there was a filter on field C_PFCTR2 in DTP linked to transformation between master data C_MATPNT2 and DSO DBDYN08 :

Image Added

Filter value applied was OLAP variable V_0G_CWWE03_0001.

But the issue is that field C_PFCTR2 is not filled for source system PF1.

When we applied the filter, only data from source system WP1 was loaded in DSO DBDYN08.

To fix the issue, filter value was deleted and a start routine was added in transformation.

In this one, we read the master data C_MATPNT3 to keep C_PFCTR2 value with key Plant & Material.

If an evolution is done to fill C_PFCTR2 value for PF1 System in C_MATPNT2 master data, start routine could be deleted and filter value in DTP will be applied again.

General presentation

Objective of the application

BW Demand Planning Scheduling (DPS)

Image Added

Tool Leader: Olivier Descamps

IT leader of the application: Laure Pichot-Plasse (DynaSys), Craig Wanamaker (BW)

Name of project: Dynasys

PMO Project: 6046 S&OP with Dynasys - Core model and pilot

UR: UR335513 DYNASYS Sales Forecast / UR333365 DYNASYS Demand Planning

Reporting Coordinator: PAIVA Diogoa <diogo.paiva@solvay.com>

Important links

Usage information

Nu mber of users: tbd

Critical period: none

Geographical perimeter: worldwide

InfoArea:

• Demand Planning Scheduling
  IA_DPS
  Image Added

Process chain Display Component:

• 127 - PROJECT - DPS - Demand Planning Scheduling
  COMP_DPS_PC
  Image Added

Roles & Access

Roles and access

See also file maintained by Authorization team : BW Catalog of Roles / link: https://drive.google.com/open?id=10GEfKYqrT1eeTO_uHYAheL1GX7L5y_pvH0KQU64qh5I

Authorization objects

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.

All interfaces flat files are documented in specification googlesheet

MasterData => Master Data Process specification

DP (used for DP module) => DP Process specification

DIP-PP (used for DiP-PP module) => DI-PP Process specification

Useful file to understand dataflow from APD to source, and check filters applied all along the dataflow: (not up to date)

Image Added

Currency Conversions

All amounts transfered to DynaSys are in Euro (EUR).

Many discussions have been led concerning the exchange rate to use. Finally the exchange rate has been set to CAR4 (active since 2018/07/26)

CAR4 exists only on BW side, It handle begin of month rates.

it is created from exchange rate CAR2 via program ZBW_LOAD_EXCHANGE_RATES_CAR4 (old Z_CREATE_EXCHANGE_RATES_CAR4). The creating is handle via a scheduled process chain Z_TAUX_CARAT.

Image Added

TIP  : To check exchange rate on SAP side, use transaction ZRATE (available on WP1 & PF1)

Interface part

Reporting part

Conversion in KG unit

Image Added

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

The different step of the routine are the following:

Creation of internal table

Creation of internal table between T006and T006D (T006D provide the fields MSSIE, base unit of a dimension DIMID)
Creation of internal table for DSO UOMCMAT2, filled with both conversion from UOM to UNIT and UNIT to UOM and joined with T006 to get Dimension DIMID

Conversion in KG (if possible)

Quantity needs to be converted to KG.

The routine check:

1. if Quantity is already in KG, nothing is done
2. if Quantity is equal to 0, Unit is set to KG
3. if Unit is in dimension MASS (the same dimension as the one for KG), then conversion is done in KG using T006
4. if Unit is not in MASS, we check in UOMCMAT2 if we have a direct conversion from UNIT to KG
5. if no direct conversion exists, we check if there is a conversion from Unit to any MASS unit and after conversion we apply another conversion from MASS to KG using T006

If no conversion exists, Unit remains empty and will be manage as an error (see below)

Catch missing conversion

The flow uses Error DTP. When Unit can't be converted, the routine raise an exception "cx_rsrout_skip_val". The error is loaded in the error queue with text from the message class ZDYN_CONV_ERROR

Not all error will be fixed. Most of these error are linked with BU outside of Dynasys perimeter.

Transformation from ZWPPTDYS ECC table

Documentation

Functional specification are available in the following spreadsheet:

In the following tabs:

Image Added

ECC process

The ZWPPTDYS is loaded on ECC side through the transaction ZWPPTMRPOUT (which load the ZWPPMRPOUT program)

This transaction use the program RMDMRPEXTRACT01 which create a list of material to extract.

Then, for each material, the program RMDMRPEXTRACT01 run through the exit ZCL_PP_IM_MD_SR_LIST_EXTRACT.

This exit reads the database for each material and loads in memory several table among which is table IT_MDPSX.

Then, through specific code, the table ZWPPTDYS is loaded from IT_MDPSX using method IF_EX_MD_SR_LIST_EXTRACT~EXTRACT_SR_LIST_INFOS

BW Process

This table is loaded from WP1 into WBP in the DPDYN02 DSO (Propagation) and then in the DBDYN14 (Propagation).

This table is loaded from PF1 into WBP in the DPDYN05 DSO (Propagation) and then in the DBDYN14 (Propagation).

All rules are available in following transformations :

ODSO DPDYN02 -> ODSO DBDYN14

ODSO DPDYN05 -> ODSO DBDYN14

See short description of this rules below

Begin of global

1. Declaration of types
2. Declaration of table & variable

Begin of routine

1. Declaration of field-symbols
2. Refresh internal table
3. Clear variable
4. Get Source system using class oref_dynasys_utils, method get_source_systems
5. Get Systems extensions using class oref_dynasys_utils, method get_system_extension

Phase 0: Table preparation

Load each required table into hashed table.

Phase 1: DSO Enrichment

Depending on value of field c_delkz:

1. Step 1: Ship/Rec Shipto ID (PARTNER_CUST_ID)
2. Step 2: Ship/Rec plant ID (PARTNER_PLANT_ID)
3. Step 3: Complement ID (COMPL_ID)
4. Step 4a: BU Source
5. Step 4b: BU Destination
6. DOC_TYPE
7. ITEM_CATEG

Remarks:

• Step 1 to 4 depends on result of previous step. No simplication is done in the code.
• If in Step 1, PARTNER_CUST_ID equals source_field-X, in step we will use PARTNER_CUST_ID and not source_field-X
• This means any error in the code will raise error in further rules. This is a choice in all the routine and this logic must be kept.
• For Step 1,2,3, value are loaded without modification in variable ended by*_origin (and later in the script, these value are saved in dedicated infooject to ease debugging)
• Even useless rules are loaded to keep homogeneity in the code, example: loading a field at null even if this field is already null.
• For step 3, a master have been created C_PLNTCON (previously MD C_CUSTASS) to apply a specific Complement ID. This case happen only on flow "Plan consignment" :
  Image Added

Example :

If the PARNET_PLANT_ID is 8254,  normally COMPL_ID  linked to this plant is 61281 (by reading master data C_PLANT).

Image Added

But for this flow, we previously read master data C_CUSTASS to see if this plant is a specific case :

Current values in C_CUSTASS (Update 09/03/2018 manually)

Image Added

Previous values to 09/03/2018

Image Added

And if it's the case, we apply the transcodification => in the example, NDC-66852 replace NDC-61281.

For the moment this master data C_CUSTASS is maintained manually.

Between phase 1 and 2:

Fields are assigned for expert routine (source to result)

System extension is added to field (Material, Plant, Partner plant ID etc) and remove unneeded 0 using function conversion_exit_alpha_output. These new value are stored in dedicated infooject to e used later in Phase 2 of script

A check is done to find any correspondance with content of specific table ZMATPLANT and ZMATVENDOR (see below) :

Two specific table have been created in SM30 to manage following rules

Image Added

Image Added

Two customised transaction have been created in SE93:

• ZMAINT_MATPLANT (maintain table ZMATPLANT)
• ZMAINT_MATVENDOR (maintain table ZMATVENDOR)

Phase 2: Flag determination

Once Phase 1 is finished, depending on DELKZ value, several fields are loaded:

• File flag fields: these flag will be used in APD to dettermine which data needs to be loaded in flat file
• Flowid identify which rule has been applied regarding the specification
• SKU R in FS (C_FLGSRF), filled from PARTNER_CUST_ID / PARTNER_PLANT_ID / COMPL_ID depending on flow id value.

All rules are checked one after the other. Once one check is validated, the check stop

Remarks: c_pfctr2 = BU SOURCE and c_recptbu = BU DESTINATION

Phase 3: DBDYN14 data loading with process chain

DSO DBDYN14 is loaded by 4 DSO "Source" :

Image Added

DSO DPDYN02 & DPDYN05 are loaded in full mode due to modification done on table ZWPPTDYS in ECC systems (adding and deletion lines everyday).

DSO DSO_DLV1 DPSDSO71 & DPSD001 are loaded in delta mode. (DSO_DLV1 Replaced by DPSDSO71 - 15.11.2021)

To not to have to delete data everyday DSO DBDYN14 and reload it from the four sources, we'll use a flag on object C_FLGZWDY (Flag ZWPPTDYS data) wich is equal to 'X' for all data coming from DSO DPDYN02 & DPDYN05.

Program ZBW_DYN001 with variant ZBW_DBDYN14 will be launched everyday (in process chain) before DBDYN14 loading in order to delete data with flag ZWPPTDYS data = 'X'.

After that DTP full will run for DPDYN02 & DPDYN05 and DTP delta for DPSD001 & DSO_DLV1 DPSDSO71. (DSO_DLV1 Replaced by DPSDSO71 - 15.11.2021)

Specific rules on Dynasys dataflow

Nota fiscal 

Plant 7525 is not recognized on Dynasys side, deletion or modification are done on BW side following rules like below :

These rules are generally applied in transformation (by routine) before DSO source of each file.

Interco rule 

For DIP files below, delete line where "Receiving site" = "source site" :

Field with extension C_DYN_***

In Dynasys file exported, fields are generaly with an extension S or R corresponding of source system :

• *R => Rhodia (WP1)
• *S=> Solvay (PF1)

These fields are calculated and created in transformation before to be added in their DSO target.

It's also possible in specific dataflow these fields are directly calculated in APD.

Main fields with extension :

• C_DYN_001 : Plant with System Extension
• C_DYN_003 : Customer with System Extension
• C_DYN_006 : Distribution Channel with System Extension
• C_DYN_005 : Material with System Extension
• C_DYN_008 : Division with System Extension
• C_DYN_025 : Ship-to (including Prospects) with extension

Use of the Global Filter (C_GLBFILT)

Image Added

Stream: DPS

Image Added

Main filter : C_PFCTR2 (BU) and  PLANT

These 2 filter may be extended regularly due to the extension of Dynasys perimeter (RCS in january 2016, Soda in june 2016)

Other filters: C_MGN_ACC, DEL_TYPE, ITEM_CATEG, MATL_TYPE, REASON_REJ, REC_TYPE

Be careful, it's forbidden to have the same filter value twice for a global filter field (Active = Y only one time).

Reload data :

• If a new line is added in Global filter, all delta data flow have to be reinitialized

See below all DSO wich are to be reload :

1. DBDYN06
2. DPDYN21
3. DPDYN22
4. DBDYN14

Refer to Paragraph Recurring Procedures for detailed process

• Concerning BU, in APD there are BU (Field C_PFCTR2) filters values "hardcoded".Some modifications have to be done to update these filters if necessary.

      => See Dynasys dataflow document (BW Layer = APD / field =*C_PFCTR2) :

https://drive.google.com/file/d/1hsxeQAMi3quJ-rs6aa0tl5neod7oz85lzBr_o8kAQmQ/view

Image Added

Usage of error stack

Error stack are used in relation with Unit and Currency conversion.

Most if not all error are linked with BU outside current perimeter of project and won't be fixed.

Each DTP has the following settings:

DTP

Image Added

Error DTP

Image Added

Image Added

Package Size is lower than Maximum Number of Errors per Pack as the number of error won't decrease (example in may 2016: 2567 records from DP_PUSL2 to DPDYN22, 17618 records from DPSD001 to DPDYN21  and 530 from DSO_DLV1 DPSDSO71 to DPDYN21) 

(DSO_DLV1 Replaced by DPSDSO71 - 15.11.2021)

Connection with UD CONNECT

Dynasys is a MSSQL tool, BW WBP is on an AIX server. No ODBC driver exists between BW and MSSQL server in Linux / AIX.

This problem was solved setting an UD connect connection

Main servers:

• Dynasys Production server: WDCCLSLBV01\SLV1_DBPRD  => connected to WBP
• Dynasys Development server: WDCCLSLBV01\SLV1_DBDEV => connected to WBD
• Dynasys Testing server: WDCCLSLVBV01\SLV1_DBTST => connected to WBQ
  

Important:

• Adagio Team is in charge of UD Connect connexions. Admin Change to be created by Guillaume T for any change or issue.
• Wintel Operations is in charge of DynaSys servers (Contact Abdelmôti KHABABA)

Management of file through APD

Files are created in the following folder in AL11 :

• /exploit/depart/Dynasys

An archive is created everyday with generated file in following folder :

• /exploit/BW/archive/DYNASYS

Special Format

Interface between BW and DynaSys

Documentation about Dynasys process and Interface here.

Specificities for Composite Material - AERO

GBU CM has been deploied on WP1 and WBP in january 2020 (golive). The project is called Solstice.

Few major enhancements has been done for AERO :

• new key axis Specification List

C_SPECLIS / Specification List (Max 15) / CHAR 130

On WP1 side, none, one or several specifications are managed on Sales order item, tab 'Additional data B'

Example WP1 Sales Order 0002994889

Image Added

Stored in a specific table ZWOCT435 on WP1

Image Added

Store in C_ITM_SD on WBP side (part of Global Sales steam), concatenated separated by a '|'

Image Added

This axis has been added as key in several interface files. General file documentation is updated.

• new material classification Z_CM_MAT for AERO 

Example Material WP1 166422

Image Added

Stored on C_MATCLS on BW side

• lots of different material units (L, M2, GAL...) 

Lots of different Material Base UOMs, and Sales Units, most of them not mass ones

Image Added

ADSO ABDPDY52 is containing conversion factors to KG.

Most of the efforts to get conversion factor is done here

Image Added

In other files, containing quantities in KG if rule in place does not get a KG conversion, the KG conversion is read in ADSO ABDPDY52 

=> Class : ZBW_DPS_DYNASYS_UTILS + Method : GET_MATERIAL_CONVERSION_FACTOR / Get material conversion from DBDYN02

Data loadings

Loading frequency

Daily: launched by the RSP_DAILY process chain around 6am every day from Monday to Friday

• PC_DPS_DYNASYS_01 / DPS DynaSys META Part1 - D - Daily Meta-Chain Part 1
  Image Added
• PC_DPS_DYNASYS_25 / DPS DynaSys META Part2 - D - Daily Meta-Chain Part 2

         Image Added

Weekly: launched on saturdays at fixed hour 9am

• PC_DPS_DYNASYS_03 / DPS Dynasys: META - W - Weekly Meta-Chain
  Image Added

Remark: DynaSys tool is waiting for files between 6am and 5pm

Flag end of file generation

Files are splitted into 3 groups : MASTER DATA, PART1, PART2, at the end of each group file generation a flag file is generated (used to start automatique import on DynaSys side)

BW_MASTER_COMPLETE

BW_DYN_PART1_COMPLET

BW_DYN_PART2_COMPLETE

Image Added

Files transfert

After flag file generation, an ABAP step has been added to transfert files from BW to DynaSys via webmethod

ABAP = ZCA_MFT_CALL_RFC

with 3 variants : DYNASYS_MASTER / DYNASYS_PART1 / DYNASYS_PART2

Image Added

Image Added

Archive files cleaning

Flat files are archived at each run in repository /Exploit/BW/archive/DYNASYS during abap ZCA_MFT_CALL_RFC execution

A filesystem cleanup procedure is managed by Adaio based on the File_Retention_Rules file (File maintained by Adagio team)

Rule in place : clean DynaSys files older than 1 month in all BW systems (WBD, WBQ, WBP).

For any change, email Adagio team

Average performance

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

Exception:

• DPDYN21: 6,4 M lines loaded in delta mode (init)
• DPDYN22: 2,2 M lines loaded in delta mode (init)
• DBDYN06 : 150 000 lines loaded in delta mode (init)
• DBDYN14 (only from DPSD001 / DSO_DLV1 DPSDSO71) : 5 M lines loaded in delta mode (init) - (DSO_DLV1 Replaced by DPSDSO71 - 15.11.2021)
  
  

NB : Statistics dating March, 2017.

Average duration (March 2017):

• Daily chain usually run for approximately 1,5 hour 
• Weekly chain usually run for 40 minutes  to 1,5 hour (= Daily Run + Material data flow loading and Material.csv file generation)

Remark : On going evolution will change Daily run to take into account the various dependences of DSO source wich are out of Dynasys perimeter (Deliveries, Sales order, Stock...).

Process will be cut in various process : DI-PP / DP / Master data & Reporting. (See part Planned evolution)

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.

It involves that the volume of data loaded increase during the year, until arrived at its maximum at the end of december.

Reporting

Queries Documentation or user guide

No dedicated documentation on queries

Reporting Specification here.

Main queries

Main functionnalities

n/a

Broadcast

n/a

Maintenance

Known bugs

ShipTo missing in file ShipTo.csv

In end routine DPDYN22 => DBDYN31 & DBDYN18 => DBDYN31, only ShipTo with a filled country is loaded in target.

Image Added

To fix the issue, follow the steps bellow :

1. Check if country is correctly filled in C_CUSTOMR master data for missing ShipTo.
2. If not filled, reload this ShipTo from ECC source system.
3. Check if country is filled
4. Delete data in DSO DBDYN31 and reload it from DPDYN22 and DBDYN18.
5. Generate file ShipTo.csv, the ShipTo would be appear.

Customer Sales empty or inexact (C_CUSTSAL or 0CUST_SALES)

Due to loading routine in the propagation level of DPSDSO05 / DSO_SD02 DPSDSO45 which are loaded in delta mode, this field is not correctly updated. (DSO_SD02 Replaced by DPSDSO45 - 15.11.2021)

Image Added  

Customer Sales attributes empty or inexact (0CUST_SALES & C_CUSTSAL)

Correction done for 0CUST_SALES (see below), the same dataflow must be done for C_CUSTSAL Master data.

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

 Image Added

A specific extractor has been created based on KNVP table from WP1_400 in order to feed ZZ fields correctly.

Image Added

This data loading is done everyday with the process chain ZPC_MD_ATTR_RCS.

After that we have to retreat data stored in DSO DPDYN22 to update ZI PArtner only if we have a modification. To do that a new transformation has been created :

Image Added

A new DTP has been created too, launching it ZI partner is reading into master data 0CUST_SALES and updated in DPDYN22.

This DTP is in daily and weekly Dynasys process chain :

• PC_DPS_DYNASYS_08

• PC_DPS_DYNASYS_12

Repository /EXPLOIT in AL11 is full (Dump => Error when calculating position for open file)

If you have the following DUMP when you execute an APD :

Image Added

It means the repository where the file generated will be stored is full (/EXPLOIT).

In September 2016, ADAGIO Team added 50GB on WBP server : wbpsapr3.ibm.be.solvay.com 

If the issue appears again please contact ADAGIO Team.

File DYS_BW_PROD_HIST.csv - Ressource not filled for RCS Material/Plant

The field is linked to the process order and comes from WP1 table AUFK field ZZMDV01 (Production line)

Check the Production Version via transaction C223 is filled.

If not filled, ask 'Agent d'Ordonnancement' to update.

The value stored in table MKAL is then copied at process order level (table AUFK).

To be check if update will impact existing process orders and associated material movement or will be taken into account only for new flow

Image Added

Issue encouraged 2019/03/26 for Material 76010 / Plant 7525 => value Production Line 'AENSACAG' was missing

Interface Flat files are generated but not archived or not received by DynaSys

https://wiki.solvay.com/x/HICOEw => known issues

BOM missing on DYS_BW_BOM.csv

The list of BOM loaded into Dynasys used filters and especially attributes from C_MATPNT3. It's possible that the BOM was loaded from the transactional flow and the master data C_MATPNT3 was not yet updated especially during the end frozen period. In this case the data in both ADSO APPPBO01 & APPPBO02 have to deleted and reloaded from Acquisition Layer ADSOs.

Maintenance

Recurring procedure

Asking an update on lists of flat files to be transfered to DynaSys server (Obsolete since 21st of June 2021)

Lists are not used anymore, a cleaning has been asked to Adagio

The lists are stored in AL11 directory /exploit/TA/programs/env

• BW_DYN_PART1_COMPLETE.filelist
• BW_DYN_PART2_COMPLETE.filelist
• BW_MASTER_COMPLETE.filelist
  
  

For info BW_DYN_COMPLETE.filelist is obsole and you have been removed from all systems.

If a flat file name need to added or removed, send a email to IS-Adagio-SAP-Operations@solvay.com

NB : Adagio does the modification on a separated server which is replicated every hours. You have to wait to see modification.

Example of message :

Image Added Image Added

Adding a plant to DynaSys scope

CAUTION : all delta loading are impacted 

Step1 ) Check the daily DynaSys chain (PC_DPS_DYNASYS_01) is finished via ST13

Image Added

Step2) Add a new line in Global Filter (C_GLBFILT) for Stream DPS / Rule PLANT

/!\  check requested Plants are not already in DynaSys scope, dupplicates records would make daily chain fails

Please indicates in the description the date and user code to track changes

Image Added