Page tree


Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
outlinetrue

Access Management 


Panel
borderColor#ffffff
titleColor#ffffff
titleBGColor#009EE0
titleRoles & Access

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

Role CodeRole DescriptionExplanation

ZR_RCS_CA_M09M08

Plant MaintenancePS - Project Costs

Role menu for all project costs queries

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

PM_A02

Maintenance Orders Applications - End User role


ZR_RCS_PM_

A02:

A03

Maintenance Orders Applications -

End

Key User role

  • Role menu : ZR_RCS_CA_M08: PM - Plant Maintenance

  • Panel
    borderColor#ffffff
    titleColor#ffffff
    titleBGColor#009EE0
    titleAuthorization Objects

    List of authorization objects mandatory for the application.

    Authorization objectExplanation
    0COMP_CODE;
    C_COMPCDE
    ;C_PMORDER__0COMP_CODE
    Company
    , 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

    COMPCDE__C_

    FAMIL;C_WBS_ELE__C_FAMILFamily, role

    AUTHMA

    Authorization scope: ZR_*_CA_
    P04
    Company Code
    P00

    DataFlow

    Overview

    Image Modified

    Embedded Google Drive File
    migratedtrue
    urlhttps://docs.google.com/presentation/d/1XP-u0TaR0tWYw93x3bD1vEnv4bMvX9uEfAnQBWbYsYk/edit?usp=sharing
    fullwidthtrue
    height600

    Embedded Google Drive File
    migratedtrue
    urlhttps://docs.google.com/presentation/d/1QFcHWVicoAArMfnyhnZPeqncNJTVs9DN7LNyrH0aBzY/edit?usp=sharing
    fullwidthtrue
    height600

    Embedded Google Drive File
    migratedtrue
    urlhttps://docs.google.com/presentation/d/1uLyqRaleufC3cFA2JOhfP6h8AHjCFToH227qQjMNbSE/edit?usp=sharing
    fullwidthtrue
    height600

    Technical documentation for dataflows : https://drive.google.com/open?id=0B-KST39ThPrUeUVDb0FRNVNQckU/file/d/1q05V4_aHcOHTr_lF4fzYVPymPtUw1iAW/view

    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)

    Transformation: DSO_PM01 -> DSO_PM02 (simplified explanation, for mode details check directly the routine):

    Start routine:


    For transformations between propagation and business layer C_COMPDE comes from master data C_PMORDR if a correspondance is found, else c_compcde is empty. C_WORKCTR and C_PLANT come from C_PM_OP2.


    There are also seletives deletion in the start routines.


    Each transformations (except for DSO_PM11) have similar structures rules (with some specificities, for more detail check directly in routines):

    During the first package loading, an internal table is filled with data in source package.

    Then during the next packages, we check if the new record added already exist in internal table but with different keys. If it's the case, the line is added in ITB_ SCAFFOLDING. If not the line is added but with key figures at 0 (or null) and some key fields (C_GTBUSHC_INONUMC_INOREF) empties or the lines is not loaded.

    Key figures have differents rules in function of a specific field.

    SourceTargetSelective deletionField used in "case" to define the key figures
    DSO_PM01 DSO_PM02 Delete data where: C_EQUCAT is not empty and not equal to 0001, 0002, 0003, 0004, 0005 OR C_WKTYP nor equal to SCAFFO.

    Data are sorted in ascending by: LOGSYS, C_GTBUUID, C_GTBUVER, C_EQUCAT, C_EQUNR, C_SCITKEY.

    During the first package loading, ITB_ SCAFFOLDING is filled with data in source package. Key figures have differents rules in function of C_SCITKEY.

    Then during the next packages, we check if the new record added already exist in ITB_ SCAFFOLDING but with different LOGSYS, or C_GTBUUID, or C_GTBUVER, or C_SCSCCAT or C_SCSCNUM. If it's the case, the line is added in
    C_SCITKEY
    DSO_PM01 DSO_PM04 Delete data where C_WKTYP is different from 'PIPING'.C_SCITKEY
    DSO_PM01 DSO_PM05 Delete data where  C_WKTYP is different from 'INEL'.v_C_SCITKEY (end values of C_SCITKEY after the last ".")
    DSO_PM01 DSO_PM07 Delete data where  C_WKTYP is different from 'INEL'.C_SCITKEY
    DSO_PM01 DSO_PM08 DELETE SOURCE_PACKAGE WHERE  /bic/c_wktyp <> c_insula
                              OR /bic/c_scitkey( 5 NE c_insu2  . 
    C_SCITKEY
    DSO_PM01 DSO_PM09 DELETE SOURCE_PACKAGE WHERE  /bic/c_wktyp <> c_insula
                              OR /bic/c_scitkey( 5 NE c_insu5  . 
    C_EQUNR 
    DSO_PM01 DSO_PM10  DELETE SOURCE_PACKAGE WHERE  /BIC/C_WKTYP <> 'INSULA'
                              OR /BIC/C_EQUNR NE  ''  .
    C_SCITKEY
    DSO_PM01 DSO_PM13 DELETE SOURCE_PACKAGE WHERE  /BIC/C_WKTYP <> 'LIFT'  AND
        /BIC/C_WKTYP <> 'CLEAN' ) . 
    C_SCITKEY
    DSO_PM01 DSO_PM25 DELETE SOURCE_PACKAGE WHERE  /BIC/C_WKTYP <> 'LIFT'  AND
        /BIC/C_WKTYP <> 'CLEAN' ) . 
    C_SCITKEY
    DSO_PM01 DSO_PM26  DELETE SOURCE_PACKAGE WHERE  /BIC/C_WKTYP <> 'PIPING'
                              OR  /BIC/C_SCITKEY( 5 NE  'PIPG3'  )
                              OR  /BIC/C_EQUCAT IS  NOT  INITIAL
                                    AND /BIC/C_EQUCAT NE  'M41'
                                    AND /BIC/C_EQUCAT NE  'M42'  . 
    C_SCITKEY
    DSO_PM01 DSO_PM27 DELETE SOURCE_PACKAGE WHERE  /BIC/C_WKTYP <> 'PIPING'
                              OR  /BIC/C_SCITKEY( 5 NE  'PIPG3'  )
                              OR  /BIC/C_EQUCAT IS  NOT  INITIAL
                                    AND /BIC/C_EQUCAT NE  'M41'
                                    AND /BIC/C_EQUCAT NE  'M42'  . 
    C_SCITKEY
    DSO_PM01 DSO_PM11 DELETE SOURCE_PACKAGE WHERE /BIC/C_WKTYP <> 'COSTFE -
    DSO_PM14 DSO_PM32 DELETE SOURCE_PACKAGE WHERE /BIC/C_WKTYP <> 'COSTFE' .  -
    DSO_PM14 DSO_PM15 DELETE SOURCE_PACKAGE WHERE /BIC/C_EQUCAT <> ''
                                      AND /BIC/C_EQUCAT <> '0001'
                                      AND /BIC/C_EQUCAT <> '0002'
                                      AND /BIC/C_EQUCAT <> '0003'
                                      AND /BIC/C_EQUCAT <> '0004'
                                      AND /BIC/C_EQUCAT <> '0005' )
                                     OR /BIC/C_WKTYP <> 'SCAFFO' . 
    C_SCITVAL
    DSO_PM14 DSO_PM17 DELETE SOURCE_PACKAGE WHERE /BIC/C_WKTYP <> 'PIPING' .   
    DSO_PM14 DSO_PM18 DELETE SOURCE_PACKAGE WHERE /BIC/C_WKTYP <> 'INEL' .  Values from C_SCITKEY after the last "."
    DSO_PM14 DSO_PM20 DELETE SOURCE_PACKAGE WHERE /BIC/C_WKTYP <> 'INSULA'
                              OR /BIC/C_SCITKEY( 5 NE 'INSU1'  . 
    C_SCITKEY 
    DSO_PM14 DSO_PM21 DELETE SOURCE_PACKAGE WHERE /bic/c_wktyp <>  INSULA 
                              OR /bic/c_scitkey( 5 NE  INSU2   . 
    C_SCITKEY 
    DSO_PM14 DSO_PM22 DELETE SOURCE_PACKAGE WHERE /bic/c_wktyp <>  INSULA 
                              OR /bic/c_scitkey( 5 NE insu5 . 
    c_equnr+17( 1 ) 
    DSO_PM14 DSO_PM23 DELETE SOURCE_PACKAGE WHERE /BIC/C_WKTYP <> 'INSULA'
                              OR /BIC/C_EQUNR NE ''  . 
    Values from  /BIC/C_SCITKEY before the first "."
    DSO_PM14 DSO_PM24 DELETE SOURCE_PACKAGE WHERE /BIC/C_WKTYP <> 'LIFT' AND
        /BIC/C_WKTYP <> 'CLEAN' ) . 
    Values from  /BIC/C_SCITKEY before the first "."
    DSO_PM14 DSO_PM28     DELETE SOURCE_PACKAGE WHERE /BIC/C_WKTYP <> 'PIPING'
                              OR /BIC/C_SCITKEY( 5 NE 'PIPG1' AND
                              /BIC/C_SCITKEY( 5 NE 'PIPG2' )
                              OR /BIC/C_EQUCAT IS NOT INITIAL
                                    AND /BIC/C_EQUCAT NE 'A'
                                    AND /BIC/C_EQUCAT NE 'B'
                                    AND /BIC/C_EQUCAT NE 'F1'
                                    AND /BIC/C_EQUCAT NE 'F3'  . 
    C_SCITKEY
    DSO_PM14 DSO_PM29 DELETE SOURCE_PACKAGE WHERE /BIC/C_WKTYP <> 'PIPING'
                              OR /BIC/C_SCITKEY( 5 NE 'PIPG3'  )
                              OR /BIC/C_EQUCAT IS NOT INITIAL
                                    AND /BIC/C_EQUCAT NE 'M41'
                                    AND /BIC/C_EQUCAT NE 'M42'  . 
    C_SCITKEY
    DSO_PM14 DSO_PM30 DELETE SOURCE_PACKAGE WHERE /BIC/C_WKTYP <> 'PIPING'
                              OR /BIC/C_SCITKEY( 5 NE 'PIPG3'  )
                              OR /BIC/C_EQUCAT IS NOT INITIAL
                                    AND /BIC/C_EQUCAT NE 'M5'  . 
    C_SCITKEY
    ITB_ SCAFFOLDING.

    End routine:

    Transfert data from ITB_ SCAFFOLDING into result package.

    C_COMPDE comes from master data C_PMORDR if a correspondance is found, else c_compcde is empty.


    Reporting

    Main queries

    QueryDescription
    BW_QRY_MPR_PM05_002BW - GTBU SCAFFOLDING - Order Analysis (Core Query)
    BW_QRY_MPR_PM05_001BW - GTBU SCAFFOLDING - Scaf. Analysis (Core Query)
    BW_QRY_MPR_PM05_003BW - GTBU - Reactivity Analysis (Core Query)
    BW_QRY_MPR_PM05_004BW - GTBU INEL - Operations Analysis (Core Query)
    BW_QRY_MPR_PM05_005BW - GTBU INEL - Order Analysis (Core Query)
    BW_QRY_MPR_PM05_008BW - GTBU - Services Analysis (Core Query)
    BW_QRY_MPR_PM06_001BW - GTBU INSULA - Piping Analysis (Core Query)
    BW_QRY_MPR_PM06_004BW - GTBU INSULA - Global Analysis (Core Query)
    BW_QRY_MPR_PM06_003BW - GTBU INSULA - Misc. prices Analysis (Core Query)
    BW_QRY_MPR_PM06_002BW - GTBU INSULA - Devices Analysis (Core Query)
    BW_QRY_MPR_PM06_005BW - GTBU INSULA - Reactivity Analysis (Core Query)
    BW_QRY_MPR_PM06_006BW - GTBU INSULA - Services Analysis (Core Query)
    BW_QRY_MPR_PM05_009BW - GTBU LIFTING - Lifting Analysis (Core Query)
    BW_QRY_MPR_PM05_010BW - GTBU LIFTING - Mounting Analysis (Core Query)
    BW_QRY_MPR_PM05_011BW - GTBU LIFTING - Order Analysis (Core Query)
    BW_QRY_MPR_PM05_012BW - GTBU CLEANING - Cleaning Analysis (Core Query)
    BW_QRY_MPR_PM05_013BW - GTBU CLEANING - Extra-cost Analysis (Core Query)
    BW_QRY_MPR_PM05_014BW - GTBU CLEANING - Order Analysis (Core Query)
    BW_QRY_MPR_PM07_007BW - GTBU PIPING - Services Analysis (Core Query)
    BW_QRY_MPR_PM07_001BW - GTBU PIPING - Piping Analysis (Core Query)
    BW_QRY_MPR_PM07_003BW - GTBU PIPING - Welding Analysis (Core Query)
    BW_QRY_MPR_PM07_004BW - GTBU PIPING - Laying/Removal Analysis (Core Query)
    BW_QRY_MPR_PM07_005BW - GTBU PIPING - Support Analysis (Core Query)
    BW_QRY_MPR_PM07_002BW - GTBU PIPING - Order Analysis (Core Query)
    BW_QRY_MPR_PM07_006BW - GTBU PIPING - Reactivity Analysis (Core Query)

    Image Modified

    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

    GTBU

    Load GTBU data (PM)

    CR_PM06

    + sub chains

    Daily - not weekend.

    Arround 1:56 am

    Triggeredd by process chain RSP_DAILY

    20 mins

    GTBU_REACTIVITY

    Load GTBU execution reactivity

    CR_PM03Daily - not weekend.

    Arround 2;10 am

    Triggeredd by process chain GTBU

    2 mins

    GTBU_INEL

    Load GTBU INEL data (PM)

    CR_PM05Daily - not weekend.

    Arround 2;02 am

    Triggeredd by process chain GTBU

    3 mins

    GTBU_LIFTING

    Load GTBU LIFTING/CLEANING data (PM)

    CR_PM13Daily - not weekend.

    Arround 2;07 am

    Triggeredd by process chain GTBU

    1 mins

    GTBU_SCAFFO

    Load GTBU scaffolding data (PM)

    CR_PM02Daily - not weekend.

    Arround 1:57 am

    Triggeredd by process chain GTBU

    2 mins

    GTBU_PIPING

    Load GTBU piping data (PM)

    CR_PM26

    CR_PM25

    CR_PM04

    CR_PM27

    Daily - not weekend.

    Arround 2;00 am

    Triggeredd by process chain GTBU

     

    3 mins

    Load GTBU INSULA data (PM)

    CR_PM08

    CR_PM09

    CR_PM07

    CR_PM10

    Daily - not weekend.

    Arround 2;03 am

    Triggeredd by process chain GTBU

     

    3 mins

    GTBU_SOLVAY

    Load GTBU Solvay: data (PM)

    CR_PM19

    + sub chains

    Daily - not weekend.

    Arround 2:45 am

    Triggeredd by process chain RSP_DAILY

    20 mins

    GTBU_SOLVAY_REACTIVITY

    Load GTBU Solvay: execution reactivity

    CR_PM16Daily - not weekend.

    Arround 3:02 am

    Triggeredd by process chain GTBU_SOLVAY

    2 mins

    GTBU_SOLVAY_INEL

    Load GTBU Solvay: INEL data (PM)

    CR_PM18Daily - not weekend.

    Arround 2:50  am

    Triggeredd by process chain GTBU_SOLVAY

    2 mins

    GTBU_SOLVAY_LIFTING

    Load GTBU Solvay: LIFTING/CLEANING data (PM)

    CR_PM24Daily - not weekend.

    Arround 3:00 am

    Triggeredd by process chain GTBU_SOLVAY

    2 mins

    GTBU_SOLVAY_SCAFFO

    Load GTBU Solvay: Scaffolding data (PM)

    CR_PM15Daily - not weekend.

    Arround 3:00 am

    Triggeredd by process chain GTBU_SOLVAY

    2 mins

    GTBU_SOLVAY_REACTIVITY

    Load GTBU Solvay: execution reactivity

    CR_PM16Daily - not weekend.

    Arround 3:02 am

    Triggeredd by process chain GTBU_SOLVAY

    2 mins

    GTBU_SOLVAY_INSULA

    Load GTBU Solvay: INSULA data (PM)

    CR_PM22

    CR_PM23

    CR_PM21

    CR_PM20

    Daily - not weekend.

    Arround 3;00 am

    Triggeredd by process chain GTBU_SOLVAY

     

    2 mins

    GTBU_SOLVAY_PIPING

    Load GTBU Solvay: Piping data (PM)

    CR_PM29

    CR_PM28

    CR_PM30

    CR_PM17

    Daily - not weekend.

    Arround 3;00 am

    Triggeredd by process chain GTBU_SOLVAY

    2 mins
    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.