Specify allocations for different purposes, such as distributing expenses based on department headcount. Conduct allocations on any dimension of your data model.
Anaplan Financial Consolidation allocations comprise four elements: Source, Driver, Target, and Offset. Set up multiple allocations and use the goal of one allocation to affect another by choosing the allocation order.
Allocations can be performed on any dimension within the data model.
Multiple allocations can be defined where the target of one allocation can be used to drive another allocation.
Allocations can be processed in a given order, which is set when the allocation rules are created.
Drivers can be existing Trial Balance accounts, such as Revenue. They can be statistical accounts, such as headcount, square footage, or percentages. These statistical drivers can be input using the details section or imported via another Extract, Transform, and Load (ETL) solution.
You can begin by setting up your Allocation rules.
Configure Allocation Rules
Allocation definitions
Navigate to the Maintain module and select Allocations from the Calculations card to open Allocations. This enables you to create new allocations in your consolidation application.
To create a new Allocation, select the Create icon from the toolbar menu and configure the fields:
| Column | Value |
| Allocation | Specify the name of your allocation and it must be under 100 characters in length. |
| Model | Specify the name of the model that you want to run the allocation against. You can select from a list of all models for your tenant. |
| Allocation Order | Specify the order value. If you have many allocations in your system, the Allocation Order lets you select the order in which the allocations will run. The value for Allocation Order is an integer, where 1 represents the first allocation run. Allocation order is important if you have an allocation where the source is based on the result of a previous allocation's target calculation. |
| Allocation Dimension | Specify which dimension in your system will be used as the basis for the allocation. You can specify alternate hierarchies. For example, if you select Entities as your Allocation Dimension, the defined allocation will take the values from your defined source Entity and be able to spread it across a range of Target Entities. |
| Sort Order | Specify the sort Order, which is a numeric value that defines the order the allocations will be displayed in the Allocation form. The sort order has no impact on the allocations run order. |
Once the Allocation rule has been defined, select the Details checkbox beside the allocation to define the allocation details.
Allocation Details
Define configurable allocation parameters in the Allocation Details section by selecting the Create icon on the Details toolbar. Allocations within the system are comprised of four parts:
| Column | Value |
| Source | Select the intersection that defines the source data to be used in the allocation. |
| Driver | Specify the intersection that defines the driver to be used in the allocation. This defines the pattern to be applied to the source intersection to calculate the target value. |
| Target | Specify the intersections that define the target of the allocation. This is the destination intersections where the calculated output of the allocation is submitted. The target for the Allocation Dimension can have a one-to-many relationship with the source. This means that data from one source intersection can be spread to many data points in the target. |
| Offset (Optional) | If defined, Offset value is used to back out the Source amount from the Target of the allocation. This is used to avoid double-counting the source amount once the allocation has been performed. In general, the operator for the offset is set to Negative. Operators for Source, Driver, and Target are normally set to Positive. |
| IsPeriodic | This determines if the Allocation will use data from the YTD (Amount) or Periodic measure.
Note that data should only be stored in the periodic measure if the Scenario that is being allocated on is a periodic scenario, that is if |
Each allocation defined can only have one Source, Driver, Target, and Offset defined.
If multiple targets or sources are required, separate allocations must be created. Once your allocations have been defined, select the Save icon.
