- SAP Managed Tags:
This blog post is the fourth part of a blog post series with the intent to serve as a guide towards success with allocations in the SAP Analytics Cloud. It is complementary to the Webinar “Getting the Most out of Allocations with the SAP Analytics Cloud”.
To view the introduction with an overview of SAP Analytics Cloud allocations and other blog posts in the series, please click here.
Scenario: Your IT Department has been collecting costs for the entire organization since the beginning of the year. After quarter 1 ends, you want to simulate the allocation based on the headcount values stored in your plan version. In order to do this simulation, we can use a calculated account for the driver.
Create the Calculated Account:
In our account dimension, we can create a new member to use as our driver. In this member, we add a member formula:
Allocation Process:
Create an allocation step with a source dimension and target dimension of entity. We will need to specify our accounts that we want to allocate in the “Filter by Accounts” options.
Create the Allocation Step:
Create an allocation step to and from the Entity dimension, and check the boxes to "Keep Source and "Overwrite Target"
We are still filtering on our expense accounts in this example.
Allocation Rule:
Once we create the Allocation Step, we can add the details to the Allocation Rule. For this rule, we have specified the Cost Collector (our IT department) as the source entity (sender), Plan headcount as the driver (calculated account) and the parent node All Portfolios as the target entities (receiver)
Source Data:
On our source data, we will focus on the EXP1 line for January - we want to allocate out $62,500.
Headcount (Driver) Data:
When the system runs the allocation, it will calculate the amounts each Entity receives based on the data stored against headcount data. In our example, if we focus on January, P1_L will receive 20% of the costs incurred on the Cost Collector (20/100=10%). Notice that the version of this headcount data is Plan V1 which is what we are looking up in our calculated account. So, even when we run the allocation on the "Allocs" version, the driver values will come from the Plan V1 version.
Run Allocation:
We run the allocation using the "Execute Allocation Process" button in the story menu:
Results:
Once we run the allocation, we can check the results. If we focus on P1_L for January, we can see that 20% of $62,500 was allocated correctly. Please see calculation below.
Calculation:
Source Amount for Cost Collector/Input/Jan: $62,500
P1 Large/HC/Input value: 20/100= 0.2
$62,500 *0.2 = $12,500
To view the introduction with an overview of SAP Analytics Cloud allocations and other blog posts in the series, please click here.
Scenario: Your IT Department has been collecting costs for the entire organization since the beginning of the year. After quarter 1 ends, you want to simulate the allocation based on the headcount values stored in your plan version. In order to do this simulation, we can use a calculated account for the driver.
Create the Calculated Account:
In our account dimension, we can create a new member to use as our driver. In this member, we add a member formula:
Allocation Process:
Create an allocation step with a source dimension and target dimension of entity. We will need to specify our accounts that we want to allocate in the “Filter by Accounts” options.
Create the Allocation Step:
Create an allocation step to and from the Entity dimension, and check the boxes to "Keep Source and "Overwrite Target"
We are still filtering on our expense accounts in this example.
Allocation Rule:
Once we create the Allocation Step, we can add the details to the Allocation Rule. For this rule, we have specified the Cost Collector (our IT department) as the source entity (sender), Plan headcount as the driver (calculated account) and the parent node All Portfolios as the target entities (receiver)
Source Data:
On our source data, we will focus on the EXP1 line for January - we want to allocate out $62,500.
Headcount (Driver) Data:
When the system runs the allocation, it will calculate the amounts each Entity receives based on the data stored against headcount data. In our example, if we focus on January, P1_L will receive 20% of the costs incurred on the Cost Collector (20/100=10%). Notice that the version of this headcount data is Plan V1 which is what we are looking up in our calculated account. So, even when we run the allocation on the "Allocs" version, the driver values will come from the Plan V1 version.
Run Allocation:
We run the allocation using the "Execute Allocation Process" button in the story menu:
Results:
Once we run the allocation, we can check the results. If we focus on P1_L for January, we can see that 20% of $62,500 was allocated correctly. Please see calculation below.
Calculation:
Source Amount for Cost Collector/Input/Jan: $62,500
P1 Large/HC/Input value: 20/100= 0.2
$62,500 *0.2 = $12,500
3 Comments
