1. Administering Planning
  2. Configuring IPM
  3. About IPM Insights
  4. Considerations for IPM Insights

Considerations for IPM Insights

The following are some of the considerations and best practices for leveraging the benefits of IPM Insightsand Auto Predict.

Considerations:

  • IPM Insights requires an EPM Enterprise Cloud service subscription.
  • IPM Insights works with these Planning application types:
    • Custom
    • Modules
    • Sales Planning
    • Strategic Workforce Planning
    • Cash Forecasting

  • You can use IPM Insights with Oracle Sales Planning Cloud and Oracle Strategic Workforce Planning Cloud.

  • IPM Insights and Auto Predict are not yet available in FreeForm applications; this is on the roadmap. For more information about Auto Predict considerations, see Auto Predict Considerations.
  • IPM Insights works only with applications with Hybrid Essbase enabled.

  • IPM Insights honors both member level security and cell level security, so planners see insights only for slices of data to which they have access. However, note that insights are not generated for a user when cell level security is defined on Year/Period dimensions.

IPM Insights Support Matrix

Review the table for a summary of the supported SKUs, business processes, and application types for IPM Insights.

Table 15-1 IPM Insights Support

SKU Business Process Application Type Supported? Comments
EPM Enterprise Planning Modules Supported

Hybrid Essbase must be enabled.
  Planning Custom Supported

Hybrid Essbase must be enabled.
  Planning Freeform Not supported  
  Planning Sales Planning  

Hybrid Essbase must be enabled.
  Planning Strategic Workforce Planning  

Hybrid Essbase must be enabled.
    Predictive Cash Forecasting  

Hybrid Essbase must be enabled
  Other business processes   Not supported  
Legacy SKU Planning Enterprise Planning and Budgeting Cloud Not supported  
  Planning Planning and Budgeting Cloud Not supported  
  Other business processes   Not supported  
EPM Standard Planning Standard Module Not supported  
  Other business processes   Not supported  
Sales Planning Planning Sales Planning Supported

Hybrid Essbase must be enabled
Strategic Workforce Planning Planning SWP Supported

Hybrid Essbase must be enabled

Best practices:

  • Historical Data: Prediction results are more accurate the more historical data you have. There should be at least twice the amount of historical data as the number of prediction periods. For example to predict 12 months in the future, you should have at least 24 months of historical data. At the time of prediction, if there is not enough historical data available, a warning is displayed.
  • Time Granularity of Predictions: Because the lowest Period dimension member level in an Insights job determines the time granularity of the prediction, create the Insights job using the lowest level of Period members possible so that the greatest amount of historical data can be used.

For more information about the statistical methods used in IPM Insights, see IPM Insights Metrics in Working with Planning.