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_M15 | ER - Environmental & Rehabilitation expenses analysis | Role menu |
ZBI_RCS_CO_A23 | Project Costs and Structures Analysis - End User role | Application Role |
List of authorization objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
C_COMPCDE__C_MNGAREA | roles ZR_*_CA_P08 |
C_BFCSITE | roles ZR_*_CA_P13 |
| CPFCTR1_2 | roles ZR_*_CA_P05 |
| C_COMPCDE__C_AUTHMA | roles ZR_*_CA_P01 |
DataFlow
Overview
Technical Rules on Workbench
Datasources / IP:
IP: 0CO_OM_OPA_7 - RCS - delta(ZPAK_52NV2OPK3T4OHROVSC9O6AVCA) / I P: 0CO_OM_OPA_7 - Solvay - Delta(ZPAK_52OMT6EQ7ZPOM3RQWGPVOUT62) / 0CO_OM_OPA_6 - delta (ZPAK_3RK9PYPD9FI1T5F1U607BRFVW)Filter on currency type = 10 and 20
Transformations
ODSO DPCOOP01 -> ODSO DBCOOP01 / ODSO DPCOOP02 -> ODSO DBCOOP02 /
Start routine
Select data from master data global filter for stream 'CO' and rule ' C_CE_SCOP' into internal table g_rg_ce_scop_ord_typ.
Field routines
C_CREDID: if source field C_CREDID ( creditor from standard field LIFNR ) is not empty take it, else take source field C_VENDPO ( vendor of the purchase order ).
C_CE_SCOP: If internal table " g_rg_ce_scop_ord_typ" is not empty and source field C_CORDTYP is present in this table, C_CE_SCOP = source field costelmnt (else empty).
Transf: 0CO_OM_OPA_6 -> ODS6OPA6
Partner IO (RSPAROBVAL) & Partner (RSPOBART) are used with module function "CO001_BIW_PARTNER_DECODE" to determine fields Partner cost center (0PART_CCTR) & Activity Type of Partner Cost Center (0PART_ACTTY) & Partner Business Process (0PART_ABCPR).
Module funciton CO001_BIW_PARTNER_DECODE source code :
DTPs:
DTP : ODS_OPA6 -> CRCOOP03 - Delta: Filter with routine on C_CORDTYP with list defined in master data global filter stream = CRCOOP03 & rule = C_CORDTYP.
DTP: ODS6OPA6 -> CRCOOP04 - Delta: Filter with routine on C_CORDTYP with list defined in master data global filter stream = CRCOOP04 & rule = C_CORDTYP.
DTP: 0CO_OM_OPA_6 -> ODS6OPA6 - Delta: doc date >= 01.01.2000 & Partner IO <> YQ-CIV-701-MTOOL-Х6232!N. Semantc group on fields KOKRS / BELNR / BUZEI / FISCVAR / FISCPER.
Reporting
BW_QRY_MVCOOP01_0001 - BW - Environ. & Rehab. expenses (Core Query)
BW_QRY_MVCOOP01_0002 - BW - E&R database (Core Query)
QV_BW_QRY_MVCOOP01_0002 - BW - E&R database (Core Query)
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
Detail of process chain, list + link between or special event done for the loading
| Main Process Chain | Final Provider Loading | Frequency | Time start | Duration |
|---|---|---|---|---|
CO OM OPA : TD - D - Commitments - RCS PC_CO_OM_OPA_02 | CRCOOP01 | Daily | 1:25 am | 2 mins |
CO OM OPA : TD - D - Commitments - Solvay PC_CO_OM_OPA_01 | CRCOOP02 | Daily | 2:35 am | 3 mins |
CO OM OPA : TD - D - Actual - ER - RCS PC_CO_OM_OPA_03 | CRCOOP03 | Daily | 1:25 am | 2 mins |
CO OM OPA : TD - D - Actual - ER - Solvay PC_CO_OM_OPA_04 | CRCOOP04 | Daily | 2:35 am | 3 mins |
Data Quality Control
Data come from SAP system. To compare data between BW and sources systems, check propagation layers.
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
<List past & future evolutions for the application (including links to MED/FSD/TSD)>