The objective of the application is to diplay Forecast & Booking data coming from Dynasys at component level (BOM Data from WPX system).
Forecast & Booking data have been recalculated proportionnaly to BOM base quantity and component quantity.
Report is expanded with Recipe & Capacity data coming from WPX system.
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
UR: UR335513 DYNASYS Sales Forecast / UR333365 DYNASYS Demand Planning
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/0B0qn89R0RGdqYkZZOFZyYXlXVkE
Dataflow overview :
Specification document :
Currency conversion :
There are two "AMOUNT" key figures with currency in the application :
Both are extracted from Dynasys in Euros :
In the report, users have the possibility to convert them in USD (target currency choosen in the prompt of the query).
The conversion is done directly in the report with convertion type CTK_CAR4.
Quantity conversion :
All "QUANTITY" key figures in the report are expressed in Production Unit of Measure. If for this material the Production Unit does not exists, the quantity is expressed in Base Unit of Measure.
Example of Production Unit of Measure from SAP system :
To convert key figure in Production Unit of measure, first of all data have to be expressed in Base Unit of measure, then they will be converted to PUoM based on ADSO UOMC_MAT2 (Material/plant Unit of Measure).
We can't use the ADSO UOMC_MAT because the PUoM is linked to the material and the plant as well.
Where the quantity has been converted ?
| Key figure | Conversion in Base Unit of Measure | Conversion in Production Unit of Measure | Conversion Type (PUoM) | Comments |
|---|---|---|---|---|
| Costing Lot Size (EOQ) (K_COMPCLS) | During extraction. Extractor : 0MAT_PLANT_ATTR | In the query | QCT_MATNR5 | Key figure is stored in C_MATPLNT master data with the technical name K_LOSGR. |
| Recipe Base Qty (K_OPERQTY) | During Extraction. Extractor : DTS_ZBW_V_PLPO | In the query | QCT_MATNR5 | Key figure is initialy stored as field in AAPPRE02 ADSO with the name : BMSCH |
| Base Quantity for BOM (PUoM) (K_BQTYBOM) | During Extraction. Extractor : DTS_ZBW_MAST_BOM_LEVEL | In transformation between ADSO AADPDY05 -> APDPDY02. | QCT_MATNR6 | Key figure is initialy stored as field in AAPPBO02 ADSO with the name : BMENG |
| Component Quantity (PUoM) (K_COMPQTY) | During Extraction. Extractor : DTS_ZBW_MAST_BOM_LEVEL | In transformation between ADSO AADPDY05 -> APDPDY02. | QCT_MATNR5 | Key figure is initialy stored as field in AAPPBO02 ADSO with the name : ZZMENGE |
| Forecast (Dynasys) (K_FFQTY) | No converstion, the key figure is loaded from Dynasys in KG and stored as identical. | No converstion, the key figure is loaded from Dynasys in KG and stored as identical. | Key figure is initialy stored as field in AADPDY01 ADSO with the name : FF_QTY | |
Forecast (PUoM) (K_FFQTYB) | In transformation between ADSO APDPDY01 (DYNASYS) -> ABDPDY01 | In transformation between ADSO AADPDY05 -> APDPDY02. | QCT_MATNR9 | |
| Forecast Quantity Level by Level (K_FFLVL) | Key figure is directly expressed in PUoM. | Key figure is assigned and calculated from K_FFQTYB in transformation between ADSO AADPDY05 -> APDPDY02. | ||
| Quantity Forecast Base (K_FFBASE) | Key figure is directly expressed in PUoM. | Key figure is assigned and calculated from K_FFQTYB in transformation between ADSO AADPDY05 -> APDPDY02. | ||
| Booking (Dynasys) (K_SOBQTY) | No converstion, the key figure is loaded from Dynasys in KG and stored as identical. | No converstion, the key figure is loaded from Dynasys in KG and stored as identical. | Key figure is initialy stored as field in AADPDY01 ADSO with the name : SOB_QTY | |
| Booking (PUoM) (K_SOBQTYB) | In transformation between ADSO APDPDY01 (DYNASYS) -> ABDPDY01 | In transformation between ADSO AADPDY05 -> APDPDY02. | QCT_MATNR9 | |
| Booking Quantity Level by Level (K_SOBLVL) | Key figure is directly expressed in PUoM. | Key figure is assigned and calculated from K_SOBQTYB in transformation between ADSO AADPDY05 -> APDPDY02. | ||
| Quantity Booking Base (K_SOBBASE) | Key figure is directly expressed in PUoM. | Key figure is assigned and calculated from K_SOBQTYB in transformation between ADSO AADPDY05 -> APDPDY02. |
Forecast quantity calculation at component level :
Sample example :
This application and report is based on following BW application :
Detail of process chain, list + link between or special event done for the loading
Detail of frequency : monthly; weekly or else
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.
BW - DPS - Forecast Vs Booking / Component (Core Query)
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