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 and not to use them directly with Analysis for Office 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 |
|---|---|
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 BW application provide data to Qlikview E2E VC Dahboard application.
Both ADSO AASCE2E01 and AASCE2E02 in acquisition layer are loaded by 2 FULL DTPs (without selection) respectively from WP1 and PF1 SAP source system.
Average number of lines in ZWPPT025 table (June 2020) :
Detail of frequency : monthly; weekly or else
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.
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.