Access Management 

DataFlow

Overview

Use the google presentation below as a template. This google presentation must be saved in the Reporting GDrive folder under the corresponding application. Then post the link to the document here.

Reporting documentation drive folder:

https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE

Exemple of dataflow overview :

Template Application name DataFlow

Technical Rules on Workbench

Mains abap rules in transformations:

MVQM01 → cubes associated with no data or not loaded since 2019 or 2021 doc done in december 2023).

TRSF: DPQM09 -> DBQM04 (Rhodia)

Start routine: an internal table is filled with data from  APQMNCPLT (QM - Novecare Plants) for each correspondance with source system and plant from data from DPQM09.

If this internal table is empty (it means no correspondance with APQMNCPLT) source data with C_MRMITNI (Result exists) not empty are deleted.

If this internal table is not empty, and if we don't have a correspondance AND if C_MRMITNI (Result exists) is not empty, then the records are deleted.

If field  BATCH is empty, he takes value from C_LSCHARG (Batch Number (QALS)).

Internal table itb_h_dpqm09 is filled with multiples rules:

Internal table  itb_C_GLBFILT take values from master data global filter for stream 'QM' and rule = 'INSP_TEXT"

Fields routine:

Fields:

K_MITTEL (Quantitative Result) / C_SATZS (Results Record Status (Global)) / C_PRUDV (Inspection Start Date (Global)) / C_RESULT (Result) / C_PRUDT (End Date of the Inspection (Global)) / C_PRUET (End Time of the Inspection (Global)) / C_MBETG (Inspection Result Valuation (Global)) / C_PRUTV (Starting Time of the Inspection (Global)) / C_POSTE (Work Center (real) = General information if exists) / C_ATTRI (Attribute of the Results Record (Valid, Invalid,..) (Global)) / C_MASCHIN (General Information (Global)) / C_QERGDAT Origin of Results Data (Global)

come from itb_h_dpqm09 (key fields  insp_lot / c_insp_ch / plan_type / plnnr / c_plannod / c_phys_sp / c_detaile / c_probenr / logsys).

0CO_AREA comes from master data PLANT.

End routine:

Fields C_FTR / C_TOT_SL / C_TOT_OFF / C_FSR  contains TRUE or FALSE with a comparaison between the records of fields  C_PHYS_SP /  C_LTXA1 and INSP_LOT (see end routine to more details).

TRSF: DPQM10 -> DBQM04 (Rhodia)

Except for the selective deletion in start routine not present here, the logic and rules are the same as transofrmation TRSF: DPQM09 -> DBQM04 (Rhodia)

TRSF: IH_QM_2LIS_05_QE1_RCS -> DPQM09

Key figure K_MINUTES comes from dso DPQM09 in case of same records was already loaded in the past with K_MINUTES greater than 0.

C_SHIFTDT (Shift work day) and C_SHIFT (Work shift) are determined in function of workctr (work center), c_qzeitv (Starting Time of the Inspection (QAMR)).

TRSF: DPQM07 -> DBQM03 (Solvay)

Start routine: If field  BATCH is empty, he takes value from C_LSCHARG (Batch Number (QALS)).

Internal table itb_h_dpqm07 is filled with same rales as  itb_h_dpqm09 in transformation TRSF: DPQM09 -> DBQM04 (Rhodia)

Fields:

K_MITTEL (Quantitative Result) / C_SATZS (Results Record Status (Global)) / C_PRUDV (Inspection Start Date (Global)) / C_RESULT (Result) / C_PRUDT (End Date of the Inspection (Global)) / C_PRUET (End Time of the Inspection (Global)) / C_MBETG (Inspection Result Valuation (Global)) / C_PRUTV (Starting Time of the Inspection (Global)) / C_POSTE (Work Center (real) = General information if exists) / C_ATTRI (Attribute of the Results Record (Valid, Invalid,..) (Global)) / C_MASCHIN (General Information (Global)) / C_QERGDAT Origin of Results Data (Global)

come from itb_h_dpqm07 (key fields  insp_lot / c_insp_ch / plan_type / plnnr / c_plannod / c_phys_sp / c_detaile / c_probenr / logsys / recordmode).

TRSF: 2LIS_05_QE2 - Solvay -> IH_QM_2LIS_05_QE2

0CO_AREA comes from master data PLANT.

TRSF: DPQM08 -> DBQM03 (Solvay)

Data with C_MRMITNI (Result exists) is empty are deleted.

Internal table itb_h_dpqm08 is filled with same rales as itb_h_dpqm08 in transformation TRSF: DPQM09 -> DBQM04 (Rhodia) and same fields are loaded.

0CO_AREA comes from master data PLANT.

TRSF: IH_QM_2LIS_05_QE1_SOLVAY -> DPQM08

C_SHIFTDT (Shift work day) and C_SHIFT (Work shift) are determined in function of workctr (work center), c_qzeitv (Starting Time of the Inspection (QAMR)).

MVQM02 → cubes associated with no data or not loaded since 06.2020 (doc done in december 2023).

CPQM01

Based on CVs CV_QM_INPDVL_PF1 & /CV_QM_INPDVL_WP1.
Theses CVs use dso DBQM03 & DBQM04 (transformations associtaed already documented), DPSD001 and DSO_DLV1.

RSDS DTS_BW_LIPS_LIKP PF1_020 -> ODSO DPSD001

In start routine an internal table itb_dpsd001 is updated with fiscvarnt, delnum2 (delivery number) and delitm2 (delivery item) from dpsd001 (only for data from package with same c_delnum2 in DSO).

This table is usend in end routine to fill fiscvarnt.

TRSF: 2LIS_12_VCITM -> DSO_DLV1

0ITEM_CATEG (Sales document item category) comes from:

dso_sd02 in function of vgbel (reference doc) and vgpos (reference item) and if the two firsts characters from vgbel (reference doc) not equals to 45.

If vgbel equals to 45, default value = NLC.

Else, 0ITEM_CATEG equal source field pstyv (item category)

CPQM02:

Based on aDSO: ABQM02, APQM01, ABQM04, ABQM01 and ABQM03.

ABQM02 & ABQM04 have a source DBQM03 (transformations associated already documented) with direct mapping.

ABQM01 & ABQM03 have a source DBQM04 (transformations associated already documented) with direct mapping.

No specials rules for APQM01.

CPQM03:

No speciales rules in transofrmations asscoiated

CPQM04:

No speciales rules in transofrmations asscoiated

CPQM05:

CV CV_QM_CPQM05 based on CPQM02 and CPQM03

Propagation layer-APQM02

This ADSO extracts data from the following two data sources from WP1 and PF1

DTS_BW_QM_ATTRIBUT(WP1_400) → APQM02

DTS_BW_QM_ATTRIBUT(PF1_020) →  APQM02

Both the Data sources  created based on Function Modules(ZFM_BW_QM_ATTRIBUT (PF1+WP1) and implemented the same business logic in both the systems.

Function module extracts  Inspections lot with  ' SATZSTATUS -5 (Record status completed)  and ATTRIBUT type  Invalid results Only .

Source for  this function module is QASR,QALS,QAMV,QAPP and PLKO tables in SAP in order to find the required field 

From source to PSA data load will be triggered based on created on and changed on date in two different Info packages. There is a code at Info package level to extract last four data.

Reporting

Workbooks:

Dependencies with other applications

We should have the information where the application is sending or receiving information (e.g. APD open hub) 

Data Loading

Info Providers and objects loaded 

Detail of process chain, list + link between or special event done for the loading

Data Quality Control

Operational Documentation

Procedures

<Describe the recurring procedures needed to operate the application (eg. start/pause/terminate/restart the app processes, data preparation, data ingestion, ETL, data visualization, data export, other manual activities)>

Scheduling

<Describe the scheduling in place for the application (eg. existing jobs, trigger time/event based, dependencies)>

Monitoring

<Describe the monitoring checks to confirm the application is performing well (eg. check the overall status, check performance metrics like runtime/data volume/memory/disk/CPU, maintain and react to alerts/notifications)>

Error Handling

<Describe how to handle errors (eg. error codes, description and respective resolution, alert users)>

Known Bugs

<List the existing bugs, its criticality, workarounds and resolution plan.>

Roadmap

<List past & future evolutions for the application (including links to MED/FSD/TSD>