The objective of the application is to extract from SAP Vault source system Recipe data (operation linked to a ressource, setup time, machine time...).
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_Recipe" :
There are 3 key figures used in this application:
SAP T-CODE : C203 to display these key figures on SAP.
They are loaded from SAP Vault source system with the datasource DTS_ZBW_V_PLPO (Task list - operation/activity ) based on table PLPO ans stored in first level ADSO AAPPRE02.
BOM component is kept from STPO table and added to the datasource structure (join between STPO and PLPO table with PLMZ table).
Recipe Base quantity is converted in Base Unit of Measure of the BOM component previously mentionned.
This conversion is done in class ZDTS_ZBW_V_PLPO.
The datasource is configured as Generic Delta based on specific field AEDAT.
Data are filtered between acquisition and propagation level on field Control Key = ZCS3.
Key figures previously submitted are linked to a Recipe Group. To be used in the aplication BW - DPS - Forecast Vs Booking / Component, we need this information at material level.
To do that we need the link between Material and Recipe group. This link is stored in MAPL SAP table.
BW Extractor DTS_ZBW_V_MAPL is based on MAPL table. A join with MKAL table (Production Version for Material) has been added to filter only on production version = A001.
The result of the extraction is stored in ADSO APPPRE01.
Capacity data are used in application BW - DPS - Forecast Vs Booking / Component.
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 is a query BW_QRY_CPPPRE01_0001 (Recipe / ProdVersion / Material Data Reporting) based on composite provider CPPPRE01 (Recipe - Virtual).
This query was used for testing data coming from SAP Vault 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