Skip to main content
Adaptive Planning
Concept: Actuals Versions

Concept: Actuals Versions

As you create your actuals version hierarchy, you use different icons on the toolbar to create each actuals sub-version type:
  • Actuals sub-versions.
  • Journal entry versions.
You can hide an actuals version and still use it for actuals overlay on your plans.

Root Actuals Versions

Each instance includes a built-in actuals version. When you create actuals sub-versions or journal entry versions, this built-in actuals version becomes your root actuals version.
When you change the version details of your root actuals version, you change these version details on all:
  • Actuals sub-versions.
  • Journal entry versions.
Your root actuals version details always take precedence even when your sub-version details look different.
Example: Your version access controls enable the marketing team to view an actuals sub-version. When you hide your root actuals version from the marketing team, you also hide the actuals sub-version from the marketing team. We don't automatically update the access control settings on the actuals sub-version to reflect the root actuals access control settings.

Actuals Sub-Versions

Actuals sub-versions data rolls up to the data displayed in the actuals version. You can nest multiple layers of sub-versions. Because sub-versions inherit most settings from the root, you can only change a limited number of settings on the sub-versions.
When you create the first sub-version of an actuals version:
  • The data from the parent moves to the new sub-version.
  • The parent version becomes read-only even if you set the access control to Full Access. The parent version becomes read-only because the data is rollup data of its sub-versions.
Any additional sub-versions of an actuals version contain blank cells.
When you delete 1 of multiple sub-versions, you delete all of that data and the data in the parent version reflects that.

Translated Currencies

Translated currencies is a capability that enables you to load complete data sets of actuals in a specific currency for all levels. With translated currencies, you can load your data in the local currency of each leaf level as usual. In addition, you can load the same set of data in a specified currency for all levels.

Journal Entry Versions

Journal entry versions enable consolidation instances to maintain the integrity of their imported actuals. Instead of changing the data directly, you can create journal entries to make balanced adjustments to the data.
You can create separate journal entry versions for:
  • IFRS to GAAP.
  • Accruals.
  • Reclassifications.