IBM Planning Analytics Tips & Tricks

Do you know how to define your global settings in the overview area of an IBM Planning Analytics Exploration? Revelwood’s FP&A Technology Director, Lee Lazarow, demonstrates how to manage and define these settings. 

Watch our latest IBM Planning Analytics Tips & Tricks video to learn:

• Locate the gear icon in the overview area of your Exploration
• Identify the four different global settings you can define
  • Hierarchy name – shows details about each dimension
  • Iconography – gives details about each one of the dimensions, similar to the legacy version of Subset Editor
  • Context information – provides details about the database, which database it is references, which cube it is referencing
  • Section headers – shows within the area what is the context, or what was previously called titles or picks.

When you define your global settings in IBM Planning Analytics, you create a better experience for your end users. It enables end users to determine what they are looking at and what they are navigating through.

Revelwood has worked with IBM Planning Analytics / TM1 for more than 27 years. We’ve partnered with hundreds of companies on the design, development, maintenance and updates of IBM Planning Analytics applications, across every industry. Have a challenge with Planning Analytics / TM1? We can help you!

Watch more IBM Planning Analytics Tips & Tricks Videos:

IBM Planning Analytics Tips & Tricks: Add Color to Multidimensional PAW Charts

IBM Planning Analytics Tips & Tricks: Shortcuts in PAW Models

Did you know you can use MDX to create dynamic subsets based on cube values in IBM Planning Analytics? In our example we will only show companies with net sales greater than 30,000,000 in the selected year. 

An MDX statement that can provide this result may look something like this:

{FILTER({TM1SUBSETALL([bpmCompany])},[bpmFinance].([bpmScenario].CurrentMember, [bpmDepartment].CurrentMember,[bpmAccount].[Net Sales],[bpmCurrency].CurrentMember,[bpmPeriod].CurrentMember,[bpmFinance_Msr].[Balance Post-Alloc]) > 30000000 )}

The components of this statement are:

• FILTER({abc}),[Cube].([Dim1].[Value],[Dim2].[Value]…) > 30000000 )
  • Filter set ABC to only show members with a value greater than 30,000,000 for the intersection defined in the section after the comma
• TM1SUBSETALL([bpmCompany])
  • Grab all members within the bpmCompany dimension
• [bpmFinance]
  • The cube being used for the data
• ([bpmScenario].CurrentMember, [bpmDepartment].CurrentMember,[bpmAccount].[Net Sales],[bpmCurrency].CurrentMember,[bpmPeriod].CurrentMember,[bpmFinance_Msr].[Balance Post-Alloc])
  • The intersection used to get the cube value
  • This is like a DBRW formula in the sense that we are defining a view by listing every dimension and providing a member within that dimension
    • CurrentMember will grab whatever element is selected in the cube view for that dimension
    • The other dimensions are using a specific member that we always want to filter by

Below you will see only companies with net sales greater than 30,000,000 for the “Balance Post-Alloc” measure remain in the bpmCompany subset. This will dynamically update as selections for other dimensions are changed.

Revelwood has worked with IBM Planning Analytics / TM1 for more than 27 years. We’ve partnered with hundreds of companies on the design, development, maintenance and updates of IBM Planning Analytics applications, across every industry. Have a challenge with Planning Analytics / TM1? We can help you!

Read more IBM Planning Analytics Tips & Tricks:

IBM Planning Analytics Tips & Tricks: NumberToStringEx

IBM Planning Analytics Tips & Tricks: WildcardFileSearch

IBM Planning Analytics Tips & Tricks: Planning Analytics Workspace Visualization Axis