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" 


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

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
  • Company Code

DataFlow

Overview

Technical documentation for dataflows : https://drive.google.com/open?id=0B-KST39ThPrUeUVDb0FRNVNQckU

Technical Rules on Workbench

Below objects should be loaded previously before load GTBU in the following sequence:

  1. Master Data C_PMORDR (Work Orders Master Data)
  2. DSO ODS_PM04 (Work Orders / Operations)

Reporting


Main queries

Main functionnalities

The files generate data for BW in the export tab. Indicators are registered in the files with a key. After confirmation of the file, a night job (on WP1: PM_T00400_EU; on PF1: ZZI_020_TA_GTBU_EXTRAC_BW) for program ZWPMT00400 add data in tables ZWPMT007 and ZWPMT019 for the extraction. We can check the files uploaded by suppliers in the SAP transaction. In BW, the key relate to the KF.

The application is based on three datasources based on SAP tables:

  • DTS_ZBW_ZWPMT007
  • DTS_ZBW_ZWPMT019
  • DTS_PMESLL

Main dimensions for the data:

  • C_GTBUUID Unique log file identifier for GTBU
  • C_PMORDR PM Work Order

  • C_EQUNR Equipment number

  • C_LBLNI Entry sheet number

  • C_SEDAT Service entry sheet creation date

  • C_SCITKEY Equipment item key

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 

  • Process Chain GTBU 
  • Process Chain GTBU_SOLVAY

Loading frequency

  • Daily loadings

Average performance

  • Daily Process Chain GTBU loaded in 1h, with around 50k lines for delta and 50k lines for full at propagation level.
  • Daily Process Chain GTBU_SOLVAY loaded in 1h30, with around 1k lines for delta and 50k lines for full at propagation level.

Historization

  • None


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 criticity, workarounds and resolution plan.>

Roadmap

  • Ticket #17365: A new data has been added in the definition sheet for Scaffolding. The users want to add it in BW reports.