List of application role + menu role and explanation if we have several applications role with specials rules.
|
List of authorization objects mandatory for the application.
|
Data is extracted from standard extractors from system WP1 400: 2LIS_17, 0PM_OM_OPA_1 & 2, 0CA_TS_IS_1
Dependencies:
Functional Rules:
Transformations for CUB_PM001 CUB_PM001 IFS_0PM_OM_OPA_1:
Start routine:
Fields ABCINDIC (ABC indicator) and C_OBJTYPE (Object Type (equip)) comes from view /BI0/MEQUIPMENT if a corrspondance is foundwith the equipment, else comes from view /BIC/MC_FUNCLOC.
Infopackages are filtered on CURTYPE = 10 & 0VTYPE between [020;030] and [050;090] with differents periods.
Transformation TRSF: ODS_PMEN -> CUB_PM001:
C_FUNCLOC (functional location) / 0WAPRL (Maitenance plan) / C_WAPOS (maintenance plan item) & 0NOTIFICATN (Notification number) come from master data C_PMORDER.
C_COSTCENTER equal M if field C_MATNR is not empty.
C_EBELN (Purchase order number) → if ref_doc_ct (Reference Document: Type) = 020 then field equal ref_doc_nr (Reference Document Number (External Document Number)).
C_EBELP (Item Number of Purchasing Document) → if ref_doc_ct (Reference Document: Type) = 020 then field equal ref_doc_it (Reference document item).
C_DINPD (Item number purchase document description)→ if ref_doc_ct = 020 then field equal C_DINPD.
Fields ABCINDIC (ABC indicator) and C_OBJTYPE (Object Type (equip)) comes from view /BI0/MEQUIPMENT if a corrspondance is foundwith the equipment, else comes from view /BIC/MC_FUNCLOC.
DTP - ODS_PMEN -> CUB_PM001 : filters currency type = 10 and semantic group on CURTYPE / METYPE / VTYPE / FISCVARNT / MATL_GROUP / DB_CR_IND / CREDITOR / VTSTAT / VTDETAIL / VERSION / COSTELMNT / COMP_CODE / CO_AREA / FISCPER / /BIC/C_EKORG / /BIC/C_EKGRP.
Transformation: TRSF : 0PM_OM_OPA_2 -> ODS_PM01 (Rhodia)
Fields 0PART_CCTR (Partner Cost Center), 0PART_ACTTY (Activity Type of Partner Cost Center), 0PART_COORD (Partner Order), 0PART_WBSEL (Partner WBS Element), 0PART_ABCPR (Partner Business Process) are determined with module function CO001_BIW_PARTNER_DECODE with input parameter rspobart (Partner (short)) & rsparobval (Partner IO val.)
DTP : 0PM_OM_OPA_2 -> ODS_PM01 (Delta): semantic group on KOKRS, BELNR, BUZEI, FISCVAR, FISCPER and CURTYPE.
Transformation RSDS 2LIS_17_I3OPER WP1_400 -> ODSO ODS_PM04:
C_PM_USST (C_PM_USST User Status.) comes from master data C_PMORDER (field ZZISTAT).
C_SYSTATS (Detailed System Status.) comes from master data C_PMORDER (field ZZESTAT).
Transfer rule CUB_PM004 8ODS_PM04:
Fields ABCINDIC (ABC indicator) and C_OBJTYPE (Object Type (equip)) comes from view /BI0/MEQUIPMENT if a corrspondance is foundwith the equipment, else comes from view /BIC/MC_FUNCLOC.
| Query | Descriptions |
|---|---|
| BW_QRY_MPR_PM001_0001_BCAST | BW - PM Monthly Synthetic Expenses (BROADCAST) |
| BW_QRY_MPR_PM001_0030 | BW - PM Cumulated (year) detailed costs (Core query) |
| BW_QRY_MPR_PM001_0030_2 | BW - PM Cumulated (year) detailed costs (Core query) |
| BW_QRY_MPR_PM001_0031 | BW - PM Monthly costs synthetic report (Core query) |
| BW_QRY_MPR_PM001_0031_MPI1 | MPI 1 - Maintenance Costs per ton of production |
| BW_QRY_MPR_PM001_0031_MPI4 | MPI 4 - Structure of Maintenance Costs |
| BW_QRY_MPR_PM001_0033 | BW - PM Material consumptions per order (Core query) |
| BW_QRY_MPR_PM001_0034 | BW - PM Orders list by vendor (Core query) |
| BW_QRY_MPR_PM001_BCAST_0001 | BW_QRY_MPR_PM001_BCAST_0001 |
| BW_QRY_MPR_PM001_BCAST_0001 | Extraction Oracle 2019 |
| BW_QRY_MPR_PMECO_0001 | BW - Emergency WOs |
| BW_QRY_MPR_PMECO_0002 | BW - Past Due PM |
| BW_QRY_MPR_PMECO_0003 | BW - MTBF Rotating Equipment |
| BW_QRY_MPR_PMECO_0004 | BW - MTBF |
| BW_QRY_MPR_PMECO_0005 | BW - Backlog Maintenance Metrics |
| MPR_PM003_QRY005 | General Control of Preventive Maintenance (Quantities) |
| QV_BW_QRY_MPR_PM001_0030 | QV-BW-PM Cumulated (year) detailed costs (QV) |
| QV_BW_QRY_MPR_PM001_0031 | QV-BW-PM Monthly costs synthetic report (QV) |
We should have the information where the application is sending or receiving information (e.g. APD open hub)
Detail of process chain, list + link between or special event done for the loading
| Main Process Chain | Final Provider Loading | Frequency | Time start | Duration |
|---|---|---|---|---|
RSP_PM Plant Maintenance | CUB_PM001 CUB_PM002 CUB_PM003 CUB_PM004 CRFICCS01 | Daily (not saturday) | Arround 1:15 am | 45 mins |
Infoproviers and Master data are grouped in the Application Area AREA_PM.
Process Chains included in the Global RSP_DAILY Process Chain:
Others Process Chains:
The main process chain RSP_PM run in about one and a half hours.
PM Extractors (2LIS_17) are set up in delta with a delta queue. Costs on PM orders are loaded in full mode.
We keep all the data in the DSO and Cubes. Archiving is done on Source System.
<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)>
<Describe the scheduling in place for the application (eg. existing jobs, trigger time/event based, dependencies)>
<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)>
<Describe how to handle errors (eg. error codes, description and respective resolution, alert users)>
<List the existing bugs, its criticity, workarounds and resolution plan.>
<List past & future evolutions for the application (including links to MED/FSD/TSD)>