Access Management 


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

Role CodeRole DescriptionExplanation

ZR_RCS_CA_M09

PS - Project Costs

Role menu for all project costs queries

ZBI_RCS_PS_A02

Project Costs and Structures Analysis - End User role

Application Role:

    • End User rights
    • gives access to infoproviders of Infoarea "AREA_PSCO"
    • BI Analysis Authorization "ZBI_PS" ("*" for authorization objects not relevant for the application)

ZBI_RCS_CO_A21

CBS Project costs Reporting Analysis - End User role

Application Role:

    • End User rights
    • gives access to infoproviders of Infoarea "AREA_F_CO_CBS_PS"
    • Gives access to multiprovider:MPR_PS014
    • BI Analysis Authorization "ZBI_CBS_PC" 

List of authorization objects mandatory for the application.

Authorization objectExplanation
0COMP_CODE;C_COMPCDE;C_PMORDER__0COMP_CODECompany, role: ZR_*_CA_P01
0PROFIT_CTR__CPFCTR1_2; 0PROFIT_CTR__C_PFCTR1;CPFCTR1_2;C_AGRITM__CPFCTR1_2;
C_ASSET2__C_PFCTR1;C_ASSET__C_PFCTR1;C_MATPLNT__CPFCTR1_2;
C_MATPLNT__C_PFCTR1;C_MATPNT2__CPFCTR1_2;C_PFCTR1;
C_PMORDER__C_PFCTR1;C_PMORDR__C_PFCTR1;C_PRDEQUI__CPFCTR1_2;
C_RECONTR__CPFCTR1_2;C_RESP_CC__CPFCTR1_2;C_SUBACT2__CPFCTR1_2
C_TECMAT__CPFCTR1_2;C_WBS_EL2__CPFCTR1_2;C_WBS_EL2__C_ZSECT;C_WBS_ELE__CPFCTR1_2;
C_WBS_ELE__C_ZSECT;C_ZSECT		GBU, role: ZR_*_CA_P05
C_FAMIL;C_WBS_EL2__C_FAMIL;C_WBS_ELE__C_FAMILFamily, role: ZR_*_CA_P04

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


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:


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)

TRSF: IH_QM_2LIS_05_QE1_RCS -> DPQM09

TRSF: 2LIS_05_QE2 WD1_110 -> IH_QM_2LIS_05_QE2_RCS


TRSF: DPQM07 -> DBQM03 (Solvay)

TRSF: 2LIS_05_QE2 - Solvay -> IH_QM_2LIS_05_QE2

TRSF: IH_QM_2LIS_05_QE2_SOLVAY -> DPQM07 (Solvay)


TRSF: DPQM08 -> DBQM03 (Solvay)

TRSF: IH_QM_2LIS_05_QE1_SOLVAY -> DPQM08

TRSF: 2LIS_05_QE1 Solvay -> IH_QM_2LIS_05_QE1


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

TRSF: 2LIS_12_VCITM -> DSO_DLV1


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.

RSDS DTS_BW_QALS_PLMK WP1_400 -> ADSO 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

Reporting

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

Main Process ChainFinal Provider LoadingFrequencyTime startDuration
















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>