...
PMO Project: 8612 Solstice AERO
UR: UR335513 DYNASYS Sales Forecast / UR333365 DYNASYS Demand Planning
Reporting Coordinator: Lei Shen
...
| Role Code | Role Description | Explanation |
|---|---|---|
Authorization objects
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
Dataflow overview
Reporting documentation drive folder:
https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE1Yd_vWT7i3hmTaFBBH3DAtYE3LalTzOz8
Dataflow overview :
| Embedded Google Drive File | ||
|---|---|---|
|
Functional and Technical rules on Workbench + Reporting
Rules & Explanations
Specification document
...
| Embedded Google Drive File | ||
|---|---|---|
|
...
We can't use the ADSO UOMC_MAT because the PUoM is linked to the material and the plant as well.
There are 3 conversion type used :
| Conversion Type | Reference Infobject | Comments |
|---|---|---|
| QCT_MATNR9 | C_MATPLNT | Conversion type used for key figures at Product Level |
| QCT_MATNR6 | C_BOMHEAD | Conversion type used for key figures at BOM Head Level |
| QCT_MATNR5 | C_BOMCPNT | Conversion type used for key figures at BOM Component Level |
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 | Already in Base Unit of Measure when data is extracted | 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 | |
Quantity Per 1 Puom (K_QTYPUOM) | Key figure is directly expressed in PUoM. | Key figure is assigned and calculated from K_SOBQTYB in transformation between ADSO AADPDY05 -> APDPDY02. | |||
| 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 in transformation between ADSO AADPDY05 -> APDPDY02. | |||
| Quantity Forecast Base (K_FFBASE) | Key figure is directly expressed in PUoM. | Key figure is assigned and calculated 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 in transformation between ADSO AADPDY05 -> APDPDY02. | |||
| Quantity Booking Base (K_SOBBASE) | Key figure is directly expressed in PUoM. | Key figure is assigned and calculated in transformation between ADSO AADPDY05 -> APDPDY02. |
...
Forecast quantity calculation at component level
Forecast and Sold & Booked quantity are determined in Dynasys for a "main product".
Theses quantities have to be recalculated for each component composing the "main product" proportionally to component quantity.
Forecast and
Sample example
To do it we need BOM Data (to have each component of the "main product" ans associated quantities) and Dynasys data (to have Forecast and Sold & Booked quantities).
Both data flow are joined in the calculation view Forecast Data level by level (CV_FORECAST_LEVEL_BY_LEVEL).
The calculation is done on BW side in the ADSO APDPDY02.
Sample example
Please find below, Excel file with example of calculation and rules applied :
https://drive.google.com/file/d/1qxOZq4EgVWkj7tzjhNdEcksmLgLLMpK6/view
Dependencies with other applications
...
Step used to send the event :
Global Master
...
data
Master Data are loded loaded with process chain RSP_DAILY_GLOBAL.
Transactionnal
...
data
Transactionnal data are loaded with process chain RSP_DAILY.
...
Data are loaded every day.
Average performance
...
| 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 |
Record Keeping
Reporting
Queries End User Documentation
Main queries
BW - DPS - Forecast Vs Booking / Component (Core Query)
...
Recurring procedure
Planned Evolution
...