Access Management
List of application role + menu role and explanation if we have several applications role with specials rules.
| Role Code | Role Description | Explanation |
|---|---|---|
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:
|
ZBI_RCS_CO_A21 | CBS Project costs Reporting Analysis - End User role | Application Role:
|
- 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 object | Explanation |
|---|---|
| 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__C_FAMIL;C_WBS_ELE__C_FAMIL | Family, 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:
- Master Data C_PMORDR (Work Orders Master Data)
- 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 Source | DSO Target | Selective deletion | Field 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. | 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 | - |
Transformation: DTS_PMESLL -> DSO_PM06:
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
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
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
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
- List of BEx Reports & Workbooks : CATALOG - Industrial & Planning Reporting (in the tab Maintenance, Category = GTBU)
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 Chain | Final Provider Loading | Frequency | Time start | Duration |
|---|---|---|---|---|
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.