The objective of the application is to extract from SAP Vault source system Work center data and calculate capacity at week level & month level.
Then these data are used for the application BW - DPS - Forecast Vs Booking / Component and in the query BW-DP-Labor Planning Tool Interface (Core query).
Tool Leader: Lei Shen
IT leader of the application: Lei Shen (PP), 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 |
|---|---|
https://drive.google.com/drive/folders/1Y2OmoBqD6VWwpmUPnuiQ6ZFm0hwlPruA
Sheet "Dim_Resource" & "Dim_ProdVersion" :
There are 2 ADSO following the calculation level :
Both ADSO are loaded by the same datasource DTS_DPS_ZWPPT042 based on SAP (Vault) table ZWPPT042.
Calculation is done in end routine of each transformation between ADSO and datasource by reading ADSO APPPCP01 (Interval of Available Capacity) with function module Z_WBW_READ_KAZY_2 (duplication and adaptation of existing one on WBP BW system).
There are 2 key figures calculated :
This ADSO (APPPCP01) is loaded by the datasource DTS_DPS_KAZY based on function module Z_WBW_DTS_DPS_KAZY (duplication and adaptation of existing one on WP1 SAP system).
The capacity loaded in APPPCP01 is reported in secondes for a defined weekday, then it is calculated in hours in ABPPCP02 (by week) & ABPPCP03 (by month).
Capacity data are used in application BW - DPS - Forecast Vs Booking / Component.
All these previous process chain are part of global RSP_DAILY_GLOBAL :
There are 2 process chain :
They are part of process chain PC_PP_04 :
PC_PP_04 is part of global RSP_DAILY :
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 are 2 queries :
BW_QRY_CPPPCP03_0001 (Capacity Planning Monthly data) based on composite provider CPPPCP03 (Capacity Planning - Monthly).
This query was used for testing data coming from SAP 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