Before you Begin
This tutorial shows you how to configure insights to generate insights that display on the Insights dashboard. This tutorial takes approximately 40 minutes to complete.
IPM Insights analyzes past data and predicted data, helping you find patterns and insights into data that you might not have found on your own. Insights can be trends, anomalies, forecast bias, or variations. With IPM Insights, the insight discovery phase of the planning process is automated with data science and financial pattern recognition, enhancing your forecast effectiveness. Using IPM Insights, you can analyze and explore data across any account. IPM Insights automates processing large amounts of multidimensional data, so that as new actuals come into the system, you quickly detect patterns in your data or hidden correlations, streamlining reporting, improving your forecasting, and strengthening your decision making. You spend less time in analysis, saving time in the overall planning process.
You configure IPM Insights by selecting the type of analysis to perform, specifying the slice definitions for analysis, configuring the analysis, and then defining the settings for the insights displayed on the Insights dashboard. You can define insights for as many data intersections as you need. Planners see insights only for slices of data to which they have access.
You can also define a prediction using Auto Predict to predict future performance based on historical data and schedule a job to run that prediction definition, automating the prediction process. You can use these prediction results as input for generating insights.
What Do You Need?
An EPM Cloud Service instance allows you to deploy and use one of the supported business processes. To deploy another business process, you must request another EPM Enterprise Cloud Service instance or remove the current business process.
You must have:
- Service Administrator access to an EPM Enterprise Cloud Service instance.
- Upload and import this snapshot into your instance.
Activating Navigation Flows
In this section, you activate the IPM Insights navigation flow so you can work with Insights.
- On the home page, click Tools, then Navigation Flows.
- For the IPM Insights row, under Active, click Inactive.
The IPM Insights navigation flow is activated, and the Default flow is inactivated.
- Click (Home).
- Click (Navigation Flow), and then IPM Insights.
The IPM Insights navigation flow is displayed.
Tip:You can reload the navigation flow to ensure the IPM Insights navigation flow is displayed.
In this section, you explore Insights with a sample application for Vision. You analyze Revenue data for the Sales West entity and identify areas on which you need to focus in order to improve your forecasting for this entity. Insights can be set up for any data across any account or measure – revenue, expense, balance sheet, cash flow or volumes.
You start by reviewing the underlying data, both historical and future data for the Sales West entity.
- On the home page, click IPM, then Insights Data.
Historical data for Insights is displayed.
The Sales West entity has five Revenue accounts and seven Products.
|Sentinal Standard Notebook|
|Sentinal Custom Notebook|
|Envoy Standard Netbook|
|Envoy Custom Netbook|
Data for historical actuals and historical forecasts is available starting from Jan FY19. The future forecasts have been made for the next six months (Jul FY21 through Dec FY21).
Planners have tried their best to forecast revenue data for the Sales West entity across five revenue accounts and seven products. You will do the following:
- Take a data-driven approach to analyzing historical data and identifying areas where significant forecast variance and/or bias exist
- Leverage machine-generated predictions which incorporate past trends and patterns to more accurately forecast data for the next six months
You will leverage IPM Insights to apply a data-driven approach to forecasting with data science.
In this section, you create an insight by selecting the types you want to create. Then you define the historical and future data slices, set thresholds, and define display dimensions and impact magnitude thresholds.
- Above Historical data for Insights, click Configure
- Click Create.
The Details page for IPM Configurator is displayed.
- In Details, for Name enter Revenue Analysis for Sales West, and for description enter To analyze the revenue data by product and generate all three types of insights.
- Under Generate Insights, select Forecast Variance & Bias Insights.
Forecast variance and bias insights analyzes historical data to reveal hidden bias in forecasts submitted by planners. This type of insight measures the variance or bias between two historical scenarios such as Forecasts and Actuals. .
- Under Generate Insights, select Prediction Insights.
Prediction insights look for variances between future scenarios such as forecasts and computer-generated predictions.
- Keep the default selection of No to indicate that you do not have prediction data available.
Note:If you have prediction data, you can indicate that by clicking the option to toggle it on. With no predicted data, Auto Predict is automatically selected under Generate Predictions.
Auto Predict uses the historical data for the intersection you defined to generate prediction data that is used for the insight. Prediction results can be used as input for generating prediction insights.
- Under Generate Insights, select Anomaly Insights.
Anomaly insights detect outlier values that vary widely from other values.
- Click Next.
Selecting the Historical Data Slice
In this section, you define the data slices used for insights analysis. For the Historical Data section, you define both actuals and the forecasts provided by planners. The slice definitions show all the dimensions for the cube, except for the Year and Period dimensions. All members start out with their root member selected.
- Under Historical Data, for Cube, select Plan 1 and for Number of Historical Years, enter 2.
- Under Actual, click Account.
- In Member Selector, search for Revenue, and click (Function Selector).
- Select Level 0 Descendants.
- Click HSP_View, and select BaseData.
- Click Scenario, and select Actual.
- Click Version, and select Working.
- Click Entity, then search for and select the second Sales West entry.
- Click Product, and search for Computer Equipment.
- For Computer Equipment, click (Function Selector), and select Level 0 Descendants.
- Click OK.
- Under Forecast, click the Actual scenario.
- In Member Selector, select Forecast and click OK.
Selecting the Future Data Slice
For the Future Data section, you select the cube and then define the slice of data for the future data, both the forecast provided by planners and the base prediction (most likely a scenario).
- Under Future Data, for Forecast, click the Actual scenario.
- In Member Selector, select Forecast, and click OK.
- Under Base Prediction, for Scenario, click Actual.
- In Member Selector, select Predict Base, and click OK.
- Click to select Future Periods.
- Under Period, click Select Period.
- In Member Selector, for Period, select Jul.
- Click Year, select FY21, and click OK.
Note:When you select Auto Predict, your prediction results are stored in this location.
- Click Next.
Note:If data is available, you can add a Best Case and Worst Case definition and define the slice of data for the best case and worst case scenarios.
You define the error tolerance and thresholds for insights. IPM Configurator selects default metrics for analysis.
- For Forecast Variance & Bias Insights, for Error Tolerance Limit, keep the selected error tolerance limit of 5%.
The error tolerance percentage defines the percentage variance between historical forecasts submitted by planners and actuals that lies within acceptable range. If the percentage variation crosses the error tolerance limit, it is considered for bias calculation.
- For Prediction Insights, change the threshold to 25%.
The Prediction threshold defines the acceptable percentage variance between future forecasts submitted by planners and computer-generated predictions.
- For Anomaly Insights, accept the Threshold of 3%.
The Anomaly threshold defines the acceptable threshold for Z-score value (the standard deviation from the mean of the values). Anything that is too far from zero (the threshold is usually a Z-score of 3 or -3) should be considered an outlier. An insight is generated when the specified outlier detection metric crosses the specified threshold.
You define metrics and trigger criteria on the Advanced Options page. Forecast variance indicates the level of accuracy of the forecasts submitted by planners. Forecast bias indicates the tendency of the direction of forecast error. A tendency to forecast in excess of the actuals is considered an “over-forecasting bias,” while a tendency to forecast below the actuals is considered an “under-forecasting bias.” For prediction insights, you specify how the deviation (variance) is determined by specifying the metric and threshold to measure the variance between future forecasts and historical predictions.
- Click Show Advanced Options.
- For Forecast Variance & Bias Insights, select the deviation percentage at which to trigger an insight. Change the Threshold to 25%.
- Specify the metric to use to measure forecast bias. For Bias Metric, set the threshold to 50%.
An insight is generated when either deviation or bias crosses the specified threshold.
- Select the deviation percentage between the future forecasts submitted by planners and computer-generated predictions at which to trigger an insight. For Prediction Insights, set the threshold to 50%.
- For Anomaly Insights, keep the selected threshold of 3%.
The threshold for Anomaly insights sets the threshold at which to trigger an insight.
- Click Next.
Tip:For help on any of the metrics, click (Help).
Setting Display Dimensions and Impact Magnitude Thresholds
On the Settings page, you configure the settings that define how to display the insights to planners. You select the dimensions that planners will use to navigate and analyze the insights. The dimensions you select will display on the Insights dashboard. You also define the impact magnitude thresholds to categorize insights into High, Medium, and Low groups.
- Under Display Dimensions, select Account, Entity, and Product.
- For Impact Magnitude Thresholds, change the low threshold to 30% and the High threshold to 60%.
When insights are displayed on the Insights dashboard, this setting categorizes insights into High, Medium, and Low groups based on the percentage impact calculated for each insight. This helps users focus attention on the insights that have more extreme variations.
- Click Save.
Note:Insight definitions are saved as global artifacts (in the Auto Predict folder under Global Artifacts) and are backed up with the maintenance snapshot.
- Click Cancel.
The Configured insight is displayed.
Specifying Insight Priority
In this section, you review the priority set for specific accounts.
- Click (Navigator) and under Application, click Overview.
- Click Dimensions.
- Click Account.
- Click (Zoom in Bottom Level).
- Select the North Channel row and scroll to the right until you see the Priority column.
The priority for each revenue account is displayed. North Channel has a high priority. Consumer Channel has a medium priority.
- Click Cancel.
Note:The relative priority of accounts is considered when ranking or prioritizing the generated insights. The magnitude of impact and the relative importance are the two factors considered for the prioritization of insights.
Copyright © 2021, Oracle and/or its affiliates.
In this tutorial, you configure insights to generate insights that display on the Insights dashboard.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.