Snapshot scenarios
Running of the snapshot scenario¶
The snapshot scenario is run, i.e. populated with data, in different ways for the steps by Entity and the steps with Custom or Analytical dimensions.
| Step type | Description |
|---|---|
| by Entity | - The datasets associated with the step, filtered by the selected entities, are copied onto the Analytical Workspace. - The data for all the steps, filtered by the selected entities, are copied onto the Analytical Workspace. |
| with Custom or Analytical dimensions | The datasets associated with the step, filtered by the selected elements, are copied. |
CCH Tagetikruns the data processing as follows:
- Considers only the "reporting layer” partitions.
- Recovers the data of the AIH partitions that refer to the scenario and period dimensions and the dimension of the step.
- Applies the user restrictions only for the dimensions for which the snapshot is being run.
- The data processing can be run on one or more lowest-level elements or a node. If a node is selected, the data processing is run for all the lowest levels elements of the node.
Execution conditions¶
Before running a snapshot scenario, CCH Tagetikcheck that the following conditions are met:
- No period of the scenarios to be copied is stored offline.
- For each scenario to copy, the corresponding snapshot scenario has opened the same periods, and those periods have not been locked.
- If the scenario to copy is related to a financial planning process, there is a snapshot scenario of the event scenario related to the process.
IMPORTANT: before restoring a snapshot scenario, CCH Tagetik a blocking error will be flagged if you select a filter by dimension on which no snapshot was previously created.
Specific characteristics of the snapshot scenarios on AIH¶
Based on the process and partition types of the dataset, the partitions are selected as follows:
| Process type | Partitioning of the Dataset | Data selection criterion |
|---|---|---|
| Scenario / period | Not partitioned | - The scenario/period columns are required. - If the snapshot type is By entity, the partition must have an Entity column. - If the snapshot type is Also by other dimensions, the partition must have the respective Dimension columns. |
| Scenario / period | Partitioning by business cycle | - The scenario/period columns are not required. - If the snapshot type is By entity, the partition must have an Entity column. - If the snapshot type is Also by other dimensions, the partition must have the respective Dimension columns |
| Scenario / period | Partitioning by business cycle and entity | - The scenario/period/entity columns are not required. - If the snapshot type is Also by other dimensions, the partition must have the respective Dimension columns. |
| Single cycle | Not partitioned | - If the snapshot is By scenario, the scenario column is required. - If the snapshot is By scenario/period, the period column is required. - If the snapshot type is By entity, the partition must have an Entity column. - If the snapshot type is Also by other dimensions, the partition must have the respective Dimension columns. |
| Single cycle | Partitioning by business cycle | - If the snapshot is By scenario, the scenario column is required. - If the snapshot is By scenario/period, the period column is required. - If the snapshot type is By entity, the partition must have an Entity column. - If the snapshot type is Also by other dimensions, the partition must have the respective Dimension columns. |
| Single cycle | Partitioning by business cycle and entity | - If the snapshot is By scenario, the scenario column is required. - If the snapshot is By scenario/period, the period column is required. - The entity is not required. - If the snapshot type is Also by other dimensions, the partition must have the respective Dimension columns. |