July21 Release Notes

Dynamic Planning: Breakback Loop

With this release, a new Breakback Loop step has been introduced in the calculation. The new functionality helps to achieve the following:

• Breakback Loop will leverage the existing Breakback engine and enhance it to support complex use cases with a simple setup.

• Breakback Loop will help customers configure complex top-down processes, make top-side adjustments, push the changes across multiple dimensions, and allocate the amounts based on historical trends.

• Breakback Loop will simplify the configuration of complex top-down processes.

• Breakback Loop will reduce the ongoing model and calculations maintenance.

• Breakback Loop will merge multiple breakback steps into one, simplify the calculations and improve their maintenance.

• Breakback Loop will collect all leaf members falling within the scope range for each loop dimension and iterate through them.

To understand the Breakback functionality, see Breakback functionality.

To run a Breakback from a calculation, see Breakback Calculation.

Now, you can set up a Breakback Loop comprising a Breakback Scope to generate forecast data for any model based on the available data instead of creating multiple calculation steps.

Previously, you had to set up dimension attributes in the Breakback Manager and create multiple calculation steps to generate forecast data for any model.

For example, previously, if you want to generate a forecast for 24 months for 100 customers having multiple dimensions based on the actual data, you have to define all dimension attributes in the Breakback manager and create 2400 Breakback steps. This took a lot of effort and time. With the new Breakback Loop, you can generate the same forecast for 100 customers by just creating one Breakback Loop calculation comprising one Breakback Scope. The new functionality saves time and effort and increases flexibility.

To enable this functionality, application admin users have to set the Enable Breakback Loop property to Yes. There is no need to contact the customer support team; application admin users can enable this functionality directly from the application.

Once you set the value of this property to “Yes”, you will be able to see “Breakback Loop” in the Type drop-down list for creating a calculation step.

You will also see the Breakback Scope column enabled in the Scope sheet.

Breakback Scope property is an optional property in the Scope.

• Users will be using Scope for various reasons, and it is applicable for Aggregation and Formula types in the calculation.

• If users are using Scope for any other type in the calculation other than the ‘Breakback Loop’, there is no need to populate or select any values in the Breakback Scope property.

• Breakback Scope property is only applicable for the Scopes users will use in the Breakback Loop type.

• Breakback Scope property should not impact the Scopes that are already created in the application.

• If users want to use Breakback Loop, they need to create the Scope with appropriate selections in the Breakback Scope property.

• Breakback Scope property drop-down contains Breakback Cell, Spread: Reference, Value: Reference, and Hold values. It is not mandatory that all these values have to be selected for a given scope. Based on the use case and need, users can select a combination of these values. For example, a Scope may only have a Breakback Cell, or a Scope may have a Breakback Cell and Spread Reference, etc.

• For the dimensions that users want to loop through, they need to set up the Scope and select the appropriate Breakback Scope property. For example, if users want to configure Breakback for 24 months, then one option is to use Breakback type in the calculation and create a 24 step calculation. Another option is to use the new Breakback Loop type in the calculation and define the Scope. In the Scope, set the Time dimension. Based on the Scope setup, the Breakback engine will loop through for each month, that is, 24 months.

• Any dimension that is defined in the Scope will work as a loop dimension for the Breakback engine. The only exception is for dimensions where the Breakback Scope property is set to Hold.

• Hold primarily holds the dimension members from the execution. The Hold in the Breakback Loop works the same as how Hold works in Breakback. The benefit users will have from defining Hold in the Scope is to make updates from one place.

• For users to use Hold, they have to define the hold dimension members in the Breakback configuration when they configure Breakback in the calculation.

• Hold is primarily to hold the dimension members from Breakback during the execution.

• Currently, defining the hold members in the Breakback manager in the calculation is mandatory. Hold in the Scope will only override the values. In future releases, this limitation will be relaxed.

• Hold dimension and the dimension on which users want to loop should not be the same. For example, if a user is looping through the Time dimension, defining the Hold on Time dimension is not supported.

• Dimensions in Breakback Scope must be limited to those that are loop parameters. There is no need to define all dimensions in the Scope.

Business Value

This functionality significantly reduces the time and effort required to generate forecast at the dimension level by creating several calculation steps.

When you have a huge data volume and you want to generate a forecast based on the actual data and other factors, you previously had to create many calculation steps that took immense effort and time. You can now achieve the same result by using Breakback loop, where

you have to create one Breakback scope and Breakback Loop calculation.

While defining the scope you must configure all dimensions in the loop that will be required to generate the forecast. The breakback loop calculation process considers all dimensions defined in the scope and uses the information defined in the Breakback manager for calculating the forecast.

With the new Breakback Loop, you can use the existing actuals and forecast data to design innumerous forecast scenarios quickly, or you can also make some changes to your existing scenarios and use it for analysis purposes. You can achieve all this by creating just one Scope and a Breakback Loop calculation step.

This functionality significantly reduces the time and effort required to create multiple calculation steps.

In Practice: Creating Breakback Loop Calculation Step

1. Navigate to the Scope sheet.

2. In the Scope sheet, set the Dimension, Filter Type, Filter Value, and Breakback Scope values. The Breakback Scope drop-down list will contain Breakback Cell, Spread: Reference, Value: Reference, and Hold values.

3. Save the scope.

   

4. Navigate to the Calculation sheet.

5. Select “Breakback Loop” from the Type drop-down list.

6. Enter the required Breakback Scope name in the Name column and add the required variables in the Variables column.

   

Sample Use Case

Let's say we have a sample model where salespeople are forecasting the revenue by region, and there are other dimensions in the model such as department, business unit, time, scenario, and measures.

There are four regions in the model (i.e., East, West, North, and South), and salespeople forecast the revenue for 24 months. Once the sales forecast is inputted, department managers have to plan for expenses in each department based on the sales forecast.

In this use case, revenue is forecasted at the region level, and expenses are forecasted at the department level.

To solve these types of use cases, users can consider multiple options. One option is to create separate models with corresponding dimensions and then consolidate the data for analysis and reporting purposes. Essentially the revenue is forecasted in a separate model, and expenses are forecasted in another model. By leveraging the Map functionality, users can move required data into these models.

Another option is to have both revenue and expense forecasted in the same model by leveraging the Breakback engine.

For example:

Step 1 - Let salespeople input their forecast for the regions that they are responsible for.

Step 2 - Create breakback steps in the calculation to push the revenue forecast data, which is at the region level to departments and business units level so that expenses forecast can be based on the sales targets.

Step 3 - Have department managers input the expenses at the department level by considering the sales targets.

The aspect of this process is how to achieve Step 2 simply and straightforwardly. Leveraging Breakback is an ideal approach; however, as the salespeople input the data for each region for 24 months, the engine then has to take that data and push the data into all the departments and business units based on the previous year's forecast, or current actuals, or a combination of both. So in practice, users have to create at least 24 breakback steps for each region. So to solve this use case, we need 24 * 4 = 96 steps.

If there are more regions and if there are more months, then the complexity increases drastically.

Also, suppose users want to make changes every month, like adjusting the time horizon or adding more regions. In that case, there will be a significant amount of changes needed in the breakback steps and calculation.

The Breakback loop will simplify these kinds of complex use cases by leveraging the looping mechanism.

So, we want the breakback to loop through 4 regions and 24 months in this use case, which means both Time and Region are the loop dimensions.

The first step in creating the Breakback loop step is to determine the dimensions and dimension members that qualify for the looping. Every use case will be different, so based on the use case, users must define the loop dimensions and dimension members.

One simple assumption that users can make here is to solve the use case with Breakback step, and understand what's changing (i.e., dimension and dimension members) for each step in the calculation, and then consider configuring those dimensions and dimension members loop dimensions.

Steps involved in creating the breakback loop for the above use case.

Step 1 - Create the Scope

As we have identified Time and Region as the loop dimensions, we need to include only these two dimensions in the Scope.

While defining the Breakback step in the calculation, users must provide Breakback Cell, Values Reference, and Spread Reference. Similarly, the Scope will also accept the same information.

We will discuss these options below.

In the above use case, we want both Region and Time dimensions to be included in the loop, and we also want the same for both Breakback cell and Value Reference.

Users can use FixedMember or MemberandBelow as the filter type options.

This Scope will result in 4 regions * 24 months = 96 breakback steps internally.

Step 2 - Create Breakback Loop step in the calculation

Creating Breakback Loop step in the calculation is exactly the same as how users create the Breakback step in the calculation. The only additional step is to select the Scope that was created in the previous step.

Breakback Loop with Spread Reference

Below Scope will consider running the breakback for 4 regions * 24 months by leveraging the 2020 spread.

Breakback Loop with MemberAndBelow for Region dimensions vs. Fixed Member

Below scope will loop through all the regions under ‘All Regions’ rollup, for example, 4 * 24 months = 96 steps.

An additional benefit in configuring the Breakback loop is that when a new Region gets added, it automatically gets included in the loop without any manual intervention from admin users.

Breakback Loop for 3 quarters in a year

Below Scope will loop through 9 months * 4 regions = 36 steps.

Breakback Loop for 3 months in a year

Dynamic Planning: Suppress Inner Block and Indent Hierarchy Members in Cascade Reports

Now, when you Suppress Rows in a Cascade report, if one of the data cells contains data, the inner block is not suppressed, and only the rows that do not contain any data are suppressed. With this functionality, any cells containing formulas but not having any data are not suppressed and are displayed appropriately.

Previously, all rows containing zeros or blank rows were deleted even if any inner cell had data or a formula associated with it.

Users can now add a new removeInnerBlockRows attribute to enable this new functionality. The value of this attribute is "true" by default; if users do not add this attribute, the system will assume it as true.

Examples:

Report Design - If the removeInnerBlockRows attribute is set to “false”.

Report Output in Run mode: Blank and Zero rows are hidden in the report. They are not deleted. This will ensure that any dependent excel formulas will not impact the overall report.

Report Design:- If the removeInnerBlockRows attribute is set to “true”.

Report Output in Run mode: Blank and Zero rows are not included in the report. This is applicable when the inner block does not have any dependent excel formulas in the inner block that might be affected.

Now, you can indent inner block members of dimension in a Cascade report. Previously, you did not have an option to indent. This functionality indents the inner block members based on their levels defined in the hierarchy.

Users can now add a new indentRowMembers attribute to enable this new functionality. The value of this attribute is "false" by default; that is, if users do not add this attribute, the system will assume that there is no indentation. When users add this attribute and set the value to "true", all the inner block dimension members on the row will be indented based on the levels defined in the dimension.

Platform: Added Sibling Hierarchy Validation

When you use ICSegment as an additional segment, then you cannot use IFRS hierarchy. Similarly, when IFRS is enabled, the Reuse ICSegment as Additional Segment checkbox is disabled when you try to add a segment in Configuration Tasks > Define Financial Segments.

Predict: The Signals Overview is now available in Reports

The Signals Overview feature is now available under Reports and is accessible to all the users having access to Reports. Signals Overview is essentially a Signals report of leaf-level anomalies present in the various Financial Models.

Similar to all reports, the Signals Overview also opens as a tab in the Reports section.

Predict: Added Dimension Security

Now, Signals Overview will be accessible to all FP&A users which was previously an admin-only feature.

With Dimension Security in place, users will only be able to see the members they have the access to view under the Selection Criteria. The users will not be able to see the Signals to which they do not have access under dimension security.