(warning)     (warning)     (warning)     (warning)

The new wiki link for this data flow is here:

Technical Documenation - Quality Management Report

Please update the doc there and no longer here.

(warning)    (warning)     (warning)     (warning)


General presentation

Objective of the application

The objective of the application is to provide the KPI Conformity Rate to the Qlikview application E2E Value Chain Dashboard.

That KPI is calculated with Accepted Quantity and Total batch Quantity available with this BW application.

It is also existing "Core Query" usable with Analyses for Office (AFO) Tool .


Tool Leader: Meire Santos

IT leader of the application: Meire Santos (PP), Craig Wanamaker (BW)

Reporting Coordinator: Meire Santos

Usage information

Number of users: tbd

Critical period: none

Geographical perimeter: worldwide

InfoArea:


History

This application was created in order to provide a new KPI to the E2E VC Dashboard.

Roles & Access

Roles and access

List of application role + menu role  and explanation if we have several applications role with specials rules.

Role CodeRole DescriptionExplanation
ZR_RCS_CA_M14QM - Quality ManagementThis role gives access to the Query and Workbooks through role menus.
ZBI_RCS_QM_A02Quality Results Application - End User roleThis role controls access to the application.
ZR_*_CA_P02

Analysis - Plant XXX - YYY

Role to control access to data based on the plant, with XXX being the name of the plant, and YYY its description. There is a many role as there is plants.

In the new Composite Provider created, the infoobject used for authorization is C_PLANT.

Authorization objects

List of autorisation objects mandatory for the application.

Authorization objectExplanation






Dataflow overview

Functional and Technical rules on Workbench + Reporting

Functionnal  Specification Document 


Rules & Explanations

All fields are mapped 1 to 1 from the datasource to the ADSO of Business Layer excepted in the transformation :

  • IS 2LIS_05_UDN (Core) -> APQM03 (Solvay)
  • IS 2LIS_05_UDN (Core) -> APQM04 (RCS)

For both, above mentioned transformations, there are 2 fields filled by ABAP routine :

  • 0LOGSYS : Logsys is determined in the start routine using the function module  'Z_WBW_SOURCE_SYSTEM'. The field is filled in the end routine.
  • C_VALCLAS : Valuation class is stored in an internal table in the start routine reading master data C_MATPNT3. Field is filled in the end routine

Dependencies with other applications

Data are consumed by the E2E VC Dashboard (QV application).

Data loadings

Info providers and objects loaded

Propagation Layer 

  • The ADSO APQM03 (QM - Inspection Lot/Usage Decision (Solvay)) is loaded by the process chain PC_QM_37.
  • The ADSO APQM04 (QM - Inspection Lot/Usage Decision (RCS)) is loaded by the process chain PC_QM_38.

Business Layer 

  • The ADSO ABQM06 (QM - Inspection Lot/Usage Decision (Solvay)) is loaded by the process chain PC_QM_39.
  • The ADSO ABQM07 (QM - Inspection Lot/Usage Decision (RCS)) is loaded by the process chain PC_QM_40.


Master Chain

All previous process chain are part of the master chain PC_QM_00

Loading frequency

Data are loaded every day.

Average performance


Key FigureWP1PF1
~ Average Process Chain Runtime (Propa + Business Layer)1 min50 sec
~ Average nb of rows loaded per load (delta)1500350
~ Total nb of rows loaded (if full) => Init of 2LIS_05_QVUDN4.177.2481.041.687
~ Average Runtime for 10k lines//

Init of datasource 2LIS_05_QVUDN (filling of setup table)

LOGSYS

Time

QALS (Nb rec.)

QAVE (Nb rec.)

WQ1 (11/2020)

2 hours

6.386.362

5.655.505

QF1  (11/2020)

10 min

1.326.678

1.188.337

WP1 (07/01/21)

1 hour

6.579.602

5.820.417

PF1 (07/01/21)

11 min

1.386.075

1.231.528

Record Keeping

Reporting

Queries End User Documentation

Main queries

Main functionalities

Broadcast

Maintenance

Known bugs

Recurring procedure

Planned Evolution


  • No labels