General presentation

Objective of the application

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:

Dataflow Architecture (with technical rules)
Monitoring Procedure (with already known issues)
List of Jobs in ECC and Process Chains in BW
List of BEx Core Reports
Functional Administrator Guide for BW (for setting tables)
Functional Guide for KPI (user catalog of KPI with functional rules )

List of contacts:

Ruben FERNANDEZ SANCHEZ (SBS Manufacturing Excellence) : Business Application Owner
Célia GONZALEZ-ROUX (SBS Information Services) : Reporting Coordinator
Raphaël BERT (SBS Information Services) : IT Project Leader
Christophe MALLEVAEY (SBS Information Services) : PM Process Expert
Gilles BOUNAN (SBS Information Services) : Qlikview Technical Developer
Benoit ROSSET (SBS Information Services) : BW Technical Developer

Usage information

Around XX key users on BW and XXX end users on QV. The tools is used by five plants worldwide during the PoC and the first deployment, it will be opened progressively to new plants.

Roles & Access

Roles and access

Authorization role : ZR_RCS_PM_A02: Maintenance Orders Applications - End User role
Role menu : ZR_RCS_CA_M08: PM - Plant Maintenance

Authorisation objects

Plant
Company Code

Dataflow presentation

Overview

Functional and Technical rules on Workbench + Reporting

<detail of main topics with explanations of the rules and only the main + special rules about queries to run and use in the correct way

Dependencies :

It shares extractors (2LIS_17_I3OPER, 0PM_OM_OPA_2/3) with the legacy PM application for RCS.
It shares texts of master data Notification and Work Order with PUNCH.
Some data is calculated in ECC with program ZWBWF00100 every day at 23:00 GMT+1 before being loaded in BW. BW Snapshots run at 01:00 GMT+1.
Data is consumed by Qlikview dashboard. The loadings in QV are weekly and done on Monday at 05:00 GMT+1. One KPI is also loaded every day in QV.
There is no links in the loadings between SAP, BW and QV. It run on a fixed scheduled, the loadings must be finished when the next start.

Data loadings

Info providers and objects loaded

< detail of process chain, list + link between or special event done for the loading >

Loading frequency

Average performance

<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>

Historization

We keep all the data in the Up to Date DSO, and we keep only one year of history for Snapshots in DSO and cubes.

The deletion of old Snapshots is done in process chain based with deletion programs, it has been generated as described here : https://drive.google.com/open?id=0B6UtwJUYvmgTWjhHY0k0RG5xZjA

The programs have been modified to fill automatically the parameter C_SNAPWK for the deletion from the setting RET_WEEK from master data C_GBLFILT.

Reporting

Queries Documentation or user guide

List of BEx Core Reports
Functional Guide for KPI (user catalog of KPI with functional rules)

Main queries

List of BEx Core Reports

Main functionnalities

Functional Guide for KPI (user catalog of KPI with functional rules)

Broadcast

None

Maintenance

Known bugs

Refer to the known bugs in the recovery procedure: Monitoring Procedure (with already known issues)

Recurring procedure

Monitoring Procedure (with already known issues)

Planned Evolution

Actions to plan for a deployment on a new plant:

Grant users authorizations for reporting in BO Analysis and Qlikview.
Create jobs for calculation of KPI 2.4, 2.10, 2.15 and 2.16 in ECC if needed.