Restatement Page
Data Processing tile > Advanced Consolidation > Restatement
Purpose of the page¶
This page allows you to define the templates to be used in theRestatement utility.
The page consists of three main areas:
- left area: it shows the original scenarios that represent the baseline for the restatement
- central area: displays the templates associated with the selected original scenario
- right area: lists the attributes to be configured when creating a new template or editing an existing one
A template involves the definition of the following elements:
- Basic scenario: this is the original scenario containing the basic restatement version
- Suffixes for delta scenarios: used to create original scenarios dedicated to entering correction and integration data compared to the basic scenario
-
Suffix for stacked scenario:
-
for the creation of an original scenario automatically populated by the restatement utility as the sum of the basic scenario data and delta scenarios
- for the creation of stacked consolidation scenarios
- Periods to be processed
Buttons on the page
| Tab | Description |
|---|---|
| Add | Allows you to add an original scenario to the list of scenarios subject to restatement and to create the first scenario template . Active scenarios that have at least one period are available. IMPORTANT: the restatement utility is only available from the Process Hub. It is possible to create templates for scenarios/periods associated with standard processes; however, the template will not be usable. |
| Template creation | Allows you to create a new template for the original scenario of the selected row in the scenario list. |
Attributes on the page
| Tab | Description |
|---|---|
| Code | Template Code |
| Template name | Description of the template in the set languages. |
| Suffix for delta scenario | Suffix to be concatenated with the selected original scenario code to generate the delta scenario code. The scenario code has a maximum length of 15 characters; thus, the number of characters available for the suffix depends on the length of the base scenario. The delta scenario is used for data input to correct or integrate basic scenarios. It is possible to insert multiple suffixes, thus creating multiple delta scenarios. |
| Suffix for stacked scenario | Suffix to be concatenated with the selected original scenario code to generate the stacked scenario code. The stacked scenario is automatically populated by the restatement utility as the sum of the data in the basic and delta scenarios. The same stacked suffix may be used in more than one template of the same basic scenario, only if the selected periods are different. |
| Periods | Periods to be included in the restatement It is possible to choose from the existing periods for the original basic scenario. The selected periods may also belong to different processes. |
| Consolidation scenarios | After selecting the periods, the consolidation scenarios linked to the original basic scenario, which include at least one of the selected periods, are displayed. The toggle is active by default. If the concatenation of the consolidation scenario code with the stacked suffix exceeds the 15-character limit, the consolidation scenario cannot be selected. It is recommended to use a synthetic coding for scenarios in order to avoid length problems. |
| Update scenarios grouping relationships | It allows delta and stacked scenarios to be combined with the same nodes to which the basic scenario belongs. |
Save template
When the template is saved, the system automatically performs the following operations:
- Creation of delta and stacked scenarios and periods, if not already existing.
- Scenarios/periods relationship with the same processes to which the basic scenarios/periods belong. The relationship is set even if the process parameterisation is locked.
- If the Update scenario grouping relationship option is enabled, relationships with the same nodes to which the basic scenario belongs are added for delta and stacked scenarios.
IMPORTANT: Recoding scenarios may cause template inconsistency