Actuals Thru and Dependent Scenarios

This article contains the following topics:

• What is the Dependent scenario type
• What are source scenario periods?
• More on Actuals Thru

Understanding Dependent Scenario Type

Definition: A dependent scenario type in Catalyst refers to a scenario that continuously synchronizes with a source scenario during its creation and beyond, allowing selective control over specific data types while excluding ongoing updates. This type is valuable when users want to model financial situations based on existing data without being affected by subsequent changes in the source scenario.

Found under Administration > Site Management > Scenarios > Add New

Importance of Dependent Scenario Type

• Initialization with Specific Data: Dependent scenarios allow users to initialize a new scenario with specific data from a chosen source scenario, providing a snapshot of the financial situation at the time of creation.

• Continuous Synchronization: Unlike some other scenario types, a dependent scenario continuously updates with changes in the source scenario after its creation. This provides an ongoing reflection of the source scenario while maintaining selective control over designated data types.

• Independent Rate Management: With the Dependent Scenario Type, users can synchronize with actuals while having the ability to load and manage rates independently in the new scenario. It allows for the exclusion of specific data types, such as rates, from automatic updates.
  
  
  
  

• Flexible Rate Editing: Users can designate "independent overrides" in the new scenario, allowing them to choose configurations, like currency exchange rates, to exclude from the automatic synchronization logic. This enables editing rates in the new scenario without being overwritten by the source scenario.

• Limited Dependency: Dependent Scenarios can only depend on Actuals scenarios, denoted by the fiscal year selected in the dropdown. The chosen year indicates which Actuals scenario the new scenario should sync with.

• Source Period Definitions: The source period definitions are used as an initial snapshot during the scenario setup and will not dynamically sync if changes are made in the source scenario after the new scenario creation.

Scenario Source Periods

Definition: Scenario source periods are specific time intervals selected during the setup of a new scenario, determining which data from the source scenario will be captured during the scenario creation process.

Importance of Scenario Source Periods:

• Initialization of New Scenarios: Selecting source periods is crucial for populating a new scenario with relevant data, providing a starting point for further analysis and modeling.

• Customizing Initial Dataset: Source periods allow users to customize the initial dataset with desired periods from other scenarios, creating a tailored starting point.

• One-Time Capture: The connection between scenarios and source periods is a one-time capture, meaning subsequent changes in the source scenario won't automatically update the new scenario.

• Learn More: For detailed steps and considerations regarding scenario source periods, refer to the Understanding Scenario Source Periods article.

Actuals Through

Definition: Actuals Through is a setting that determines the range of actual data to be included in a scenario. It plays a role in defining the starting point for certain scenario types, such as forecast and budget scenarios, capturing actual data up to a specified period.

Importance of Actuals Through

• Scenario Initialization: Actuals Through is used in certain scenario types, like forecast and budget scenarios, to define the baseline by capturing actual data up to a specific period.

• Automatic Data Pull: It automatically pulls data from the fiscal year actuals selected in the fiscal year dropdown for specific scenario types.

• Continuous Synchronization: Dependent scenarios continuously synchronize with the entire fiscal year's actuals selected under the fiscal year dropdown, providing an ongoing reflection of changes.

• Dependent Scenario Usage: When creating an audit scenario for a prior year and desiring automatic synchronization with actuals while retaining freedom to manage and change rates, volume, or currency exchange, the Dependent Scenario type is recommended.