Considerations for Defining the Slice for Insights

In IPM Insights, you can generate insights for dynamic calc parent members.

• For reporting cubes (Aggregate Storage, or ASO cubes), there is no restriction on including dynamic calc parent members in insight definitions.
• For data entry cubes (Block Storage, or BSO cubes), you can’t include dynamic calc parent members or any dynamic calc member even at the leaf level, however you can use this solution:
  • Create an alternate hierarchy with shared members for parents that you want to consider for insight generation. The parent members should be defined as level zero members in the alternate hierarchy. When you configure the insight slice definition, make sure to select the members from the alternate hierarchy.
  • As a best practice, move the data to the reporting cube (Aggregate Storage, or ASO cube) using data maps, and then generate insights from that cube.

Including dynamic calc parent members in insights is especially helpful when you have a large number of members: you don't have to define multiple slice definitions for level zero members; you can define the slice definition to include a parent member.

Considerations:

• To avoid delays in insight generation for reporting cubes (ASO), consider not including dynamic parent members that have formulas in insight definitions.
• Because the number of alternate hierarchies you can create is limited, for data entry cubes (BSO), as a best practice, move the data to the reporting cube (ASO cube) using data maps, and then generate insights from that cube.
• For ASO cubes, prediction insights require that the slice definition includes only level zero members. Alternatively, to generate prediction insights for dynamic calc parent members, don’t enable Auto Predict. Or, run the prediction in BSO, and then move the results to ASO.