Custom Splitting on Periods
The Custom Splitting on Periods can be run from the process cockpit, “Detail summary” tab, by clicking on “Data operations” in the “Actions” panel.
The definition of a Custom splitting on Periods is available only if the user has administrator rights.
When it is necessary to define periodic data of one or more accounts from the cumulated data read from a given period, in CCH Tagetik it is possible to use the Monthly splitting data processing or the Custom Splitting on Periods data processing.
The first one (Monthly splitting) is defined for each single account and allows you to split per month from the last period of a scenario, on all previous periods of the Scenario, while the second one (Custom Splitting on Periods) allows you to define in much more detail the data to split, the Scenarios /Periods on which to split the data and the driver to use.
A Custom Splitting on Periods routine (Data processing > Data operations) is defined by a set of rules which, on their turn, are defined by a set of details.
Rules¶
A Custom Splitting on Periods rule defines the source Scenario and Period for the data to split, and the filters on Category and Entities to apply to the data to split.
Moreover, the target interval, the step and the journal category are defined at rule level. The step specifies if the data must be split on all the periods of the selected interval, or only every n periods.
For example, if we specify a step 3, we can split an annual data only on the quarters, even though all twelve periods are open on the target scenario.
A Custom Splitting on Periods rule is defined by the following properties:
- Sequence. Mandatory. It is the unique ID of the rule and represents the order in which the rules are run.
-
Description. Mandatory.
-
An Input area, in which the following properties are defined:
-
Scenario. Mandatory. It defines the source scenario. Only an Original and active scenario can be selected.
- Period. Mandatory, it defines the source Period. Only a Period of the selected Scenario can be selected.
- Period length: defines the number of months of the data to run. If you select Cumulated (default) the system will split the cumulated data of the selected Scenario Period. If you select Periodic, the system will read and split the periodic data of the selected Scenario / Period. The periodic data is calculated by subtracting from the cumulated data of the selected Scenario / Period, the cumulated data of n previous periods, where n is the value specified in the Step field.
- Step. Mandatory with the periodic data. It specifies the period length with which the data must be read.
- Category: Specifies the filters on the Category dimension to apply to the data to split. It is possible to specify a Category or a grouping.
-
Entity: Specifies the filters on the entity dimension to apply to the data to split. It is possible to specify an entity or a node of a non-time dependent hierarchy.
-
An Output area, in which the following properties are defined:
-
Scenario From. Mandatory. It specifies the first Scenario of the time frame where to split the source data. Only active Original Scenarios are available for selection.
- Scenario A. Mandatory. It specifies the last Scenario of the time frame where to split the source data. Only active Original Scenarios are available for selection.
- Period From. Mandatory. It specifies the first Period of the time frame where to split the source data. Only not blocked Periods of the selected Scenario are available for selection.
- Period To. Mandatory. It specifies the last Period of the timeframe where to split the source data. Only not blocked Periods of the selected Scenario are available for selection.
-
Step. Mandatory. It specifies the splitting time frame step: selecting 1 it splits the value over all the periods in the time frame. Otherwise it splits every n Periods, where n is the selected value, moving backwards from the Scenario/Period “To” to the Scenario/Period “From”, using the “Previous” Scenario chaining. The specified step is also applied to filter the Periods where to read the driver.
-
Category. Mandatory. Category used to write monthly splitting data.
-
A Driver area, in which the following properties are defined:
-
Category: Specifies the filters on the Category dimension to apply to the driver. It is possible to specify a category or a grouping.
Details¶
The Detail of a Custom Splitting on Periods rule defines the Accounts to split and the filters on the Custom dimensions to apply to the data to split.
The Detail of a Custom Splitting on Periods rule is defined by the following properties:
- Sequence. Mandatory. It is the unique id of the Detail and represents the order in which the Details are run.
- Description. Mandatory.
Filters area.
- Account. Mandatory. Specifies the accounts to split. It i possible to specify an account or a node of a non-time dependent hierarchy.
- Custom dimension. Specifies the filters on the dimension to apply to the data to split. It is possible to select an element of the dimension or a node of a non-time dependent hierarchy.
The system applies the detail filters when deleting data generated by any previous execution or by other monthly splitting rules.
Filters based on the data to split area.
At Detail level, it is also possible to define how the data to split and the driver must be calculated for Entity, Account and Custom dimension within the scope defined for each dimension. Possible values:
- none (default): the data to split and the driver are calculated all together within the scope defined on the dimension
- By element: the data to split and the driver are calculated individually for each element of the dimension within the scope defined on the dimension
- Per hierarchy: the data to split and the driver are calculated by subgroups within the scope defined on the dimension, on the basis of the parent node of the selected hierarchy to which each element is related
Driver area.
In this area it is possible to define the accounts to use for the drover and the source interval (Scenarios and Periods).
- Account. Specifies the accounts to use to calculate the driver. It is possible to select an account or a node of a non-time dependent hierarchy. If left empty, the driver is evaluated as an aggregation of all accounts.
- Scenario From. Defines the source Scenario of the time frame from which to read the driver. Only Original active Scenarios are available for selection.
- Scenario To. Defines the last Scenario of the time frame from which to read the driver. Only Original active Scenarios are available for selection.
- Period From. Defines the source Period of the time frame from which to read the driver. Only the Periods of the selected Scenario are available for selection.
- Period To. Defines the last Period of the time frame from which to read the driver. Only the Periods of the selected Scenario are available for selection.
The time frame from which the driver is read must be consistent with the monthly splitting interval defined in the rule.