The objective of the application is to extract from Dynasys Forecast & Booking data and also Dynasys Master data (ShipTo, SpecID, Market...).
Then these data are used for the application BW - DPS - Forecast Vs Booking / Component.
Tool Leader: Lei Shen
IT leader of the application: Lei Shen (PP), Romain Clerc (Dynasys) Craig Wanamaker (BW)
Name of project: Solstice
PMO Project: 8612 Solstice AERO
Reporting Coordinator: Lei Shen
Number of users: tbd
Critical period: none
Geographical perimeter: worldwide
InfoArea:
This application is linked to the Solstice global project and this specific need was named "DEV47- Other MiniBW request for planning team".
MiniBW (CPX) dedicated platform was created for Aero Requirements about Solstice project.
List of application role + menu role and explanation if we have several applications role with specials rules.
| Role Code | Role Description | Explanation |
|---|---|---|
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
Reporting documentation drive folder:
https://drive.google.com/drive/folders/1Y2OmoBqD6VWwpmUPnuiQ6ZFm0hwlPruA
Dataflow overview :
Dynasys is a MSSQL tool, the connection with CPX system is done with SAP Hana Smart Data Access.
Dynasys main servers :
Dynasys Development server => wdcslvbd31\slv1_dbdev
Dynasys Testing server => wdcslvbt31\slv1_dbtst
Dynasys Production server => wdcdyap21\dy_dbprd
| DynaSys View | MasterData/Transactionnal | Content | Associated Datasource | Comments |
| EXP_MFB_V1_BW | Transactionnal | Forecast and Sold & Booking data (Quantity and Amount) by month | DTS_ZBW_V_EXP_MFB_V1_BW | Forecast data from current month to current + 17 months => 18 months of forecast data |
| EXP_MFB_V2_BW | MasterData | Specification, Market, Program Master Data | DTS_ZBW_V_EXP_MFB_V2_BW | |
| EXP_MFB_V3_BW | MasterData | ShipTo Master Data | DTS_ZBW_V_EXP_MFB_V3_BW | |
| EXP_MFB_V4_BW | MasterData | Forecast Customer Master Data | DTS_ZBW_V_EXP_MFB_V4_BW |
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
Sheet "Dim_Forecast&Booking" :
There are two fields with currency coming from Dynasys :
Both are extracted from Dynasys in KG and stored respectively in following key figures :
There are also converted in Base Unit of Measure linked to the material record in following key figures :
Determination of Base Unit of Measure (by reading C_MATNR Master Data) and conversion in Base unit of measure are done in the end routine of transformation between ADSO APDPDY01 and ABDPDY01.
See below the link to have more explanations on ABAP rules applied :
BW OTC - Supply Chain- DPS (WBP) /!\ Obsolete /!\#SupplyChain-DPS(WBP)-ConversioninKGunit
Dynasys data are used in application BW - DPS - Forecast Vs Booking / Component.
Master data are loaded by the process chain DICO_PC_DPS_MD :
Dynasys Master Data Process chain are part of global chain RSP_DAILY_GLOBAL :
There are 3 process chain (one by Layer) to load transactionnal data :
These process chain are part of global chain RSP_DAILY
There is also a global process chain to load master data and transactionnal data : PC_DPS_DYNASYS_06
Daily loading
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
| Key Figure | Estimation |
|---|---|
| ~ Average Process Chain Runtime | |
| ~ Average nb of rows loaded per load | |
| ~ Total nb of rows loaded (if full) | |
| ~ Average Runtime for 10k lines |
Give details if any historisation is done, example: keep only data greater than beginning of Y-3
Query end user documentation should be created in the public "Customer Support Wiki" space under the corresponding BW application page : BW - Application. Technical query query documentation, if necessary should be added as a sub-page of this documentation using the BW Technical Query Documentation template.
There is a query BW_QRY_CPDPDY01_0001 (Dynasys - Dynasys Data Reporting) based on composite provider CPDPDY01 (Dynasys Virtual).
This query was used for testing data coming from Dynasys source system but it is not used and accessible by key users.
Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts
Indicate if there are broadcasts and give some details on the broadcast settings.
Give the list and explanation on the known, not-solved, bugs.
List recurring procedures
Detail planned major evolution if already known. Example: complete decommissioning of application is planned in 2017 / Extension to solvay perimeter planned in 2nd semester of 2016