Concept: Versions

A version in Adaptive Planning represents a particular financial scenario in your model. Versions help planners evaluate the effects of business transactions. Adaptive Planning supports these types of versions:

Actuals

Plans

You can use versions to cover 1 or more calendar or fiscal year. Every version contains different data, but the accounts, levels, and dimension structures remain the same in the model. You can add and remove levels and custom dimensions from a version.

Actuals Versions

Actuals versions display real numbers of sales and costs that have already happened. Most instances have 1 root actuals.

You can add 1 of these versions, which roll up to the root actuals:

Journal entry versions: Enable you to maintain actuals as a source of truth while using journal entries to make adjustments for instances with consolidation capabilities.

Sub-versions: Enable you to slice your actuals data.

When you have actuals sub-versions, you can select the actuals version to use for actuals overlay in each of your plan versions. Sub-versions are especially useful when you want to make adjustments to actuals without affecting the overlay. In this case, you can make adjustments to a different actuals sub-version than the 1 you use for actuals overlay. Remember that actuals sub-versions roll up to the root, which sums the values.

You can only edit the data of actuals versions without descendants.

Plan Versions

Plan versions contain forecasted or budgeted data. You can have more than 1 plan version, and you can organize these versions with folders.

Adaptive Planning supports these additional types of plan versions:

Virtual versions: Enable you to create constant currency reporting by using data from 2 different versions to create a read-only composite version.

Prediction versions: Enable you to generate machine learning predictions, which turn on anomaly detection in sheets. You can use these versions to set up intelligent planning.

Version Queuing

The version queuing process provides a more intuitive experience when you create versions. The version queuing process prevents timeout errors and creates the version in the background so that you don’t have to wait.

Statuses display next to the name of the version of the queuing version. The status displays for all users with the Versions
permission. Statuses include:

In Progress

Complete

, and

Failed

When versions fail, anyone can click the information icon next to the status to review a list of errors. When you're the person who initiated the version, an

also displays next to the version. You should click the

to dismiss the failed version, which removes it from the version list of all users. When you don't see the

, you didn't initiate the version and can't dismiss it.

Version Access

You can set how your team interacts with versions using:

Version Settings: Enables you to change the access for each type of user.

Level Settings: Enables you to add or remove levels from versions. This controls access to version data since users are associated with levels.

End User Version Access

When team members sign in, they select versions from the toolbar. Team members can only view and access versions based on:

User type.

The levels they select.

Opened sheets.