Manage MUNs and Model for Drill-Through in Framework Manager

1
Manage MUNs and Model for Drill-Through in
Framework Manager

• Cognos 8 BI

2
Objectives

• At the end of this module, you should be able to
• describe model types and data entities
• define members and member unique names
• define a report drill-through
• identify drill-through combinations
• identify conformed drill-through values

3
Model Types in Cognos 8

• Cognos 8 lets you work with three model types
• relational
• dimensionally modeled relational (DMR)
• OLAP

4
Data Entities in Cognos 8

• Two data entity types
• values (relational)
• members (OLAP and DMR)

Relational
OLAP/DMR
Product
TrailChef Water Bag 1110
TrailChef Canteen 2110
TrailChef Kitchen Kit 3110
Product name
Aloe Relief
Bear Edge
Bear Survival Edge
Members
Values
5
Work with Members
Dimension

• Members are located in levels of an OLAP or DMR
  model.

Hierarchy
Level
Member
Child members
Members used as data items for a report
6
What Makes Up a Member?

• Framework Manager DMR source
• member key _businessKey (role)
• member caption _memberCaption (role)
• OLAP source (PowerCube)
• member key Category code
• member caption Category label
• OLAP source (MSAS)
• member key Member Key Column
• member caption Member Name Column

7
What is a Member Unique Name (MUN)?

• Used to locate a member
• Referenced in an expression when a member is
  used
• in a report
• in a filter or calculation
• for drill-through

8
What Makes Up a MUN?

• MUN from a PowerCube data source
• great_outdoor_sales_en.Products.Products.Pr
  oduct type-gtPC._at_MEMBER.101
• MUN from a Framework Manager DMR data source
• Sales.Product.Product.Product
  type-gtall.2101.101

9
Changes that Impact a MUN

• MUNs can change when
• hierarchies or levels change
• member keys change
• category codes in PowerCubes
• Member Key Column in MSAS cubes
• _memberKey role in DMR models
• members no longer exist in the data source
• a production environment has more members than in
  the test environment

10
Demo 1

• Identify How Changes to MUNs Impact Reports

11
Conform Values

• In order to relate information between data
  sources, values and types must match.

Cognos Transformer
Framework Manager
DMR_businessKey for Camping Equipment 1
Category code for Camping Equipment
1 or Source value for Camping Equipment 1
RelationalProduct line code for Camping
Equipment 1
Conformed values for like dimensions
12
What is Drill-Through?
Source Report
Revenue 2004 2005 2006
Camping Equipment 20,471,328.88 31,373,606.46 37,869,055.58
Mountaineering Equipment 9,642,674.54 11,248,676.06
Personal Accessories 7,144,797.52 10,955,708.04 13,793,960.30
Outdoor Protection 1,536,456.24 988,230.64 646,428.04
Golf Equipment 5,597,980.86 9,598,268.88 10,709,215.84
Target Report
Year Month Product line Product type Product name Revenue
2005 1 Mountaineering Equipment Climbing Accessories Firefly Charger 15,367.16
Firefly Climbing Lamp 6,064.14
Granite Belay 29,334.24
Granite Carabiner 4,024.90
Granite Chalk Bag 2,306.82
Granite Pulley 12,538.96
Climbing Accessories 69,636.22
13
Cognos 8 Drill-Through Definition Types

• Two commonly used types of drill-through
  definitions
• report-based
• package-based
• Add parameterized filters in target reports to
  focus results

14
Demo 2

• Create Drill-Through Definitions

15
Considerations for Drill-Through Definitions

• Things to consider before creating drill-through
  definitions include
• conformed drill-through values
• supported drill methods

16
Supported Drill-Through Combinations
Source Report Value Passed Target Report Parameter Expected
Relational Value Relational Value
DMR Member Key Relational Value
MUN DMR MUN
OLAP Member Key Relational Value
MUN DMR MUN
OLAP (must be same vendor as source) MUN
17
Demo 3

• Identify Drill-Through Values

18
Use Framework Manager to Create Unique Category
Codes in Transformer

• In Framework Manager you can
• create a calculation to make codes unique across
  levels

Product line code calculation
'PL' cast(Data Source View.PRODUCT_LINE.PRO
DUCT_LINE_CODE, VARCHAR(6))
Product line code Product line Product type code Product type Product number Product
PL1 Line A PT1 Type A 1 Product A
PL1 Line A PT1 Type A 10 Product B
PL1 Line A PT1 Type A 2 Product C
Product type code calculation
'PT' cast(Data Source View.PRODUCT_LINE.PRO
DUCT_LINE_CODE, VARCHAR(6))
19
Demo 4

• Create Unique Keys Across Levels and Externalize
  a Query Subject

20
Summary

• At the end of this module, you should be able to
• describe model types and data entities
• define members and member unique names
• define a report drill-through
• identify drill-through combinations
• identify conformed drill-through values