Using the new ‘Period Movement Variance’ Insight Type!

As part of the July 2026 monthly patch, Oracle released a new insight type – Period Movement Variance Insights! This is the first new insight type since the initial introduction of IPM insights so it’s an exciting new feature to explore.

The purpose of this new insight type is to monitor variances between the current period and a particular comparison period, which can be configured in the settings to run for year-on-year or period-on-period, depending on the requirement. This can really help clients reduce the monthly analysis typically undertaken each month to compare key KPIs to prior periods/years for example.

Types

To setup an insight job for period movement variances, first select the new Period Movement Variance Insights option on the initial setup page, under Generate Insights. This insight type does not require prediction data so the Generate Predictions setting can be set to None. 

Select Calendar

It is a requirement to select a Calendar when using the period movement variance insights. This will automatically set the cube and current period, as defined in your selected calendar. If you need help setting up your calendar, see my previous blog here: https://lydia-maksoud-epm.blogspot.com/2025/08/configuring-ipm-calendars-events.html

Define Slice

Define the cube members for each dimension, which hold the historic data. Typically this would be the Actual scenario, for example. It is recommended to keep the data slice as refined as possible, to avoid hitting threshold limits, even if this means breaking down the rules into multiple, for example split by region. It’s also recommended to focus on key business KPIs, rather than selecting all accounts, for example gross profit.

Configure

There are multiple options for the baseline comparison period, which can be based on:

  • Year-on-Year – Compare the current period to the same period in the prior year, e.g. Jun-26 vs Jun-25
  • Period-on-Period (Previous Period) – Compare the current period to the prior period, e.g. Jun-26 vs May-26
  • Period-on-Period (Custom) – Compare the current period to a custom prior period using the offset option, e.g. offset 4 would compare Jun-26 vs Feb-26
  • Historical Average – Compare the current period to the historical average

In all cases, there is an option to set a % (or value) threshold which will determine whether the intersection is flagged as an insight.

Note: if applicable, you can tick multiple comparison options in a single insights rule.

Settings

Select variable dimensions to be displayed in the POV on the insight list. For example, if the insights are for varying Entities or Products, then its best to include these in the POV.

View Insights

Once the insight rule has been run, the new insights will show with Type ‘Period Movement Variance’ in the list. 

The insight details provide a visual representation of the current period vs comparison period, depending on the settings enabled.

The insights AI panel provides a Generative AI summary of the insight, with natural language explanations. The explainability panel also gives some detail on the variance vs threshold and the impact of the insight.



Give this new insight type a try and let me know how you get on!

Comments

Post a Comment

Popular posts from this blog

Using Custom Scripts in Business Rules

Image
Custom calculation scripts contain sections of code which can then be referenced several times within a Business Rule, or in multiple different Business Rules. They are created within Calculation Manager, in much the same way as Business Rules, and are listed below the relevant PBCS Plan Type, under the ‘Scripts’ heading, as below: Custom scripts are useful for times when a certain section of code is repeated throughout a Business Rule, or is contained in multiple Business Rules. Using scripts in this situation means that if the script needs to be altered, it only needs to be updated in one place, rather than having to be updated in multiple locations or Business Rules. This saves time and ensures all your Business Rules which contain this section of code are consistent. The syntax used to reference a script from within a Business Rule is: %Script(name:=" ScriptName ",application:=" AppName ",plantype:=" PlanType ") Where:   ScriptName...
Read more

Using IPM Insights in Smart View

Image
As part of the April 2025 EPM patch updates, Oracle released a new version of Oracle Smart View for Office (version 25.100), which included the ability to use IPM insights directly in Smart View . Previously, the insights generated by IPM have only been accessible via the web interface, so this is a welcome improvement to allow users to access the insights via smart view. To view IPM Insights in Smart View, first connect to your Planning application and right click on the application name. If you have the correct version of smart view (25.100 or later) then you’ll see a new IPM Insights option:  Click on this to view the list of IPM insights, as below:   There are then a few options available : 1. Analyse a particular insight (tick one) – will open a new ad hoc grid containing the insight data for analysis     2. Insert Function (tick one) – will create a HsGetInsight function for the selected insight     3. Insert into a sheet (tick one or more) –...
Read more

Using Target Expressions in EPM Data Exchange

Image
Target Expressions can be used when importing data, to apply conditions to source values before loading to the target EPM application. Oracle advise that Target Expressions should be used when possible as they are more efficient than data load mappings, especially for loading large data sets. To being, setup your integration as usual with a Location, Import Format and Data Load Rule. Then to apply Target Expressions, go to Data Exchange , open the desired integration, and select Map Dimensions , as below: For each dimension, use the Options cog to select Edit Target Expressions .               The available Target Expressions are as follows: Copy Source Value Copies the exact source value to the Target. This can be used instead of a Like * to * mapping. Constant   Sets a constant value, regardless of the source value. This can be used instead of a Like * to “Working” mapping, for example. Default Will apply a defa...
Read more