Skip to content

Scenario

Together with the period, the scenario represents Tagetik’s time dimension. In particular, the original scenario is used by Tagetik for all data entries and includes the concepts of tax year and data version.

The list of scenarios can be accessed from the administrator-user’s web interface by following the path Set-up and Admin > Dimensions tile > Scenario > List.

Navbar > Dimensions > Scenario > List.

For financial planning purposes, for every original scenario to be created, in addition to the code and description, it is also necessary to indicate:

  • the previous scenario
  • the following scenario.

These two pieces of information are essential for the purposes of balance sheet continuity: in fact, this is the only way that the system can link the various reporting years and respond to the needs of the Strategic Plan in terms of performing all of the closing and carry-forward entries spanning two years. Therefore, if the simulation in question ends with scenario 2013SP it is in any case necessary to create a following scenario, such as 2014SP.

In order to perform data entry, it is not sufficient to have defined an original scenario; it is necessary to associate one or more periods with the original scenario.

For example, to collect budget data for 2012, it is also necessary to indicate the periods, i.e. 2012BDG 03/06/09. Tagetik’s time dimension is ALWAYS the combination of the two physical dimensions: Scenario/Period.

The list of periods of an original scenario can be accessed from the administrator-user’s web interface by following the path Set-up and Admin > Dimensions tile > Scenario > List > Actions () > Periods.

Navigation panel> Dimensions > Scenario > List > Actions () > Periods.

For more details on the attributes to set during the definition of an original scenario, see the Basic Administration / Data Model HTML5 / Scenario chapter of the user manual.

Once the various original scenarios/periods have been defined, to be able to use them it is necessary to relate them to a process. This matching takes place from the administrator-user’s web interface, following the path Setup & Admin > Processes tile > Process definition > Define cycles.

Navbar > Processes & Workflow > Process > Process definition > Define cycles.

For more details, see the Process / Create a process” chapter of the user manual.

Event scenario

A particular feature of financial planning concerns the need to create an “Event Scenario”, i.e. a scenario used by the system to manage events to date, such as the opening of L/T financing or the purchase of properties.

Because financial planning operates with a date logic in Tagetik, it is not necessary to configure the periods for the event scenario since, when registering the entry, the system populates the period with a specific date, which is potentially different from the month-end.

The event scenario does not necessarily need to be a fictitious scenario; it can also be a “real” original scenario, such as the planning scenario present in the process, for example

Once the event scenario has been created, it is necessary to relate it to a process. This matching takes place from the administrator-user’s web interface, following the path Setup & Admin > Processes > Process definition > Data processing > “Cash Flow Planning” node requirements.

Navbar > Processes & Workflow > Process > Process definition > Data processing > “Cash Flow Planning” node requirements.