Co$ta - Destination View
>> Back to the Co$ta project home page
Access the query
The query to be used is BW_QRY_CPCOCT05_0001 – Cost Transparency – A destination view (POC)
=> Go to Analysis for Office in excel
=> Click "Open Data Source"
Go to the tab "Search" and enter "BW_QRY_CPCOCT05_0001" in the search bar.
Double-click on the query to open it
Run the query
Enter the same value in the prompt as the Origin view
For the release 4, the test is done with a period = 01.2020
Click OK
Change the lay-out
In columns select:
- Actual Origin - Legal view (Conv)
- Actual Destination - Legal view (Conv)
Raws
- Cost Center (exclude non allocated cost centers
- Actual origin: Costs at origin corresponds to the standard Costa view.
- Actual Destination is the amount that BW is able to allocate to a GBU / a BFC account after all settlements of the cost center.
Normally costs should be allocated at 100% and "Actual origin" should be equal to "Actual destination" => Case A
When it is not the case (Case B), a deeper investigation should be done to better understand what happens
At this stage:
- BW takes only into account the allocation to the P&L. So when one part of the cost center is allocated to a WBS Capex or Invoicing, it can explain why the allocation of the cost center is lower than 100%
Other issues should be reported in 10525 R4 TPL - Destination view:
Analysis
There are 6 new dimensions that were created for the destination view.
You can add:
- Destination - BFC Global Business Unit
- Destination - Magnitude Account
to perform a deeper analysis
The cost center SM16102048 is fully allocated to the GBU CBS & BFC account = R33400
The cost center SM16111090 is partially allocated to the GBU CBS & BFC account = R33400
62 462,09 € is not allocated
In PF1, open the cost center report S_ALR_87013611 to display the cost center SM16111090
The amount that is not allocated (62 462,09 €) is the alllocation doone with the cost element 9161000022
Double-click on the amount. This allocation is done to Networks
=> it is something that is not taken into account yet in the destination view and can be reported in the file
