1. Working with Planning
  2. Working With Strategic Modeling
  3. Creating and Running Scenario Rollups
  4. Creating a Scenario Rollup

Creating a Scenario Rollup

To create a new scenario rollup:

  1. From the Home page, click Scenario Rollups.
  2. Click Add and enter a name.
  3. From the Actions menu, click Open to start building the scenario rollup structure.
  4. Click Add Models icon to add models to the scenario rollup structure.
  5. From the Available Models list, drag and drop a model to the scenario rollup structure.

  6. To add an additional model, drag and drop a model from the Available Models list to the location you want in the scenario rollup structure.

  7. To delete a model from the scenario rollup structure, select the model, and from the Actions Actions menu menu, click Remove Model. The selected model and all of its children and business cases are removed from the scenario rollup structure.

Tip:

You can also create a new scenario rollup based on a model hierarchy. In Models, from the Actions Actions menu menu for the model you want to convert, click Convert to Scenario Rollup and then enter a scenario rollup name. The selected model and its child models are converted to a scenario rollup with the same hierarchical structure.

If you delete a scenario rollup that you've already run, it deletes the associated business cases in all of the models in the structure.

After creating the scenario rollup structure, you must create a business case to define how child node data is rolled up to the parent. See Defining Business Cases for Scenario Rollups.

About Valid Scenario Rollup Structures

To ensure that your scenario rollup structure is valid, avoid these conditions that cause scenario rollups to fail:

  • Fiscal years don't match
  • Subperiods exist in the parent that don't exist in the child
  • Deal period exists in the parent without a matching deal period in the child

These conditions won't stop a scenario rollup from running, but could cause meaningless data:

  • The child has years that the parent doesn't have
  • The parent and child have different historical boundaries
  • There are matching periods in the parent and child but the number of days in the periods are not the same
  • The actual period boundaries don't match
  • The user-defined dimensions are not compatible
  • The parent and child have a different number of months or weeks in a year or the end of the year falls on different days
  • The parent has periods with more time detail than the child (for example, the parent has months but the child only has years)