The application loads data of the Plant Maintenance domain from ECC into BW. It takes every week snapshots based on the current state of the data to calculate the KPI. The snapshots are loaded into a Qlikview dashboard.
Main documentation:
Functional Administrator Guide for BW (for setting tables)
Célia GONZALEZ-ROUX (SBS Information Services) : Reporting Coordinator
Raphaël BERT (SBS Information Services) : IT Project Leader
Gilles BOUNAN (SBS Information Services) : Qlikview Technical Developer
Benoit ROSSET (SBS Information Services) : BW Technical Develope
As part of Ticket-4391573 we have the Changed the logic of Key figure - "Nb of Notif. In Progress with Delay" in BW reports of the KPI 2.05 and KPI KPI 3.3
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 |
|---|---|
Reporting documentation drive folder:
https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE
Exemple of dataflow overview :
Template Application name DataFlow
Changed the existing logic of Key figure - "Nb of Notif. In Progress with Delay" in BW reports of the KPI 2.05 and KPI KPI 3.3
| Existing logic - KPI 2.05 | If Required end date is exists and < snapshot week first day date then, Notification delay = Snapshot week first day date minus Required end date. |
| New Logic- KPI- 2.05 | If Required end date is exists and < snapshot date then, Notification delay = snapshot date (loading date) minus Required end date |
| Existing logic - KPI 3.3 | If Due date is exists and < snapshot week first day date then, Notification delay = Snapshot week first day date minus Due Date |
| New logic - KPI 3.3 | If Due date is exists and < snapshot date then, Notification delay = snapshot date (loading date) minus Due date |
For this ,we have done changes at Method level : zbw_pm_mecano_utils=>calculate_notification_delay of the Transformations of the MVPMNO02 and MVPMCL01 flow
We have done changes in the following transformations
Not required any query level changes for this development
Please refer test cases in the following link
Dependencies with other application (BW, QV, Externals tools like PVelocity or Dynasis etc...
Detail of process chain, list + link between or special event done for the loading
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
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