The objective of the application is to extract Key figures from several sources in order to calculate Industrial KPIs.
Then data will be consumed by Qlikview E2E Value Chain Dashboard.
Tool Leader: Diogo Paiva (IS SCM)
IT leader of the application: Craig Wanamaker (BW)
Reporting Coordinator: Diogo Paiva (IS SCM) / Meire Santos
Number of users: tbd
Critical period: none
Geographical perimeter: worldwide
InfoArea:
BW queries have been created to avoid data to Qlikview Dashboard.
It is also existing "Core Query" usable with Analyses for Office (AFO) Tool .
This application is linked to the E2E VC Dashboard global 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 |
|---|---|
GBU (CPFCTR1_2) | ZR_*_CA_P05 |
https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE
Dataflow overview :
To calculate this KPI, we must get the result of the specific transaction ZWPP24A_1 (diplay "List 3") from both source system WP1 and PF1.
The same specific datasource DTS_ZBW_ZWPPT025 has been developed for each system.
It is based on table ZWPPT025.
All necessary fields to calculate the RFT KPI are in the current table expect the "Confirmed quantity". To get it, we use an append structure ZABIW_ZWPPT025 and the respective class ZDTS_ZBW_ZWPPT025.
The appened filed is ZCONFORM_QTY (Conform quantity used to calculate T0).
The ABAP code used to determine the conform quantity is a copy of the one used in the transaction ZWPP24A_1 (check the program ZWPPR01400_1).
RFT KPI (%) is determined by the formula Conform Quantity / Total Batch Quantity.
It is calculated directly on the Query.
There is a specific rule when the Line Type is equal to 5 "By Product" : If conformed quantity = 0 and Total quantity > 0, RFT KPI is equal to 100%.
To calculate this KPI, we are using following both key figures coming from Dynasys :
The extraction from Dynasys is done with the extractor DTS_EXP_BW_SKU_BW based on view EXP_BW_SKU_BW.
Key Figures are determined by the field DATAFIELDTYPE_CO :
They are defined at Material / Shipping Site / Ressource (Work center) / Period level.
Utilization Rate KPI (%) is determined by the formula Actual Production Quantity / Production Capacity Quantity.
It is calculated directly on the Query.
To calculate this KPI, we are using following both key figures coming from Dynasys :
The extraction from Dynasys is done with the extractor DTS_EXP_BW_SKU_BW based on view EXP_BW_SKU_BW.
Key Figures are determined by the field DATAFIELDTYPE_CO :
They are defined at Material / Shipping Site / Ressource (Work center) / Period level.
Planning Adherence KPI (%) is determined by the formula Actual Production Quantity / Planned Production Quantity.
It is calculated directly on the Query.
The BW application provide data to Qlikview E2E VC Dahboard application.
Both ADSO AASCE2E01 and AASCE2E02 in acquisition layer are loaded by 2 FULL DTPs respectively from WP1.
We load records with movement date >= 01.01.[Current Year - 2].
Average number of lines in ZWPPT025 table (July 2020) :
Transactional data are loaded by the process chain PC_SC_E2E_01.
Data are loaded every day at 12:00 AM CET.
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 |
We load records with movement date >= 01.01.[Current Year - 2], to keep the last 3 years of data.
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.
List the most important and complex queries only with a link to the documentation
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
PF1 RFT KPI BW dataflow is build but not into production. We are waiting for implementation of transaction on PF1 SAP system.