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/1MtvRBM_MWLRO7SN35f-dg_9iw5ONBv4m3BHxqOltmVE/view
Technical Rules on Workbench
This flow, based on CO WBS standard datasources, is the source for the budget, commitments, actual costs and hours key figures in the Project Costs Reporting. Note that commitments and actual costs are also completed by data from PM extractors (cf. WBSE - PM orders costs section).
Moreover, a specific datasource extracts data from COEPD table to enhance the cubes with the capitalized value (fixed assets).
Capitalized value determination - COEPD dataflow (Solvay & Rhodia) (R1):
Transformation: DSOCOEPD -> ODS_WBS6:
The Capitalized value is issued from SAP table COEPD, where original PS documents are updated (Settlement status = 09) when AuC linked to the WBSE is put into service (transfer AuC -> FXA).
Extraction from COEPD is done using a specific datasource based on Function Module ZFM_BW_EXTRACT_COEPD.
Three FULL infopackages run daily:
Current year + last year (based on the posting date COEPD-ABWDA): it was considered that a settlement can’t occur on a past year but the last year is also extracted to not miss the changes done on the last day of the year (December 31)
Posting date = “00000000”
Reversal indicator = “X”: allow to retrieve cancellations on past years
Partner object mapping (R2):
TRSF : 0CO_OM_WBS_6 -> ODS6WBS6 (Solvay)
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.
However, in Solvay ECC (PF1), some costs are defined at PM order operation level. When it happens, and that these costs are distributed to WBSE, the partner type is "0ACT".This partner type is not managed in the Function Module 'CO001_BIW_PARTNER_DECODE' so a specific rule is set to map the Partner Order from the generic partner field: we keep the 12 first characters and check in C_COORDER MD that it corresponds to a real order number.
Datasources customer exit:
- 0CO_OM_WBS_6: retrieve additional data from tables EKKO, CATSDB, COEPD and COEP. The field zzmbgbtr = COEP-mbgbtr is used to obtain the project hours concerning Networks settlements on WBSE (partner object type = "0NWA").
- 0CO_OM_WBS_7: 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
Fixed Costs Analysis: Actual costs DSO are sources for the cube CUB_FC002/005/006.
Data loadings
Info providers and objects loaded
Process Chain | Code | Type | Frequency | Comments |
|---|---|---|---|---|
| CO_OM_OPA / WBS - delta extraction | RSP_COOM | MAIN |
|
|
| CO_OM_OPA / WBS - delta extraction for non RCS systems | RSP_COOM_OTHER | SLAVE |
|
|
| Weekly chain for CO and WBS budget (Non RCS) | RPC_CO_WBS_BUDGET_NO_RCS | MAIN |
|
|
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.>