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=1ylatRLT_As12qGU0ZRyWkuZD5aRce-oF3-uSz9FIOKw

FIWC relevant rules for Project Costs (cf. FIWC documentation: https://wiki.solvay.com/x/ZqA_AQ) :

• Net due date management (R1)

• Reclassification of Sub-Activity C_SUBACT2 (R1)

• FIAP Split (R1)

• Additional determination of WBS Element by look-up in P&L items (R2)

• Net of Tax amounts calculation (Solvay)

WBS element determination according to the PM orders (R3 & R6):

Only line items that could be linked to WBS elements are updated in the target DSO.

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).

Net Of Tax amounts calculation (Rhodia) (R4):

For Rhodia, Net of Tax amounts (K_NOTXLC and K_NOTXDC) are determined in the transformation between DBFIAP01 and DBFIPA02.

 It corresponds to the sum of the amounts of the non "K" items on the accounting document that are affected to the same Purchage Order item (even if empty), same WBS element and CO order. 

This is done by a look up in the DSO ODSFIGL3.

Net Of Tax amounts can be correctly determined only if the FIAP item is split by PO item. As the Rhodia FIAP split by PO item was done in 2016 and that FI documents before 2013 were archived in WP1,

Net Of Tax amounts are not calculated for year < 2013. 

Clearing date review for Korean Payment Card (Rhodia) (R5)

In Project Costs reporting, an invoice is considered as paid at the time of the clearing date. 

 Korean Payment Card (KPC) is a payment method with specific posting schema (on Payables side):

the invoice is cleared by a debt transfer posting (document type = "ZP") but it should be considered as paid at the time of the debt transfer clearing by a payment posting.

Example:

In a transformation from DSO DBFIPA02 to itself, for all documents (<> "ZP") that are cleared by a "ZP" document, a look up is done in the clearing document in DSO DBFIAP01. The initial clearing date is changed to the clearing date of the clearing document item with CGS code (sp_gl_ind) = "B". A "FULL" load is needed as the invoice is not updated when the ZP document is cleared.

Only documents from Rhodia source system are concerned.

Data loadings

Info providers and objects loaded

Main Chains

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

Record Keeping

All records