The new wiki link for this data flow is here:
Please update the doc there and no longer here.
| Table of Contents |
|---|
Functional and Technical rules
Rules & Explanations
This flow allows to calculate the Cash , based on CO WBS standard datasources, is the source for the budget, commitments, actual costs and hours key figures in the Project Costs Reporting. It corresponds to the paid amounts on WBS Elements, calculated according to BFC CAPEX definition.
The assignement of FI AP (vendor) entries to WBSE is performed in BW (and/or datasource exit in ECC) according to the assignment on counterpart P&L entries in the same FI document.
Dataflow:
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).
Dataflow:
https://drive.google.com/open?id=1Yae-yS1-Y0CnA01yVnqdue9_3VLmk-66X2j17jRJOJ0
WBS element determination according to the PM orders (R3 & R6):
Deletion of existing lines in the DSO DBFIPA* (R3 & R6):
As the WBS element is part of the key of the DSO, if, for any reason (change in PM order settlement rules for instance), the determined WBS element for an accounting document item has changed, the key on the old WBS element still remain and a new key is created which would lead to false result and duplicated amounts.
In consequence, before to update a document item in the DSO, the existing lines on this document item in the DSO are deleted by creating new entries in the datapackage with recordmode = "D".
In FIAP flows, an accounting document item can be split by several characteristics and in FIGL Rhodia, a document item can be split by profit center. In consequence, if not all the lines of a document item are processed in the same datapackage, only the keys in the last package would remain. To avoid that problem, a "Semantic Group" is defined in the DTP to ensure that all lines of a document item are processed in the same datapackage (it also implies that all lines of a same document item must be change at the same time in the source DSO).
Dependencies with other applications
Data loadings
Info providers and objects loaded
Loading frequency
Average performance
/file/d/1ekxaEuJ1VwDbGcOdpl8pey1F6Uw6lY0ugsSaN184lKk/view
Capitalized value determination - COEPD dataflow (Solvay & Rhodia) (R1):
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):
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.
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
Main Chains
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 |
|
|
Loading frequency
Actual Costs = daily Delta
Commitments = daily Full with deletion
Budget = weekly Full with deletion (Acetow & Solvay), daily Full with deletion (Rhodia)
Average performance
Key Figure | Estimation |
|---|---|
| ~ Average Process Chain Runtime |
Daily RCS = 2h Daily non RCS = 2h Weekly non RCS = 2h |
| ~ Average nb of rows loaded per load |
| ~ Total nb of rows loaded (if full) |
| ~ Average Runtime for 10k lines |
Record Keeping
All records