Data, Analytics & AI Platform

Page tree


Versions Compared

Old Version 9

changes.mady.by.user GIRAUD-ext, Mickael

Saved on

compared with

New Version 10

changes.mady.by.user GIRAUD-ext, Mickael

Saved on

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_M08

Plant Maintenance

Role menu for queries

ZR_RCS_PM_A02

Maintenance Orders Applications - End User role


ZR_RCS_PM_A03

Maintenance Orders Applications - Key User role


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

List of authorization objects mandatory for the application.

Authorization objectExplanation
C_COMPCDECompany: ZR_*_CA_P01

CPFCTR1_2

GBU: ZR_*_CA_P05

C_COMPCDE__C_AUTHMA

Authorization scope: ZR_*_CA_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

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)


For all transformations from DSO_PM01 → targets (DSO_PM02, DSO_PM04, DSO_PM05, DSO_PM07, DSO_PM08, DSO_PM09, DSO_PM10, DSO_PM1, DSO_PM25, DSO_PM26, DSO_PM27, DSO_PM11) C_COMPDE comes from master data C_PMORDR if a correspondance is found, else c_compcde is empty.


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. Key figures have differents rules in function of a specific field.

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.

DSO SourceDSO TargetSelective deletionField used in "case" to define the key figures
DSO_PM01 DSO_PM02Delete data where: C_EQUCAT is not empty and not equal to 0001, 0002, 0003, 0004, 0005 OR C_WKTYP nor equal to SCAFFO.C_SCITKEY
DSO_PM01 DSO_PM04Delete data where Cwhere C_WKTYP is different from 'PIPING'.C_SCITKEY
DSO_PM01 DSO_PM05Delete data where  C_WKTYP is different from 'INEL'.v_C_SCITKEY (end values of C_SCITKEY after the last ".")
DSO_PM01DSO_PM07Delete data where  C_WKTYP is different from 'INEL'.C_SCITKEY
DSO_PM01DSO_PM08DELETE SOURCE_PACKAGE WHERE ( /bic/c_wktyp <> c_insula
                          OR /bic/c_scitkey(5) NE c_insu2 ) . 		C_SCITKEY
DSO_PM01DSO_PM09DELETE SOURCE_PACKAGE WHERE ( /bic/c_wktyp <> c_insula
                          OR /bic/c_scitkey(5) NE c_insu5 ) . 		C_EQUNR 
DSO_PM01DSO_PM10 DELETE SOURCE_PACKAGE WHERE ( /BIC/C_WKTYP <> 'INSULA'
                          OR /BIC/C_EQUNR NE '' ) .		C_SCITKEY
DSO_PM01DSO_PM13DELETE SOURCE_PACKAGE WHERE ( /BIC/C_WKTYP <> 'LIFT' AND
    /BIC/C_WKTYP <> 'CLEAN'). 		C_SCITKEY
DSO_PM01DSO_PM25DELETE SOURCE_PACKAGE WHERE ( /BIC/C_WKTYP <> 'LIFT' AND
    /BIC/C_WKTYP <> 'CLEAN'). 		C_SCITKEY
DSO_PM01DSO_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_PM01DSO_PM27DELETE 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_PM01DSO_PM11DELETE SOURCE_PACKAGE WHERE /BIC/C_WKTYP <> 'COSTFE-


Transformation: DTS_PMESLL -> DSO_PM06:

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


Transformation DSO_PM14 -> ODSO DSO_PM32

DELETE SOURCE_PACKAGE WHERE /BIC/C_WKTYP <> 'COSTFE'. 

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


Transformation: 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'. 

case  C_SCITVAL

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


Transformation: DSO_PM14 -> DSO_PM17

DELETE SOURCE_PACKAGE WHERE /BIC/C_WKTYP <> 'PIPING'. 

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


Transformation: DSO_PM14 -> DSO_PM18

  DELETE SOURCE_PACKAGE WHERE /BIC/C_WKTYP <> 'INEL'. 

v_VALUE_TYPE  (end values of C_SCITKEY after the last ".")

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


Transformation: DSO_PM14 -> DSO_PM20

DELETE SOURCE_PACKAGE WHERE ( /BIC/C_WKTYP <> 'INSULA'
                          OR /BIC/C_SCITKEY(5) NE 'INSU1' ) . 

case  C_SCITKEY 

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


Transformation: DSO_PM14 -> DSO_PM21

DELETE SOURCE_PACKAGE WHERE ( /bic/c_wktyp <>  INSULA 
                          OR /bic/c_scitkey(5) NE  INSU2  ) . 

c_scitkey

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


Transformation: DSO_PM14 -> DSO_PM22

   DELETE SOURCE_PACKAGE WHERE ( /bic/c_wktyp <>  INSULA 
                          OR /bic/c_scitkey(5) NE insu5 ) . 

case  c_equnr+17(1) 

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


Transformation: DSO_PM14 -> DSO_PM23

    DELETE SOURCE_PACKAGE WHERE ( /BIC/C_WKTYP <> 'INSULA'
                          OR /BIC/C_EQUNR NE '' ) . 

case frists value from  /BIC/C_SCITKEY before "."

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



Transformation: DSO_PM14 -> DSO_PM24

   DELETE SOURCE_PACKAGE WHERE ( /BIC/C_WKTYP <> 'LIFT' AND
    /BIC/C_WKTYP <> 'CLEAN'). 

case frists value from  /BIC/C_SCITKEY before "."

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



Transformation: 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' ) ) . 

case  C_SCITKEY SCITKEY 

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


Transformation: 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' ) ) . 

case  C_SCITKEY SCITKEY 

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



Transformation: 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' ) ) . 

case  C_SCITKEY SCITKEY 

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




Transformation: DTS_PMESLL -> DSO_PM19

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



Transformation: DTS_PMESLL -> DSO_PM06

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 

Main Process
Chain GTBU 
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

  • 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

    CR_PM0310 2 GTBU_INEL INEL PM0502 LIFTING LIFTING/CLEANING PM13;07 GTBU1
    Main Process ChainFinal Provider LoadingFrequencyTime startDuration

    GTBU

    Load GTBU data (PM)

    		CR_PM06+ sub chainsPM02Daily - not weekend.

    Arround 1:56 57 am

    Triggeredd by process chain RSP_DAILY

    		20 mins

    GTBU_REACTIVITY

    Load GTBU execution reactivity

    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_SCAFFOREACTIVITY

    Load GTBU scaffolding data (PM)Solvay: execution reactivity

    		CR_PM02PM16Daily - not weekend.

    Arround 13:57 02 am

    Triggeredd by process chain GTBU_SOLVAY

    		2 mins

    GTBU_SOLVAY_INEL

    Load GTBU Solvay: INEL data (PM)

    		CR_PM19+ sub chainsPM18Daily - not weekend.

    Arround 2:45 50  am

    Triggeredd by process chain RSPGTBU_DAILYSOLVAY

    		20 2 mins

    GTBU_SOLVAY_REACTIVITYLIFTING

    Load GTBU Solvay: execution reactivityLIFTING/CLEANING data (PM)

    		CR_PM16PM24Daily - not weekend.

    Arround 3:02 00 am

    Triggeredd by process chain GTBU_SOLVAY

    		2 mins

    GTBU_SOLVAY_INELSCAFFO

    Load GTBU Solvay: INEL Scaffolding data (PM)

    		CR_PM18PM15Daily - not weekend.

    Arround 23:50  00 am

    Triggeredd by process chain GTBU_SOLVAY

    		2 mins

    GTBU_SOLVAY_LIFTINGREACTIVITY

    Load GTBU Solvay: LIFTING/CLEANING data (PM)execution reactivity

    		CR_PM24PM16Daily - not weekend.

    Arround 3:00 02 am

    Triggeredd by process chain GTBU_SOLVAY

    		2 mins

    GTBU_SOLVAY_SCAFFOINSULA

    Load GTBU Solvay: Scaffolding INSULA data (PM)

    CR_PM22

    CR_PM23

    CR_PM21

    CR_

    PM15

    PM20

    		Daily - not weekend.

    Arround 3:;00 am

    Triggeredd by process chain GTBU_SOLVAY


    		2 mins

    GTBU_SOLVAY_REACTIVITYPIPING

    Load GTBU Solvay: execution reactivityPiping data (PM)

    CR_PM29

    CR_PM28

    CR_PM30

    CR_

    PM16

    PM17

    		Daily - not weekend.

    Arround 3:02 ;00 am

    Triggeredd by process chain GTBU_SOLVAY

    		2 mins


    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.

    Powered by Atlassian Confluence and Brikit Theme Press