When publishing a cube in T6, 4 dimensions are generated by default: Time, Entity, Account, and Scenario. The dimensions allow the data to be segmented in various ways. The Scenario dimension adds a layer of context to the data, indicating whether it is something that has already occurred, something that is planned, or something that has been finalized. Every cube starts with 2 members in the scenario dimension by default: actual and planned, and it may also include the closed state, depending on the month in a specific interface.
Scenario is the only dimension without a hierarchy, meaning all members are on the same level.
To use the Scenario Types screen, the user will need the Manager feature Manage the application structure/model;
In addition to at least one of the following Manager features (application level):
| Feature | Description |
|---|---|
| Manage Actual Scenario Type | Allows viewing and changing actual scenario types on the Scenario Types screen. |
| Manage Planned Scenario Type | Allows viewing and changing planned scenario types on the Scenario Types screen. |
If the user does not have either of the two features, the Scenario Types option will not be displayed in the Modeling menu, even with the Manage application structure/model feature enabled.
There are two security features at the Manager (application) level to control granular access to the Scenario Types screen:
The access behavior is determined by the combination of features enabled for the user:
| Enabled Features | Menu Access | Scenarios displayed in filter |
|---|---|---|
| None | Screen not displayed in menu | — |
| Only Actual | Screen accessible | Only Actual type scenarios |
| Only Planned | Screen accessible | Only Planned type scenarios |
| Actual and Planned | Screen accessible | All scenarios (Actual and Planned) |
This segmentation ensures that teams working with actual scenarios do not modify planned scenarios, and vice versa.
The Scenario Dimension has a type defined as actual or planned. The combination of the Scenario dimension with the Time dimension allows us to detail the scenario type. In an actual scenario, we can define only the closed or actual types.
In the forms within T6, the scenarios can be displayed in rows, columns, or pages.
There are calculations made in the application that depend on the scenario's state for that month (Actual, Planned, or Closed).
| State | Description |
|---|---|
| Planned: | Represents data for future forecasts or plans. |
| Actual: | Represents data for events or transactions that have already occurred. This state contains historical and recorded information (it can be changed through other forms or by formulas that run in the actual state). |
| Closed: | Represents data that will never be recalculated in the current context. |
If the application is for consolidation, the scenario types become: Open, Not Open, and Closed.
Even if a scenario is planned, it may still have months that are already actual.
EXAMPLE:
For a planning application, in a planned scenario, the months from January to April can be configured as actual months. Therefore, the data for these months will not be editable in the forms.
Through the Scenario Types screen, we can change the state of a specific scenario, filter scenarios, and perform bulk actions. To use it, follow these steps:
Open the main menu in T6 and go to Modeling;
Select the Scenario Types option; (a panel will open on the side where we can change the scenario's state);
In Scenario Types, we have 3 filtering options: Application, Scenario, and Year;
We can click on
to collapse the filters and make it easier to view the list;
Based on the definitions applied in the filters, we will have a list of the selected scenarios and periods.
In this list, Scenario, Year, Month, and Type will be displayed, as shown in the example below:
We can view the history of changes and the current state of each row.
The Scenario dimension is the dimension that indicates the context of the data, having different types depending on the Application type (Planning or Consolidation).
No. All members in the scenario dimension are at the same level.
The scenario types in a planning application are: Actual, Planned, and Closed.
The scenario types in consolidation applications become: Open, Not Open, and Closed.
Actual Scenario: event that has occurred;
Planned Scenario: future projection (can have months marked as actual).
The Closed scenario type represents a frozen period, without recalculations or editing.
Yes. In a planned scenario type we can have months marked as actual (data in this period becomes non-editable).
The user will need the Manager feature Manage the application structure/model;
In addition to having at least one of the following Manager (application) features enabled:
Without either of these features, the Scenario Types option does not appear in the Modeling menu.
Bulk actions in scenario types are used to change more than one period at once.
When applying changes to scenario types, if you don't click the Save button, the changes will be lost.
Next to each row in the panel there is a question mark icon in the Type column, click the icon to view the changes in that scenario type.
The change history in scenario types displays: Current state and recent changes (User, Date/Time, Change).
In scenario types, some periods may be Closed or controlled by a rule/process, preventing their modification.
Changing the scenario type does not alter existing values; it changes behavior (editing/calculation).
Yes. In scenarios of the Actual/Closed types, they are normally locked for editing.
The Not Open scenario type in consolidation applications is a period not yet released for input/consolidation.
You can access the Scenario Types tool and check the history to verify the recent changes.
No. Scenario types are fixed, varying according to the selected application type.