Ibm Cognos Business Keys; Member Unique Names - IBM Cognos User Manual

Conformed dimensions are also key in successful data analysis using multiple
PowerCubes. When two cubes are to be used together, as with drill through,
ensure that the dimensional structure and the category source values are the same
in each cube model. Changes in the structure of a dimension in one cube, for
example, by adding another level, will impact both the reports and drill-through
applications that use the two cubes.

IBM Cognos Business Keys

In IBM Cognos Business Intelligence Reporting, PowerCube categories, or
members, have business keys that can be used for advanced reporting or in
drill-through scenarios. During Cognos Transformer model design, you can
determine the IBM Cognos business keys by setting the level source values.
Tip: Report Studio report authors can determine PowerCube business keys using a
calculation such as
roleValue('business key',[mycube].[Product Dimension].[All
Products].[Product Line])

Member Unique Names

In the IBM Cognos studios, the Member Unique Name (MUN) is the unique
identifier for locating the category or member in the data source. The MUN is
much like the business key in a table.
Cognos metadata uses the Cognos Transformer model category codes when
defining the MUN of a PowerCube category or member.
Member Unique Names are used
v as data item references for categories or members in any report specification
v as the value passed in PowerCube to PowerCube drill through in any report
v as identifiers for categories or members used in filters, expressions, parameters,
v to return categories or members to IBM Cognos applications
Tip: You can view the Member Unique Name for a category or member in Report
Studio. In Report Studio, open a PowerCube package, select a category, and view
the category properties.
Each time a PowerCube category code changes, the MUN reflects the change.
When categories or members are directly referenced in expressions, filters, or
reports, and the MUN changes, the category or member is no longer found. This is
because the original MUN is contained in the report specification.
Member Unique Names can change for different reasons:
v Changes in the hierarchy and level structures can result in changes to MUNs.
v Relative time categories may change, for example, when the current quarter
v If a source value changes, the category code used in the MUN also changes,
v The production environment may have more categories or members than the test
22
IBM Cognos Transformer Version 10.1.1: User Guide
or calculations in IBM Cognos BI
Any time a Cognos application requests the category or member, the MUN
ensures that the unique category or member is returned.
moves from one to the next.
unless the category code is specifically set to use a unique data item in the
model design.
environment.