Functional and Technical rules
Rules & Explanations
This flow allows to calculate the Cash 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:
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
Key Figure | Estimation |
|---|---|
| ~ Average Process Chain Runtime | |
| ~ Average nb of rows loaded per load | |
| ~ Total nb of rows loaded (if full) | |
| ~ Average Runtime for 10k lines |