General presentation
Objective of the application
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
Usage information
Number of users: tbd
Critical period: none
Geographical perimeter: worldwide
InfoArea:
Usage information
BW queries have been created to avoid data to Qlikview Dashboard.
It is also existing "Core Query" usable with Analyses for Office (AFO) Tool .
History
This application is linked to the E2E VC Dashboard global project.
Roles & Access
Roles and access
List of application role + menu role and explanation if we have several applications role with specials rules.
| Role Code | Role Description | Explanation |
|---|---|---|
Authorization objects
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
GBU (CPFCTR1_2) | ZR_*_CA_P05 |
Dataflow overview
Reporting documentation drive folder:
https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE
Dataflow overview :
Functional and Technical rules on Workbench + Reporting
Functionnal Specification Document
BW Specification Document
Rules & Explanations
RFT (Right First Time) KPI
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%.
Asset Utilization KPI
To calculate this KPI, we are using following both key figures coming from Dynasys :
- Actual Production
- Production Capacity
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 :
- Actual Production : DATAFIELDTYPE_CO = ACTUALPRODUCTION
- Production Capacity : DATAFIELDTYPE_CO = PRODUCTIONCAPACITY
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.
Planning Adherence KPI
To calculate this KPI, we are using following both key figures coming from Dynasys :
- Actual Production
- Planned Production
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 :
- Actual Production : DATAFIELDTYPE_CO = ACTUALPRODUCTION
- Planned Production : DATAFIELDTYPE_CO = PLANNEDPRODUCTIONBYRESSOURCE
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.
Dependencies with other applications
The BW application provide data to Qlikview E2E VC Dahboard application.
Data loadings
Info providers and objects loaded
Scope of data loaded
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) :
- WP1 => 1.446.532 records
Transactional data process chain
Transactional data are loaded by the process chain PC_SC_E2E_01.
Loading frequency
Data are loaded every day at 12:00 AM CET.
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
We load records with movement date >= 01.01.[Current Year - 2], to keep the last 3 years of data.
Reporting
Queries End User Documentation
Main queries
Main functionalities
Broadcast
Maintenance
Known bugs
Recurring procedure
Planned Evolution
PF1 RFT KPI BW dataflow is build but not into production. We are waiting for implementation of transaction on PF1 SAP system.