Access Management
List of application role + menu role and explanation if we have several applications role with specials rules.
| Role Code | Role Description | Explanation |
|---|
List of authorization objects mandatory for the application.
| Authorization object | Explanation |
|---|
DataFlow
Overview
https://drive.google.com/file/d/1Am47Dk54BTT-vbQCe0vPnYNwAdBC8ORTrIfHv8Kz7Ao/view
Technical Rules on Workbench
This flow, based on CO PM standard datasources, completes commitments and actual costs key figures in the Project Costs Reporting.
The assignment of these costs on WBS elements is done in BW.
WBS element determination / split (R1 & R4):
In Commitments dataflow:
TRSF : DPPMCS02 -> DBFICS04 (Solvay) & TRSF: ODS_PMEN -> DBFICS02 (Rhodia)
Solvay / Rhodia :
The rule consists to split the costs on the PM orders according to the distribution rules on WBS Elements in table COBRB (Extracted to DSO DSSCOBRB (Solvay) and DSRCOBRB (Rhodia)):
We look for settlement type "Per" (by period) and, if there is no, we look for settlement type "GES" (cumulatively). The planned delivery date (scl_deldat) must be contained in the validity period of the distribution rules (COBRB-GABJA (Valid-from year) and COBRB-GBISP (Valid-to year)).
The CO original line is duplicated for each line in table COBRB where a WSB Element is filled applying the settlement percentage rate to the amount in a new ratio K_settlmt (the original amount (0amount) is conserved as it was in the first line of the split and is cleared in the other).
Solvay / Rhodia :
The rule consists to split the costs (and the quantities) that are posted on the PM orders according to the costs (and the quantities) that are transferred from the PM orders to the WBS Elements (We want to keep only the costs that are transferred to WBSE but to preserved the detailed on the primary costs that are lost at the time of settlement on WBSE):
We filter on the costs sent to the PM orders (PM order is the receiver = db_cr_ind "S").
These costs are split (in a new ratio K_settlmt) on each WBS Element for which costs are transferred from the PM order during the period.
Partner object mapping (R3):
Partner objects are mapped from a generic field "Partner IO val" (RSPAROBVAL) to specific infoobjects "Partner Costs center" (0PART_CCTR), "Partner WBSE" (C_PARTWBS), "Partner Order" (C_PARTORD),... according to the partner type (RSPOBART). It is done using the Function Module 'CO001_BIW_PARTNER_DECODE' as provided by the SAP Business Content.
Datasources customer exit:
- 0PM_OM_OPA_2: retrieve additional data from tables EKKO, EKPO, COEP and AUFM. The quantity "SMEG" is redetermined with the quantity of the goods movements (table AUFM).
- 0PM_OM_OPA_3: retrieve additional data from tables EKKO, EKPO, EBAN.
It also determines an adjusted net due date (zznetdt) that corresponds to the delivery day (or the current date if the delivery date < current date) to which is added the terms of payment.
Reporting
Dependencies with other applications
Plant Maintenance: Actual and commitments costs propagation DSO are sources for PM application flow (Solvay and Rhodia).
Data loadings
Info providers and objects loaded
Process Chain | Code | Type | Frequency | Comments |
|---|---|---|---|---|
| Plant Maintenance | RSP_PM | SLAVE |
|
|
| Solvay : Plant Maintenance | RSP_PM_SOLVAY_ | SLAVE |
|
|
| Acetow : Plant Maintenance | RSP_PM_ACETOW | SLAVE |
|
|
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.>
