Cognos 8 BI Transformer Designing OLAP Models

Cognos Training
Cognos 8 BI Transformer:
Designing OLAP Models
(version 8.3)
Instructor Guide - Volume 1
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Cognos 8 BI Transformer: Designing OLAP

Models (version 8.3)
Copyright 2008 Cognos ULC (formerly Cognos

Incorporated). Cognos ULC is an IBM Company.
C88382 - Production
Portions of Cognos(R) software products are protected by

one or more of the following U.S. Patents: 6,609,123 B1;
6,611,838 B1; 6,662,188 B1; 6,728,697 B2; 6,741,982
B2; 6,763,520 B1; 6,768,995 B2; 6,782,378 B2;
6,847,973 B2.
Part Number: 60556

Published May 2008
While every attempt has been made to ensure that the

information in this document is accurate and complete,
some typographical errors or technical inaccuracies may
exist. Cognos does not accept responsibility for any kind
of loss resulting from the use of information contained in
this document.
This document shows the publication date. The
information contained in this document is subject to
change without notice. Any improvements or changes to
the information contained in this document will be
documented in subsequent editions. This document
contains proprietary information of Cognos. All rights are
reserved. No part of this document may be copied,
photocopied, reproduced, stored in a retrieval system,
transmitted in any form or by any means, or translated
into another language without the prior written consent of
Cognos.
Cognos and the Cognos logo are trademarks of Cognos
ULC (formerly Cognos Incorporated) in the United States
and/or other countries. IBM and the IBM logo are
trademarks of International Business Machines
Corporation in the United States, or other countries, or
both. All other names are trademarks or registered
trademarks of their respective companies.
Information about Cognos products can be found at
www.cognos.com.
IP-2
2008, Cognos ULC (formerly Cognos Incorporated)

Cognos Confidential. For internal use only.
This guide contains proprietary information which is protected by copyright. No part of this document may be photocopied, reproduced,
or translated into another language without a legal license agreement from Cognos ULC (formerly Cognos Incorporated).
INSTRUCTOR
PREFACE
Contents
PREFACE....................................................................................................... IP-1
CONTENTS ...................................................................................................... IP-3
COURSE OVERVIEW ..................................................................................... IP-17
IMPORTANT COURSE CHANGES ................................................................... IP-19
COURSE OUTLINE ........................................................................................ IP-23
INSTRUCTIONAL MATERIALS ....................................................................... IP-34
GENERAL SETUP AND INSTRUCTOR PREPARATION ...................................... IP-39
DOCUMENT CONVENTIONS .......................................................................... IP-41
POWERPOINT TIPS ....................................................................................... IP-42
VMWARE KEYBOARD SHORTCUTS .............................................................. IP-43
GET THE CLASS STARTED ............................................................................ IP-45
POST-CLASS AGENDA .................................................................................. IP-46
SUBMIT FEEDBACK AND LOCATE ADDITIONAL PRODUCT INFORMATION ... IP-47
COGNOS PRODUCT HELP.............................................................................. IP-49
SETUP INSTRUCTIONS ............................................................................. SI-1
IMPORTANT SETUP INSTRUCTIONS FOR THIS COURSE ................................... SI-3
INSTALL MICROSOFT SQL SERVER 2000....................................................... SI-5
INSTALL MICROSOFT SQL SERVER 2000 SP3 ............................................. SI-10
INSTALL MICROSOFT SQL SERVER KB815495 ........................................... SI-12
ENSURE THAT THE PROPER PATCHES FOR SQL SERVER 2000 ARE
INSTALLED .................................................................................................. SI-13
ENSURE YOU HAVE INTERNET INFORMATION SERVICES INSTALLED ......... SI-14
CREATE THE COGNOS 8 CONTENT STORE .................................................... SI-15
RESTORE THE SAMPLE DATABASES ............................................................. SI-16
SET UP WEB ALIASES................................................................................... SI-18
CONFIGURE COGNOS 8................................................................................. SI-20
CREATE USERS IN THIRD-PARTY AUTHENTICATION PROVIDERS ................ SI-22
DEPLOY AND IMPORT COGNOS 8 SAMPLES.................................................. SI-23
IMPORT THE DEPLOYMENT ARCHIVES ......................................................... SI-24

IP-3
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
ADD DATA SOURCES ................................................................................... SI-25

RESTRICT ACCESS TO ADMINISTRATIVE TOOLS .......................................... SI-26
COPY REPORTS TO GO DATA WAREHOUSE (QUERY)................................... SI-27
ENABLE SAVING TO FILE SYSTEM IN REPORT STUDIO ................................ SI-28
ENSURE SIMPLE FILE SHARING IS OFF ......................................................... SI-29
INTRODUCTION.................................................................................INTRO-1
COURSE OBJECTIVES ...............................................................................INTRO-3
ADDITIONAL TRAINING............................................................................INTRO-7
OVERVIEW OF COGNOS 8 BI ....................................................................1-1
OBJECTIVES .....................................................................................................1-3
EXAMINE PERFORMANCE MANAGEMENT (PM)...............................................1-4
COGNOS 8 BI COMPONENTS ............................................................................1-5
COGNOS 8 GROUPS AND ROLES .......................................................................1-6
EXTEND COGNOS 8 BI .....................................................................................1-7
SUMMARY ........................................................................................................1-8
TRANSFORMER FUNDAMENTALS..........................................................2-1
OBJECTIVES .....................................................................................................2-3
BUSINESS INTELLIGENCE .................................................................................2-4
DIMENSIONAL ANALYSIS EXAMPLE ................................................................2-5
THE OLAP STRUCTURE ...................................................................................2-6
BENEFITS OF TRANSFORMER ...........................................................................2-7
BUSINESS REQUIREMENTS ...............................................................................2-8
WHAT IS A MODEL ...........................................................................................2-9
MODEL TYPES ................................................................................................2-10
FROM MODEL TO POWERCUBE ......................................................................2-11
WHAT IS A POWERCUBE ................................................................................2-12
MEASURES .....................................................................................................2-13
WHAT ARE DIMENSIONS AND LEVELS? .........................................................2-14
ADDITIONAL DIMENSIONS .............................................................................2-15
CATEGORIES/MEMBERS .................................................................................2-16
SUMMARY ......................................................................................................2-17
IP-4

INSTRUCTOR
PREFACE
THE TRANSFORMER DEVELOPMENT PROCESS ...............................3-1

OBJECTIVES ......................................................................................................3-3
MODEL REQUIREMENTS...................................................................................3-4
MODEL PLAN ...................................................................................................3-5
CREATE A MODEL PLAN ..................................................................................3-6
MODEL PLAN COMPONENTS ............................................................................3-7
ADD COMPONENTS TO THE TRANSFORMER MODEL ........................................3-8
DEMO 1: SET PREFERENCES .............................................................................3-9
DEMO 2: THE TRANSFORMER MODEL ...........................................................3-10
SUMMARY ......................................................................................................3-13
WORKSHOP 1: CREATE AN EXAMPLE MODEL PLAN .....................................3-14
DATA SOURCES IN TRANSFORMER.......................................................4-1

OBJECTIVES .....................................................................................................4-3
IDENTIFY YOUR DATA .....................................................................................4-4
DATA TYPES ....................................................................................................4-5
WHAT IS A DATA SOURCE FILE .......................................................................4-6
DEMO 1: CREATE A .CSV IN REPORT STUDIO TO USE AS A DATA SOURCE ......4-7
DATA SOURCE DESIGN GUIDELINES ..............................................................4-10
DEFINE DATA SOURCE PROPERTIES ..............................................................4-11
DEFINE COLUMN PROPERTIES .......................................................................4-12
PREVIEW SOURCE DATA AND SQL................................................................4-13
CONFIRM DATA SOURCE ORIGIN ...................................................................4-14
DEMO 2 : EXAMINE PROPERTY SHEETS .........................................................4-15
EXAMINE COGNOS 8 DATA SOURCES ............................................................4-17
ADD ADDITIONAL QUERIES TO EXISTING COGNOS 8 DATA SOURCES ..........4-18
DEMO 3: ADD A DATA SOURCE WITH MULTIPLE QUERIES............................4-19
DEMO 4: IMPORT QUERY ITEMS FROM A COGNOS 8 REPORT ........................4-23
TAKE ADVANTAGE OF THE DATA FILTERING IN COGNOS 8 REPORTS ...........4-27
EDIT EXISTING PROMPTS IN COGNOS 8 REPORTS AND PACKAGES ................4-28
SUMMARY ......................................................................................................4-29
WORKSHOP 1: CREATE A COGNOS 8 REPORT AND ADD IT AS A
DATA SOURCE ..............................................................................................4-30

IP-5
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
BUILDING A MODEL....................................................................................5-1
OBJECTIVES .....................................................................................................5-3
CREATE MODEL STRUCTURES .........................................................................5-4
DIMENSION PROPERTY SHEET .........................................................................5-5
LEVEL PROPERTY SHEET .................................................................................5-6
DEMO 1: BUILD A MODEL ................................................................................5-7
IMPORT DIMENSIONS FROM PACKAGES .........................................................5-11
GENERATE CATEGORIES AND CATEGORY COUNTS .......................................5-12
DIMENSION DIAGRAM....................................................................................5-13
CATEGORY PROPERTY SHEET ........................................................................5-14
VERIFY THE MODEL .......................................................................................5-15
DEMO 2: WORK WITH ITEMS IN THE DIMENSION MAP AND DIMENSION
DIAGRAM ......................................................................................................5-16
CREATE A POWERCUBE .................................................................................5-19
PUBLISH AS A DATA SOURCE AND PACKAGE IN COGNOS CONNECTION .......5-20
DEMO 3: CREATE THE POWERCUBE AND VIEW IN ANALYSIS STUDIO ..........5-21
SUMMARY ......................................................................................................5-25
WORKSHOP 1: CREATE A MODEL MANUALLY..............................................5-26
THE TIME DIMENSION ...............................................................................6-1
OBJECTIVES .....................................................................................................6-3
WHAT IS A TIME DIMENSION ...........................................................................6-4
TYPES OF TIME DIMENSIONS ...........................................................................6-5
CALENDARS .....................................................................................................6-6
DEFINE DATE FORMATS...................................................................................6-7
LIMIT THE RANGE OF DATES INCLUDED IN THE MODEL..................................6-8
SET UP FISCAL YEARS, QUARTERS, AND MONTHS ..........................................6-9
DEMO 1: SET UP THE FISCAL YEAR ...............................................................6-10
CREATE A TIME DIMENSION USING THE DATE WIZARD ...............................6-14
IP-6

INSTRUCTOR
PREFACE
DEMO 2: CREATE A TIME DIMENSION USING THE DATE WIZARD AND

MANUALLY ADD A LEVEL TO THE TIME DIMENSION ...................................6-15
NONSTANDARD TIME DIMENSIONS ...............................................................6-19
DEMO 3: CREATE A NONSTANDARD TIME DIMENSION .................................6-20
SUMMARY ......................................................................................................6-24
WORKSHOP 1: WORK WITH THE TIME DIMENSION ........................................6-25
WORKSHOP 2: WORK WITH THE DATE WIZARD ............................................6-30
RELATIVE TIME ...........................................................................................7-1
OBJECTIVES .....................................................................................................7-3
COMPARE TRENDS OVER TIME ........................................................................7-4
RELATIVE TIME CATEGORIES ..........................................................................7-5
TYPES OF RELATIVE TIME CATEGORIES ..........................................................7-6
GROUPED RELATIVE TIME ...............................................................................7-7
SET THE CURRENT PERIOD...............................................................................7-8
DEMO 1: SET THE CURRENT TIME PERIOD MANUALLY AND CREATE
ADDITIONAL RELATIVE TIME CATEGORIES ...................................................7-9
CUSTOMIZE RELATIVE TIME CATEGORIES ....................................................7-16
CUSTOMIZE: SINGLE CATEGORY ...................................................................7-17
CUSTOMIZE: PERIOD-TO-DATE ......................................................................7-18
CUSTOMIZE: N-PERIOD RUNNING TOTAL ......................................................7-19
DEMO 2: CREATE A CUSTOM RELATIVE TIME CATEGORY ............................7-20
FUTURE RELATIVE TIME CATEGORIES ..........................................................7-29
CONSIDERATIONS...........................................................................................7-30
SUMMARY ......................................................................................................7-31
WORKSHOP 1: CUSTOM RELATIVE TIME CATEGORIES ..................................7-32

IP-7
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
USE MULTIPLE DATA SOURCES..............................................................8-1

OBJECTIVES .....................................................................................................8-3
WHY USE MULTIPLE DATA SOURCES ..............................................................8-4
MULTIPLE DATA SOURCES ..............................................................................8-5
STRUCTURAL VS. TRANSACTIONAL DATA SOURCES .......................................8-6
PLAN THE DATA SOURCES ...............................................................................8-7
DEMO 1: INTEGRATE MULTIPLE DATA SOURCES INTO A MODEL ....................8-8
ASSOCIATE COLUMNS WITH LEVELS .............................................................8-11
RELATE DATA SOURCES BY RENAMING COLUMNS .......................................8-12
RELATE DATA SOURCES BY SOURCE ASSOCIATION ......................................8-13
SET THE CURRENT PERIOD.............................................................................8-14
DEMO 2: DEFINE COLUMN PROPERTIES ........................................................8-15
DEMO 3: BUILD THE DIMENSION MAP ...........................................................8-18
DEMO 4: INSERT A DIMENSION FROM AN OLAP PACKAGE ...........................8-20
SUMMARY ......................................................................................................8-22
UNIQUENESS..................................................................................................9-1
OBJECTIVES .....................................................................................................9-3
VALIDATE MULTIPLE DATA SOURCE MODELS ................................................9-4
DEMO 1: DATA SOURCE SCOPE .......................................................................9-5
WHAT IS UNIQUENESS?....................................................................................9-8
LEVEL IS NOT UNIQUE: THE ISSUE ..................................................................9-9
LEVEL IS NOT UNIQUE: A SOLUTION .............................................................9-10
DECLARE LEVELS UNIQUE.............................................................................9-11
IDENTIFY MODEL ISSUES ...............................................................................9-12
DEMO 2: DECLARE LEVELS UNIQUE ..............................................................9-13
DEMO 3: UNIQUENESS VIOLATIONS (INSTRUCTOR ONLY).............................9-15
UNIQUE MOVE ...............................................................................................9-18
DEMO 4: UNIQUE MOVE (INSTRUCTOR ONLY) .............................................9-19
SUMMARY ......................................................................................................9-27
IP-8

INSTRUCTOR
PREFACE
WORKING WITH MEASURES..................................................................10-1

OBJECTIVES ...................................................................................................10-3
MEASURES .....................................................................................................10-4
DEMO 1: MODIFY MEASURE PROPERTIES ......................................................10-5
REGULAR AND NON-REGULAR ROLLUP SETTINGS ........................................10-9
CALCULATED MEASURES ............................................................................10-10
TIMING OF CALCULATION ............................................................................10-11
TIMING OF CALCULATION: BEFORE ROLLUP ...............................................10-12
TIMING OF CALCULATION: AFTER ROLLUP .................................................10-13
CATEGORY COUNT MEASURE......................................................................10-14
DEMO 2: CREATE A CALCULATED MEASURE ...........................................10-15
DEMO 3: CREATE AND CALCULATE A ROLLUP MEASURE ...........................10-18
DEMO 4: CREATE A MEASURE WITH A TIME STATE ROLLUP ......................10-23
DEMO 5: CREATE A CATEGORY COUNT MEASURE ......................................10-27
SUMMARY ....................................................................................................10-30
WORKSHOP 1: CREATE AND CALCULATE A ROLLUP MEASURE ..................10-31
CREATE A MEASURE WITH A TIME STATE ROLLUP .....................................10-37
ALLOCATED MEASURES .........................................................................11-1
OBJECTIVES ...................................................................................................11-3
ALLOCATION ..................................................................................................11-4
ALLOCATION - AN EXAMPLE .........................................................................11-5
WHAT IS THE MEASURE SCOPE DIMENSION MAP ..........................................11-6
ALLOCATE AS A CONSTANT VALUE...............................................................11-7
DEMO 1: ALLOCATE A MEASURE AS A CONSTANT ........................................11-8
ALLOCATE AS A PROPORTION OF ANOTHER MEASURE ...............................11-16
DEMO 2: ALLOCATE A MEASURE AS A PROPORTION ...................................11-17
DO NOT ALLOCATE .....................................................................................11-22
SUMMARY ....................................................................................................11-23

IP-9
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
CURRENCY CONVERSION.......................................................................12-1
OBJECTIVES ...................................................................................................12-3
CURRENCY CONVERSION ...............................................................................12-4
HOW IS CURRENCY CONVERTED?..................................................................12-5
DEFAULT CURRENCY SETTINGS ....................................................................12-6
DEMO 1: IMPORT CURRENCY DATA USING A DATA SOURCE ........................12-7
SUMMARY ....................................................................................................12-12
WORKSHOP 1: CURRENCY CONVERSION .....................................................12-13
ALTERNATE HIERARCHIES WITHIN A DIMENSION ......................13-1
OBJECTIVES ...................................................................................................13-3
WHAT IS AN ALTERNATE HIERARCHY? .........................................................13-4
WHY DO WE USE ALTERNATE HIERARCHIES?..............................................13-5
DIRECT ACCESS .............................................................................................13-6
REORGANIZE THE LEVELS..............................................................................13-7
INTRODUCE A NEW LEVEL .............................................................................13-8
CONVERGENCE LEVELS .................................................................................13-9
DEFINE THE CONVERGENCE LEVEL AS UNIQUE ..........................................13-10
AN ALTERNATE HIERARCHY IN A TIME DIMENSION ...................................13-11
DEMO 1: CREATE ALTERNATE HEIRARCHIES ..............................................13-12
DEMO 2: CREATE AN ALTERNATE HIERARCHY IN THE TIME DIMENSION ...13-19
SUMMARY ....................................................................................................13-23
ADVANCED DIMENSIONAL MODELING .............................................14-1
OBJECTIVES ...................................................................................................14-3
ADD A NEW SOURCE LEVEL ..........................................................................14-5
WHAT ARE MANUAL LEVELS?.......................................................................14-6
POPULATE MANUAL LEVELS .........................................................................14-7
CREATE ORPHAN CATEGORIES ......................................................................14-8
DEMO 1: ADD A MANUAL LEVEL, AND MANUAL CATEGORIES.....................14-9
IP-10

INSTRUCTOR
PREFACE
DEMO 2: CREATE AN ORPHANAGE (INSTRUCTOR ONLY) ............................14-17

CREATE SUBDIMENSIONS.............................................................................14-21
SPECIAL CATEGORIES ..................................................................................14-22
DEMO 3: CREATE A SUBDIMENSION AND A SPECIAL CATEGORY ................14-23
SCENARIO DIMENSIONS ...............................................................................14-28
DEMO 4: CREATE A SCENARIO DIMENSION .................................................14-29
CALCULATED COLUMNS ..............................................................................14-33
CALCULATED CATEGORIES..........................................................................14-34
DEMO 5: CREATE CALCULATED COLUMNS AND AN EXCEPTION
DIMENSION .................................................................................................14-35
DEMO 6: CREATE CALCULATED CATEGORIES IN TRANSFORMER................14-40
DIMENSION CUSTOMIZATION REVIEW.........................................................14-46
SUMMARY ....................................................................................................14-47
WORKSHOP 1: CUSTOMIZE THE MODEL ......................................................14-48
WORKSHOP 2: CREATE A CALCULATED COLUMN AND CALCULATED
CATEGORIES ...............................................................................................14-58
CUSTOMIZE CUBE CONTENT ................................................................15-1
OBJECTIVES ...................................................................................................15-3
CUSTOMIZE CONTENT WITH VIEWS ...............................................................15-4
DEMO 1: OMIT DIMENSIONS AND EXCLUDE MEASURES FROM A
POWERCUBE .................................................................................................15-5
SUPPRESSED CATEGORY ................................................................................15-9
SUMMARIZED CATEGORY ............................................................................15-10
CLOAKED CATEGORY ..................................................................................15-11
EXCLUDED CATEGORY ................................................................................15-12
APEXED CATEGORY .....................................................................................15-13
WHAT ARE DIMENSION VIEWS?...................................................................15-14
DEMO 2: CREATE DIMENSION VIEWS ..........................................................15-15
SUMMARY ....................................................................................................15-20
WORKSHOP 1: CUSTOMIZE POWERCUBES ...................................................15-21

IP-11
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
EXAMINE COGNOS 8 SECURITY............................................................16-1

OBJECTIVES ...................................................................................................16-3
EXAMINE THE COGNOS 8 SECURITY MODEL .................................................16-4
USE AUTHENTICATION PROVIDERS ...............................................................16-5
AUTHORIZATION ............................................................................................16-6
CONTROL ACCESS TO CONTENT ....................................................................16-7
DEFINE SECURITY POLICIES...........................................................................16-8
DEFINE PERMISSIONS .....................................................................................16-9
DEMO 1: INTRODUCE COGNOS 8 SECURITY AND CREATE GROUPS .............16-10
TRANSFORMER SECURITY ............................................................................16-13
SUMMARY ....................................................................................................16-14
APPLYING SECURITY ...............................................................................17-1
OBJECTIVES ...................................................................................................17-3
OVERVIEW OF MODEL SECURITY ..................................................................17-4
CREATE PASSWORD-PROTECTED CUBES .......................................................17-5
CREATE MEMBER-BASED SECURITY..............................................................17-6
ASSIGN SECURITY TO CUSTOM VIEW ............................................................17-7
ASSIGN CUSTOM VIEWS TO POWERCUBES ....................................................17-8
DEMO 1: CREATE CUSTOM VIEWS .................................................................17-9
DEMO 2: ASSIGN SECURITY TO CUSTOM VIEWS..........................................17-12
COMBINE CUSTOM VIEWS WITH DIMENSION VIEWS ...................................17-17
UNION OF CUSTOM VIEWS ...........................................................................17-18
SUMMARY ....................................................................................................17-19
WORKSHOP 1: CREATE CUSTOM VIEWS AND APPLY SECURITY..................17-20
IP-12

INSTRUCTOR
PREFACE
OPTIMIZING POWERCUBES ...................................................................18-1

OBJECTIVES ...................................................................................................18-3
WHAT IS A CUBE GROUP?..............................................................................18-4
WHAT IS STORED IN A POWERCUBE?.............................................................18-5
POWERCUBE PRODUCTION PROCESS .............................................................18-6
CONSIDER OPTIMIZATION ..............................................................................18-7
USER RESPONSE TIME....................................................................................18-8
MANAGE CUBE BUILD TIME ..........................................................................18-9
OPTIMIZE PERFORMANCE ............................................................................18-10
MANAGE DATA READ TIME.........................................................................18-11
STREAMLINE YOUR DATA ...........................................................................18-12
WHAT IS CONSOLIDATION? .........................................................................18-13
USE THE APPROPRIATE ROLLUP FOR CONSOLIDATION................................18-14
DEMO 1: EXPLORE DATA SOURCE AND OPTIMIZATION SETTINGS ..............18-15
MANAGE CATEGORIES .................................................................................18-18
MANAGE MEASURES ...................................................................................18-19
PC OPTIMIZER UTILITY ...............................................................................18-20
LIMIT DATA READS .....................................................................................18-21
REDUCE POWERCUBE BUILD TIMES ............................................................18-22
HARDWARE CONSIDERATIONS.....................................................................18-23
PLAN FOR DISK SPACE .................................................................................18-24
MODEL SPACE REQUIREMENTS ...................................................................18-25
WORK FILE SPACE REQUIREMENTS .............................................................18-26
OPTIMIZE THE I/O ........................................................................................18-27
ENSURE SUFFICIENT MEMORY ....................................................................18-28
SUMMARY ....................................................................................................18-29

IP-13
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
PARTITION A POWERCUBE ....................................................................19-1

OBJECTIVES ...................................................................................................19-3
PARTITION A POWERCUBE .............................................................................19-4
PROS AND CONS OF PARTITIONING ................................................................19-5
DEVELOP A PARTITIONING STRATEGY ..........................................................19-6
CREATE A TIME-BASED PARTITION CUBE .....................................................19-7
DEMO 1: CREATE AND MODIFY A TIME-BASED PARTITIONED
POWERCUBE .................................................................................................19-8
AUTOMATICALLY PARTITION A POWERCUBE .............................................19-15
DEMO 2: AUTO-PARTITION ..........................................................................19-16
MANUALLY PARTITION................................................................................19-20
MANUALLY PARTITION (CONT'D) ................................................................19-21
DEMO 3: MANUALLY ADD ONE LEVEL OF PARTITIONING ..........................19-22
MULTIFILE POWERCUBES ............................................................................19-24
SUMMARY ....................................................................................................19-25
MAINTAIN MODELS AND POWERCUBES ...........................................20-1
OBJECTIVES ...................................................................................................20-3
MAINTAIN MODELS AND POWERCUBES ........................................................20-4
SOURCE DATA UPDATES ................................................................................20-5
DATA SOURCE MAINTENANCE ......................................................................20-6
SYNCHRONIZE THE MODEL AND DATA SOURCE............................................20-7
DEMO 1: MODIFY THE MODEL BASED ON SOURCE FILES..............................20-8
MODEL UPDATES .........................................................................................20-13
DELETE INACTIVE CATEGORIES...................................................................20-14
CUBE UPDATES ............................................................................................20-15
UPDATE CUBES INCREMENTALLY ...............................................................20-16
CHECK FOR OPEN CUBES .............................................................................20-17
DEMO 2: DETECT AN OPEN POWERCUBE DURING REBUILD .......................20-18
OVERWRITE A PUBLISHED POWERCUBE ......................................................20-21
UPDATE DATA SOURCE CONNECTION INFORMATION .................................20-22
IP-14

INSTRUCTOR
PREFACE
DEMO 3: OVERWRITE A PUBLISHED POWERCUBE .......................................20-23

DEMO 4: UPDATE THE DATA SOURCE CONNECTION, WITHOUT
IMPACTING COGNOS 8 USERS .....................................................................20-26
RECOVER A FAILED MODEL.........................................................................20-30
MODEL TYPES IN COGNOS 8 ........................................................................20-31
DATA ENTITIES IN COGNOS 8 ......................................................................20-32
WORK WITH MEMBERS ................................................................................20-33
WHAT MAKES UP A MEMBER? ....................................................................20-34
WHAT IS A MEMBER UNIQUE NAME (MUN)? .............................................20-35
WHAT MAKES UP A MUN? .........................................................................20-36
CHANGES THAT IMPACT A MUN .................................................................20-37
DEMO 5: HOW CHANGES TO MUNS IMPACT REPORTS ................................20-38
CONFORM VALUES ......................................................................................20-45
SUMMARY ....................................................................................................20-46
MODEL FOR DRILL-THROUGH IN TRANSFORMER........................21-1
OBJECTIVES ...................................................................................................21-3
WHAT IS DRILL-THROUGH?...........................................................................21-4
COGNOS 8 DRILL-THROUGH DEFINITION TYPES ...........................................21-5
DEMO 1: CREATE DRILL-THROUGH DEFINITIONS .........................................21-6
CONSIDERATIONS FOR DRILL-THROUGH DEFINITIONS................................21-17
SUPPORTED DRILL-THROUGH COMBINATIONS............................................21-18
DEMO 2: IDENTIFY DRILL-THROUGH VALUES.............................................21-19
WHEN CAN CATEGORY CODES CHANGE? ...................................................21-26
USE TRANSFORMER TO CREATE UNIQUE CATEGORY CODES ......................21-27
DEMO 3: CREATE A UNIQUE CATEGORY CODE IN TRANSFORMER ..............21-28
MODELING RECOMMENDATIONS .................................................................21-31
SUMMARY ....................................................................................................21-32
BLANK MODEL PLANS .............................................................................. A-1

IP-15
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
IDENTIFY COMMON DATA STRUCTURES........................................... B-1

OBJECTIVES .................................................................................................... B-3
EXAMINE THE ROLE OF A METADATA MODEL ............................................... B-4
DISTINGUISH BETWEEN OPERATIONAL AND REPORTING DATABASES ........... B-5
IDENTIFY FEATURES OF AN OPERATIONAL DATABASE .................................. B-6
IDENTIFY ISSUES WITH OPERATIONAL DATABASES ....................................... B-7
EXAMINE REPORTING DATABASES (STAR SCHEMA DESIGN)......................... B-8
CREATE A STAR SCHEMA ................................................................................ B-9
EXAMINE OPERATIONAL DATA .................................................................... B-10
EXAMINE REPORTING DATA ......................................................................... B-11
EXAMINE FACT TABLES ................................................................................ B-12
EXAMINE DIMENSION TABLES ...................................................................... B-13
IDENTIFY ISSUES WITH A STAR SCHEMA ...................................................... B-14
DEFINE RELATIONSHIPS ................................................................................ B-15
EXAMINE RELATIONSHIPS: CARDINALITY .................................................... B-16
EXAMINE RELATIONSHIPS: OPTIONAL VS. MANDATORY ............................. B-17
EXAMINE RELATIONSHIPS: DATA TRAPS ...................................................... B-18
EXAMINE OLAP DATA STRUCTURES ........................................................... B-19
IDENTIFY DATA ACCESS STRATEGIES .......................................................... B-20
SUMMARY ..................................................................................................... B-21
IP-16

INSTRUCTOR
PREFACE
Course Overview
Course Overview
Cognos 8 BI Transformer: Designing OLAP Models (version 8.3) is a
four-day, instructor-led course that teaches OLAP modelers how to
design, build, and maintain PowerCubes for use with Cognos 8 BI.
Attendees will participate in hands-on demos and workshops that
illustrate key concepts while learning how to use the product.
Intended Audience
OLAP Modelers who will build PowerCubes for use in Cognos 8 BI
Topics Covered
Topics covered in this course include:
Overview of Cognos 8 BI
Discuss the fundamentals of OLAP modeling
Plan, design, and work with the model plan
Work with data sources and build a model
Examine the time dimension and relative time
Use multiple data sources and address uniqueness
Work with measures and currency conversion

IP-17
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Create alternate hierarchies within a dimension

Advanced dimensional modeling
Customize cube content
Examine Cognos 8 security
Apply security
Maintain models and PowerCubes
Optimize and partition PowerCubes
Model for Drill-Through
Identify common data structures
Course Prerequisites
Participants should have:
Understand the business need for ad hoc queries and analysis
Cognos 8 BI: Reporting and Analyzing Data for Business Authors
(version 8.3) (recommended)
Experience using basic Windows functionality
IP-18

INSTRUCTOR
PREFACE
Important Course Changes

New features for Cognos 8 BI Transformer: Designing OLAP
Models (Version 8.3)
General Notes
Analysis Studio is used to validate model changes, not the
PowerPlay Client. In the 8.3 version of the course, the test
environment must be the Cognos Studios. The PowerPlay client is a
separate license that customers have to purchase in C8. It will not
be actively sold to new customers - only existing Series 7
customers. The S7 version of the course is still available. This
course is written for new Cognos 8 customers using 8.3
Transformer.
Uses the Cognos 8 security model instead of Access Manager.
Demo and workshop scripts are scripted with a minimalist (fewer
words, less steps) approach to make it easier for instructors and
students to read.
The amount of information on the slides and the number of slides
may have been reduced to reduce redundancy if the material is
covered in a demo.
The amount of student data is greatly reduced.
Member is the C8 terminology. However the Transformer 8.3
product uses the term "category" inside the product. A category and
member are different names for the same object. When working
inside the C8 studios, you will often see the terminology of
"member" but when working inside the Transformer product - the
terminology will be "category".

IP-19
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Module 1: Overview of Cognos 8 BI

New module to give an Overview of Cognos 8 BI.
Module 2: Transformer Fundamentals
No major changes.
Module 3: The Transformer Development Process
No major changes.
Module 4: Data Sources in Transformer
Contains new material that addresses Cognos 8 data sources.
Module 5: Building a Model
Contains new material that addresses importing dimensions from
packages, creating a PowerCube, and publishing a PowerCube as a
data source and package.
Module 6: The Time Dimension
No major changes.
Module 7: Relative Time
No major changes.
Module 8: Use Multiple Data Sources
Module was divided and uniqueness is moved to its own module.
Module 9: Uniqueness
New module focusing on uniqueness violations.
Module 10: Working with Measures
No major changes.
IP-20

INSTRUCTOR
PREFACE
Module 11: Allocated Measures

No major changes.
Module 12: Currency Conversion
No major changes.
Module 13: Alternate Hierarchies within a Dimension
Terminology is different.
Module 14: Advanced Dimensional Modeling
No major changes.
Module 15: Customize Cube Content
No major changes.
Module 16: Examine Cognos 8 Security
This is a new module that covers a basic overview of Cognos 8
security. Students build groups and add users to test security.
Module 17: Applying Security
This module focuses on applying Cognos 8 security in Transformer.
Students will create custom views and apply security.
Module 18: Optimizing PowerCubes
No major changes. Partitioning as moved to its own module.
Content from S7 appendix was moved to this module.
Module 19: Partition a PowerCube
New module that focuses on partitioning.

IP-21
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Module 20: Maintain Models and PowerCubes
This module addresses data source, model, and cube updates. It

also discusses MUNs and addressing changes that impact them.
Covers overwriting a published PowerCube using the PCCONN
utility and update the data source connection without impacting
Cognos 8 users.
Module 21: Model for Drill-Through

Focuses on Drill through access in Cognos 8.
Identify Common Data Structures (Optional)
This is a high level explanation of the differences between
Operational and Reporting databases. An explanation on why the
Star Schema is the best model for PowerCubes and for Reporting
applications. Many students wonder how they get from the
Operational database to the data warehouse.
IP-22

INSTRUCTOR
PREFACE
Course Outline
The following table outlines the high-level topics for each module, and the
number of slides, demos and workshops included, as well as the
estimated teaching time.
Topics
Slides
Demos
Workshops
Est. Time
15 -30
mins
Slides
Demos
Workshops
Est. Time
16
1 hr.
discuss Cognos 8 and

Performance Management
describe Cognos 8 BI
components
define Cognos 8 BI groups
and roles
explain how to extend
Cognos 8 BI
Transformer Fundamentals
Topics
discuss the basics of OLAP

analysis
discuss the importance of
business requirements
review Transformer and
Cognos 8 BI components
define categories and
members

IP-23
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
The Transformer Development Process

Topics
describe the purpose of a

model plan
Slides
Demos
Workshops
Est. Time
12
1 hr
Slides
Demos
Workshops
Est. Time
20
1.5 hr
match business requirements

to the model
discuss an approach for
creating a model plan
review the relationship of the
model plan to the
Transformer model
Data Sources in Transformer

Topics
discuss the types of data

used by Transformer
create data source files and
define properties
preview source data and SQL
add Cognos 8 data sources
to the model
discuss data filtering
IP-24

INSTRUCTOR
PREFACE
Building a Model
Topics
create model structures and
Slides
Demos
Workshops
Est. Time
17
1.5 hr
Slides
Demos
Workshops
Est. Time
16
1.5 hr
modify property sheets
confirm the data source origin

generate categories to
populate the model
modify the model using the

dimension diagram
verify the model and create a

PowerCube
publish as a data source and

package
The Time Dimension

Topics
discuss the purpose of a time

dimension
review properties of a time

column
define a regular time

dimension
examine standard and
nonstandard time dimensions
limit the range of valid dates

IP-25
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Relative Time
Topics
compare trends over time
Slides
Demos
Workshops
Est. Time
17
1 hr
Slides
Demos
Workshops
Est. Time
1 hr
Slides
Demos
Workshops
Est. Time
14
1 hr
set the current period

create relative time categories
customize relative time
categories
Use Multiple Data Sources

Topics
discuss the use of multiple

data sources
plan the data source

define data source types
Uniqueness
Topics
identify and resolve conflicts

between data sources
validate a multiple data

source model
discuss a unique move
IP-26

INSTRUCTOR
PREFACE
Working with Measures

Topics
discuss the purpose and uses
Slides
Demos
Workshops
Est. Time
17
1.5 hr
Slides
Demos
Workshops
Est. Time
11
1 hr
of measures
describe regular and
calculated measures
set measure properties

compare rollup options
create a calculated measure
create calculations before or
after rollups
create a category count

Allocated Measures
Topics
discuss measure allocation

allocate measures as a
constant and by another
measure
check measure distribution

IP-27
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Currency Conversion
Topics
apply and use currency

conversion techniques
Slides
Demos
Workshops
Est. Time
45
mins
Alternate Hierarchies within a Dimension

Topics
discuss primary and alternate

drill-down paths
Slides
Demos
Workshops
Est. Time
13
1 hr
describe the benefits of

alternate drill-down paths
create an alternate drill-down
path
define convergence levels
and identify uniqueness
issues
IP-28

INSTRUCTOR
PREFACE
Advanced Dimensional Modeling

Topics
discuss techniques for

customizing dimensions
Slides
Demos
Workshops
Est. Time
22
2 hr
Slides
Demos
Workshops
Est. Time
13
1.5 hr
add a new source level to an

existing dimension
create and populate a manual
level in a dimension
create orphan categories
modify a dimension using a
subdimension
create a special category
create a scenario dimension
create and use calculated
columns and categories
Customize Cube Content

Topics
create various types of

PowerCubes
omit dimensions and exclude

measures
create and apply dimension

views

IP-29
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Examine Cognos 8 Security

Topics
examine the Cognos 8

security environment
Slides
Demos
Workshops
Est. Time
11
45
mins
Slides
Demos
Workshops
Est. Time
13
1 hr
identify the Cognos 8 BI

security model
define authentication in
Cognos 8 BI
define authorization in
Cognos 8 BI
identify security policies

Applying Security
Topics
review model security

create custom views
assign security to custom
views
assign custom views to
PowerCubes
combine custom views with
dimension views
IP-30
examine a union of custom

views

INSTRUCTOR
PREFACE
Optimizing PowerCubes
Topics
examine cube groups
Slides
Demos
Workshops
Est. Time
26
1 hr
Slides
Demos
Workshops
Est. Time
14
1.5 hrs
plan for disk space

examine optimizing factors
optimize PowerCube inputs
and outputs
determine factors affecting

PowerCube build time
Partition a PowerCube
Topics
identify the pros and cons

develop a partitioning strategy
create a Time-based
partitioned cube
automatic vs. manual
partitioning
understand multifile
PowerCubes

IP-31
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Maintain Models and PowerCubes

Topics
maintain models and

PowerCubes
Slides
Demos
Workshops
Est. Time
28
2 hrs
understand data source,

model, cube updates
synchronize the model and
data source
incrementally update
PowerCubes
describe model types and
data entities
define members and member
unique names
address changes that Impact

a MUN
Model for Drill-Through in Transformer

Topics
define a report drill-through
Slides
Demos
Workshops
Est. Time
13
1 hr
identify drill-through
combinations
IP-32
identify conformed drillthrough values

INSTRUCTOR
PREFACE
Identify Common Data Structures

Topics
examine the characteristics of

operational databases and
databases designed for
reporting
Slides
Demos
Workshops
Est. Time
20
1 hrs
examine relationships and

cardinality
identify different data traps
examine OLAP data sources

IP-33
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Instructional Materials
Student Guide
The Student Guide contains material that helps to explain features of the
product, along with the presentation slides that are presented by the
instructor. Student demos and workshops are incorporated in the course
to enrich the learning experience through hands-on practice.
Demos
Demos appear after covering one or more topics or features of the
application. While not every product function is demonstrated,
participants work with the more important and complex features through a
series of tasks. Demo tasks contain a number of steps related to a
specific action or feature of the product.
Workshops
In most of the modules, a supplementary workshop is included. If
participants followed the concepts in class without difficulties, they can
probably complete the workshop with no additional information. The
second section for each workshop contains a task table that identifies
each task, where to work in the application, and any applicable hints to
help the participants. The third section of the workshop contains screen
captures of the expected results. The fourth section contains a step-bystep solution to the workshop. Participants may want to follow these
instructions if they are not able to complete the workshop or if they
require a little more practice with the application.
IP-34

INSTRUCTOR
PREFACE
Instructor Guide
The Instructor Guide contains the same content presented in the Student
Guide, along with additional notes to supplement and add value to the
lecture. The information can be generic, non-technical information, such
as multiple ways to perform the same command or a more in-depth
discussion of a topic. It may also be used to address more technical
questions from participants or as supplementary technical discussion, at
the discretion of the instructor. It helps to provide the appropriate level of
information to a specific audience.
Instructor Data Download

The Instructor Data Download is an executable (EXE) file that can install
any or all of the following files. By launching this executable and following
the prompts as the install runs, these files will be installed in
C:\Edcognos\C88382.
Instructor Slides
These files contain the Microsoft PowerPoint slide presentation for each
module of the course as presented in the Student Guide:
C8T-01-Overview_of_Cognos8_BI.ppt
C8T-02-Transformer_Fundamentals.ppt
C8T-03-The_Transformer_Developement_Process.ppt
C8T-04-Data_Sources_In_Transformer.ppt
C8T-05-Building_A_Model.ppt
C8T-06-The_Time_Dimension.ppt
C8T-07-Relative_Time.ppt
C8T-08-Use_Multiple_Data_Sources.ppt
C8T-09-Uniqueness.ppt

IP-35
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
C8T-10-Working_With_Measures.ppt
C8T-11-Allocated_Measures.ppt
C8T-12-Currency_Conversion.ppt
C8T-13-Alternate_Hierarchies_within_a_Dimension.ppt
C8T-14-Advanced_Dimensional_Modeling.ppt
C8T-15-Customize_Cube_Content.ppt
C8T-16-Examine_Cognos_8_Security.ppt
C8T-17-Applying_Security.ppt
C8T-18-Optimizing_PowerCubes.ppt
C8T-19-Partition_a_PowerCube.ppt
C8T-20-Maintain_Models_and_PowerCubes.ppt
C8T-21-Model_for_Drill-Through.ppt
C8T-A-Blank_Model_Plans.ppt
C8T-B-Identify_Common_Data_Structures.ppt
8.3)
PDF version of the Instructor Guide

These files are the Instructor Guide Microsoft Word documents in PDF.
IP-36

INSTRUCTOR
PREFACE
Student Data
The EXE contains the files that are necessary to complete the demos and
workshops. By inserting the EXE into the student PCs and allowing the
auto install to run, these files will be installed to the C:\Edcognos\C88382
directory. The EXE contains the following folders and files:
C88382 (root)
o Basic Measures.csv
o go_sales_scenario.csv
o Product Profit.csv
o Regions.csv
PPT-Advanced Dimensional modeling (folder)

o Demo 2_Start.pyj
PPT-Allocated measures (folder)

o Demo 1_Start.pyj
PPT-Alternate_Hierarchies_within_a_Dimension (folder)
o Demo 1_Start.pyj
PPT-Uniqueness (folder)
o Demo 1_Start.pyj
The Solutions folder (C:\Edcognos\C88382\Solutions) contains a

subfolder for each module. Within the module folder there is a
Transformer model solution (.pyj or .mdl) for each demo and
workshop. If a student has trouble finishing a demo or workshop (or
simply wants to compare their results), they can open the
Transformer model solution file in the desired demo or workshop
folder from within Transformer. They can then optionally do a Save
As to overwrite their own incomplete project folder.

IP-37
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Instructor Files
The C:\Edcognos\C88382\Instructor Files folder contains a .zip file
(OLAP reports.zip) needed to set up the student and instructor machines.
It is referenced in Setup_InstructionsC88382.doc.
Demos, Workshops, and Workshop Solutions
The course is designed to be easily customized for on-site training with
customer data. The files contain Microsoft Word files that you can use to
modify the demonstrations and workshops as required.
IP-38

INSTRUCTOR
PREFACE
General Setup and Instructor Preparation

Pre-Class Agenda
To ensure that the class runs smoothly, you should know the answers to
the following questions. If you need help in obtaining answers, contact the
customer or customer's sales representative (if the course is scheduled for
a client site), or the local office responsible for course logistics.
Who is the contact person for class setup?
What is the classroom setup? Is there a white board? Is there a flip
chart? Is there a computer for the instructor, a PC viewer, overhead
projector, and screen?
Will the physical environment be set up prior to your arrival (product
loaded and PowerPoint files on the computer)?
What time does the class start?
What hours are available for accessing the teaching site, copying
the files to the hard disk, tuning the color on the PC viewer, and so
on?
What Cognos office is responsible for sending the Student Guides?
If the course has been previously taught on the computers you are
using, have the Preferences been reset to their defaults, and have
student files been deleted?

IP-39
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Prepare to Teach
After you have configured the instructor and student computers, consider
the following:
Run through at least one module in a classroom with a PC viewer.
Run through the full course at least once on a computer.
Make sure you complete each of the demos before teaching the
course so that you become familiar with each step required.
Have a set of product reference manuals in the classroom.
Make sure that there is a Student Guide for each participant.
IP-40

INSTRUCTOR
PREFACE
Document Conventions
Conventions used in this guide follow Microsoft Windows application
standards, where applicable. As well, the following conventions are
observed:
Bold
Bold style is used in demo and workshop

step-by-step solutions to indicate either:
actionable items
(Point to Sort, and then click Ascending.)
text to type or keys to press
(Type Sales Report, and then press Enter.)
UI elements that are the focus of attention
(In the Format pane, click Data)
Italic
Used to reference book titles.
CAPITALIZATION
All file names, table names, column names, and

folder names appear in this guide exactly as they
appear in the application.
To keep capitalization consistent with this guide,
type text exactly as shown.

IP-41
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
PowerPoint Tips
Here are valuable keyboard commands you can use to improve your
presentation.
Command
Key(s)
Advance to next slide
Left-click, Page Down, Space, N, Right or

Down Arrow, right-click/Next, Enter
Return to previous slide
Backspace, Page Up, P, Left or Up Arrow,

right-click/Previous
Change pointer to a pen
Right-click/Pen or Ctrl+P
Erase drawings on screen
Make the screen white
W or ',' (toggle to restore)
Make the screen black
B or '.' (toggle to restore)
Help
End the slide show
Esc, Ctrl+Break, '-'
Move between PowerPoint Alt+Tab or click the application name on

and the product
the status bar
You can also jump to a specific slide by typing its slide number and
pressing the Enter key. However the slide number is not the same as the
printed page number because a page may be built from several slides to
produce an animation sequence.
Important Tips:
A page containing an animation slide (multiple clicks to complete the
slide) will also include an Instructor Guide note indicating the
number of clicks needed to complete the slide.
IP-42

INSTRUCTOR
PREFACE
VMware Keyboard Shortcuts

Below is a list of shortcuts that can be used when in a VM image.
Shortcut
Action
Ctrl-B
Power on.
Ctrl-E
Power off.
Ctrl-R
Reset the power.
Ctrl-Z
Suspend.
Ctrl-N
Create a new virtual machine.
Ctrl-O
Open a virtual machine.
Ctrl-F4
Close the summary/console view for the selected virtual

machine. A confirmation dialog appears only if the virtual
machine is powered on.
Ctrl-D
Edit the virtual machine's configuration.
Ctrl-G
Grab input from keyboard and mouse.
Ctrl-P
Edit preferences.
Ctrl-Alt-Enter Go to full screen mode.

Ctrl-Alt
Return to normal (windowed) mode.
Ctrl-Alt-Tab
Switch among open virtual machines while mouse and

keyboard input are grabbed.
Ctrl-Tab

keyboard input are not grabbed. VMware Workstation
must be the active application.

IP-43
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Shortcut
Action
Ctrl-ShiftTab

keyboard input are not grabbed. VMware Workstation
must be the active application.
Ctrl-Alt-Fx
Linux hosts: Switch among open virtual machines while

using full screen mode. Fx is a function key corresponding
to the virtual machine you want to use. The key
combination to use for a virtual machine is shown in the
VMware Workstation title bar when that virtual machine is
active and in normal (windowed) mode.
Windows hosts: For an additional similar functionality, see
Using Full Screen Switch Mode.
IP-44

INSTRUCTOR
PREFACE
Get the Class Started

Welcome participants to the course. Use the slide show,
STARTC88382.PPT, to introduce yourself, the participants, and the
agenda for the training (optional).
Instructor Introduction
Cognos 8 BI Transformer: Designing OLAP Models
(version 8.3)
Instructor Name
Instructor Background
Student Introductions
Name
Company
Position
Product Experience
Personal objective(s)
for this course
Administrative Items
Sign-in sheet
Smoking
Messages
Telephones
Use this slide to welcome the participants to the

course, to introduce yourself, and to mention
your background (for example, how long you
have been teaching the course, your teaching
experience overall, how long you have been
working with the product, and so on). Make sure
you have customized the slide ahead of time.
Have the participants take turns introducing
themselves with respect to the items listed on
this slide. The intent of the slide is to act as an
icebreaker and to encourage participation.
Use this slide to go through the list of

administrative items that participants often ask
about.
Washrooms
Emergency exits
Refreshments
Turn off cell
phones and pagers
Class Format
Lecture with slides
Student guides as
reference material
Hands-on demos to
learn and practice
Use this slide to explain the class format and

emphasize that participants are encouraged to
actively perform the hands-on demos while
following along with the instructor. Mention that
the Student Guide contains copies of the slides
and further supporting notes for the participants
to use as reference material in the future.

IP-45
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Post-Class Agenda
Have participants complete the Course Evaluation forms.
Hand out certificates.
Leave the classroom clean.
If you brought any hardware or course media, take them with you
when you leave. Erase any files copied to the hard disks of the
computers in the classroom. Change the Preferences back to their
initial settings.
Complete the Instructor Feedback form, and return it to the
Education Coordinator. Ensure that the Coordinator receives the
Course Evaluation forms.
If you are at a customer site, thank the course administrator by
letter.
List any outstanding questions, and ensure that participants receive
answers in writing.
Report any sales leads to your sales representative.
Make notes for yourself about what went well during the course and
what needs improvement. When you are preparing for your next
teach, you can refer to these.
IP-46

INSTRUCTOR
PREFACE
Submit Feedback and Locate Additional Product

Information
Submit Feedback
Your feedback is important and valuable. We are interested in your
comments or questions. If you have feedback for a course, you may
directly submit it to our online database using the following link:
http://ges/ges-feedback. The link to this feedback database can also be
found in the Instructor Support community on myCognos.
You may also send general comments or concerns to Global Education
Services at GES@cognos.com.
In the Instructor Support Community on myCognos, your suggested
course corrections and course-related supplementary information (e.g.
additional demos you use, diagrams you created) will be posted under
Course Updates, and teaching tips and techniques will be posted under
Instructor Tips. This gives other instructors worldwide, immediate use of
the information. Instructional designers will also use this information when
the course is updated. Access the Instructor Support Community at
http://myCognos. You will also find additional course information (for
example, course release status or course development templates) in the
Instructor Support Community, which you may find useful when preparing
for courses.
Suggestions for significant course enhancements will be reviewed for
possible implementation in future course updates.

IP-47
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Additional Product Information

You can research product information including issues, and advanced
functionality using the Knowledge Base. Access the Knowledge Base
through the Web at http://trakweb. If you do not already have a user
name and password to access the Knowledge Base, you can send an
email request to trakker.development@cognos.com.
You can also search the Customer Support Web site at
www.cognos.com/support, for further product information. To obtain a
user name and password, send an email request to
webmaster.support@cognos.com.
Tip: To determine if you already have a user name and password for the
Customer Support Web site, visit http://support.cognos.com/support/.
IP-48

INSTRUCTOR
PREFACE
Cognos Product Help

Help type
When to use
Location
Taskoriented
You are working in the product and you

need specific task-oriented help.
Cognos Product - Help link
Books for
Printing
(.pdf)
You want to use search engines to find

information. You can then print out
selected pages, a section, or the whole
book.
Start/Programs/Cognos
Product/Documentation
Use Step-by-Step online books (.pdf) if

you want to know how to complete a
task but prefer to read about it in a book.
The Step-by-Step online books contain
the same information as the online help,
but the method of presentation is
different.
Cognos on
the Web
You want to access any of the following:

Services and Training Web site
http://support.cognos.com
Online support
http://support.cognos.com
Cognos Web site
http://www.cognos.com

IP-49
COGNOS
IP-50
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

SI
Setup Instructions
Cognos 8 BI
COGNOS
SI-2
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

SETUP
INSTRUCTIONS
Important Setup Instructions for This Course

Instructor and Student Computer Checklist
Use the following checklist when configuring both the instructor and
student computers. The total time to set up the instructor and student
computers is 96 minutes.
Setup
Install course student data.

Install Microsoft SQL Server 2000.
Install Microsoft SQL Server 2000 SP3.
Install Microsoft SQL Server KB815495.
Ensure that the proper patches for SQL
Server 2000 are installed.
Ensure you have Internet Information
Services (IIS) installed.
Perform a default installation of the
following Cognos 8.3 RTM (build
number 8.3.81.20-0) components:
Cognos 8 Business Intelligence
Modeling
Server
Samples
Transformer RTM
Note: Do not set up the database and
do not configure Cognos 8.
Page
Est. Time Complete

(per
computer)
SI-5
SI-10
SI-12
SI-13
2 mins
5 mins
5 mins
5 mins
2 mins
SI-14
2 mins
15 mins

SI-3
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
Setup
MODELS
Page
(VERSION
8.3)
Est. Time Complete

(per
computer)
Install Cognos 8 BI Transformer 8.3

Hotsite (Updater) Windows: 8.3.821.
Available on support.cognos.com.
http://support.cognos.com/supported/en/
support/advisories/advc812_1207.html
Create the Cognos 8 Content Store.

Restore the Sample Databases.
Set up Web Aliases.
Configure Cognos 8.
Create Users in Third-party
Authentication Providers.
Deploy and Import Cognos 8 Samples.
Import the Deployment Archives.
Add Data Sources.
Restrict Access to Administrative Tools.
Copy Reports to GO Data Warehouse
(query).
Enable saving to file system in Report
Studio.
Ensure Simple File Sharing is off.
Total Time for setup
SI-4
SI-15
SI-16
SI-18
SI-20
SI-22
2 mins
10 mins
2 mins
10 mins
2 mins
SI-23
SI-24
SI-25
SI-26
SI-27
3 mins
3 mins
2 mins
2 mins
SI-28
SI-29
1 min
96
minutes

SETUP
INSTRUCTIONS
Install Microsoft SQL Server 2000

Use these instructions as a guide to install the SQL Server component. Ensure that you are
logged onto the machine with a valid account, which is the account that will be used to
administer the machine.
Note: If SQL Server 2000 is already installed, go to the section Ensure that the proper
patches for SQL Server 2000 are installed.
1.
2.
3.
4.
Start the install.

Click SQL Server 2000 Components.
Click Install Database Server.
Click Next.

SI-5
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
5.
Click Local Computer, and then click Next.
6.
7.
8.
9.
Click Create a new instance of SQL Server, and then click Next.
Edit the Name, Co., etc., and then click Next.
Accept the License Agreement.
Enter the 25-digit CD Key.
SI-6

SETUP
INSTRUCTIONS
10. Click Server and Client Tools, and then click Next.
11. Select Default as the Instance Name, and then click Next.

SI-7
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
12. Select a Setup Type of Typical, and then click Next.
13. For Services Accounts, click Use the Local System.
SI-8

SETUP
INSTRUCTIONS
14. Click Next.
15. For Authentication Mode, click Mixed Mode, and type Education1! in the
Enter password and Confirm password boxes.
16. Click Next.
17. Click Next again.
The installation continues, and the Microsoft Data Access Components are
installed. The complete installation may take a few minutes.
18. Once the install is complete, click Finish.

SI-9
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Install Microsoft SQL Server 2000 SP3

Use these instructions as a guide to install the SQL Server Service Pack 3. Ensure that you are
logged onto the machine with a valid account, which is the account that will be used to
administer the machine.
1.
2.
3.
4.
5.
SI-10
Start the install.

Click Next on the Welcome page.
Click Yes on the Software Agreement License page.
Click Next on the Instance Name page.
On the page Connect to server, check The SQL Server system administrator
login information (SQL Server authentication). Enter the Education1!
password in the textbox below. Click Next to continue.

SETUP
INSTRUCTIONS
6.
Check Upgrade Microsoft Search and apply SQL Server 2000 SP3
(required), and then click Continue.
7.
8.
9.
Click OK on the Error Reporting page.

Click Next on the Start Copying Files page.
Reboot the machine when prompted.

SI-11
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Install Microsoft SQL Server KB815495
1.
2.
3.
4.
5.
6.
7.
SI-12
You have to install the next patch if you are inside the Cognos network.
This patch is required to eliminate the problem with a virus.
Start the program. The name of the file is SQL2000-KB815495-8.00.0818ENU.exe.
Click Next on the page Hotfix Installer.
Accept the Licensing agreement.
Select the Instance that you want to upgrade. The program usually selects the
local machine.
Click SQL Server Authentication on the page Authentication Mode and type
Education1! as the password in the text box.
Click Install.
Click Finish.

SETUP
INSTRUCTIONS
Ensure that the Proper Patches for SQL Server 2000

are Installed
Use the following instruction to verify that you have the proper patches installed on the
machine. Not having the proper patch level will prevent Cognos 8 to create or use the content
store. Also, a patch is mandatory due to previous experience with a Virus.
1.
2.
3.
4.
5.
6.
Ensure SQL Server is started.

From the Start menu, click All Programs, then click Microsoft SQL Server
and then click Query Analyzer.
Select SQL Server Authentication.
Logon as sa on the database, with the password Education1!.
From the Query window, type select @@version (make sure there is a space
after "select"), and then press the F5 key to run the query.
Expand the column to see the version of MS SQL Server. The portion that you
are interested in is bolded below.
Microsoft SQL Server 2000 - 8.00.818 (Intel X86) May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation Personal Edition on Windows
NT 5.1 (Build 2600: Service Pack 2).
If you have build 8.00.194 then you have to install SP3A and KB815495.
If you have build 8.00.769 then you have to install KB815495.
If you have build 8.00.818 then you have the required patches.
7.
Close SQL Query Analyzer.

SI-13
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Ensure You Have Internet Information Services

Installed
1.
2.
3.
4.
5.
6.
SI-14
Open the Control Panel, and then double-click Add or Remove Programs.
Click Add/Remove Windows Components.
Ensure the Internet Information Services (IIS) check box is selected.
Highlight Internet Information Services (IIS), and then click Details.
Ensure all of the check boxes for the subcomponents are selected.
If any of the check boxes are grayed out, highlight the subcomponent, click
Details, and then select all of the check boxes.
When you are finished, close all of the dialog boxes, and then close the Control
Panel.

SETUP
INSTRUCTIONS
Create the Cognos 8 Content Store

Task 1. Create the Cognos 8 Content Store.
1.
2.
3.
4.
5.
6.
7.
8.
From the Start menu, point to All Programs, Microsoft SQL Server, and
then click Enterprise Manager.
Expand Microsoft SQL Servers and SQL Server Group. (If SQL Server
Group has nothing within it, right-click it and click Register SQL Server.)
Expand <servername>, and then expand Databases.
Right-click Databases, and then click New Database.
The Database Properties dialog box appears.
In the Name box, type cm.
In the Collation name list, select Latin1_General_CI_AS, and then
click OK.
Leave Enterprise Manager open for the next step.

SI-15
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Restore the Sample Databases

Task 1. Unzip the databases.
1.
2.
In Windows Explorer, go to <Cognos 8 install

location>\webcontent\samples\datasources\sqlserver.
Double-click GOSALESDW.ZIP and extract GOSALESDW to the same
location.
Task 2. Add the databases.

1.
2.
Switch back to SQL Server Enterprise Manager, right-click Databases, and

then click New Database.
In the Name box, type GOSALESDW, and then click OK.
Task 3. Restore the databases.

1.
2.
3.
4.
5.
6.
7.
8.
SI-16
Rightclick the GOSALESDW database, point to All Tasks, and then click
Restore Database.
In the Restore database dialog box, click From device.
Under Parameters, click Select Devices.
In the Choose Restore Devices dialog box, click Add.
In the Choose Restore Destination dialog box under File name, click the
Ellipsis and browse to <Cognos 8 install location>\webcontent\
samples\datasources\sqlserver\ GOSALESDW, and then click OK.
Click OK, and then click OK again.
In the Restore database dialog box, click the Options tab.
Select the Force restore over existing database check box.

SETUP
INSTRUCTIONS
9.
In the Restore database files as pane, ensure the Restore as path for both files in
the Move to physical file name column points to the location of the
GOSALESDW database.
If you chose the default location when you created the database, the path
should read, <SQL Sever location>\MSSQL\Data\ GOSALESDW.mdf for
the first file, and <SQL Sever location>\MSSQL\Data\
GOSALESDW_log.ldf for the second file.
Please note: The GOSALESDW.mdf file may be called
GOSALESDW_Data.mdf.
The data file is listed first in the logical file name column, followed by the log
file. If the positions are reversed (in other words, if the log file is listed first),
ensure that each logical file name points to the correct physical file location.
10. Click OK.
A message appears saying the restoration was successful.
11. Click OK to close the message.
12. Close SQL Server Enterprise Manager.

SI-17
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Set up Web Aliases

Task 1. Set up alias for Cognos 8.
1.
2.
3.
4.
5.
6.
7.
8.
From the Control Panel, open Administrative Tools, and then open
Internet Information Services.
In Internet Information Services, expand <servername>, and then expand
Web Sites.
Expand Default Web Site, right-click Default Web Site, point to New, and
then click Virtual Directory.
The Virtual Directory Creation Wizard appears.
Click Next.
Under Alias, type cognos8, and then click Next.
Browse to <Cognos 8 install location>\webcontent, click OK, and then
click Next.
Clear the Run scripts check box, so only Read is selected, and then click
Next.
Click Finish.
Task 2. Set up virtual directory for cgibin.

1.
2.
3.
4.
5.
6.
SI-18
Right-click the cognos8 virtual directory folder, point to New, and then click
Virtual Directory.
Click Next.
Under Alias, type cgi-bin, and then click Next.
Browse to <Cognos 8 install location>\cgi-bin, click OK, and then click
Next.
Select the Execute check box, deselect the Read and Run scripts check
boxes, and then click Next.
Click Finish.

SETUP
INSTRUCTIONS
Task 3. Set up virtual directory for help.

1.
2.
3.
4.
5.
6.
Right-click the cognos8 virtual directory folder, point to New, and then click
Virtual Directory.
Click Next.
Under Alias, type help, and then click Next.
Browse to <Cognos 8 install location>\webcontent\documentation, click
OK, and then click Next.
Clear the Run scripts check box, so that only Read is selected, and then click
Next.
Click Finish.
Task 4. Give browse access to images.

1.
2.
3.
4.
5.
Expand the samples folder.

Right-click images, and then click Properties.
In the images Properties dialog box under the Directory tab, select the
Directory browsing check box.
Click OK.
Close IIS.

SI-19
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Configure Cognos 8
Task 1. Configure the NTLM provider.
1.
2.
3.
4.
5.
6.
7.
8.
From the Start menu, point to All Programs, Cognos 8, and then click
Cognos Configuration.
In the Explorer pane of Cognos Configuration, right-click Authentication,
point to New resource, and then click Namespace.
In the New Resource - Namespace dialog box, under Name, type Local NT,
and then from the drop-down list under Type, click NTLM.
Click OK.
Click the cell in the Namespace ID row and the Value column, and type Local
NT ID, and then press Enter.
In the Explorer pane under Authentication, click Cognos.
To the right of Allow anonymous access, click True in the Value column, and
then click False to change the setting.
With Anonymous access now set to False, students will need to log in to
Cognos Connection and provide a user name and password.
Leave Cognos Configuration open.
Task 2. Enable file saving and set root directory for saving
files.
1.
2.
3.
4.
SI-20
In Cognos Configuration, expand Data Access, Content Manager.

Click Content Manager, and then ensure that Save report outputs to a file
system? is set to True.
From the Actions menu, click Edit Global Configuration, and then click the
General tab.
Ensure that Archive Location File System Root is set to
file://c:/Edcognos/C88382.

SETUP
INSTRUCTIONS
Task 3. Configure the content store.

1.
2.
3.
4.
5.
6.
7.
In the Explorer pane, under Content Manager, click Content Store.

Click the User ID and password row, and then in the Value column, click the
Edit button.
In the Password field and the Confirm password field, type Education1!, and
then click OK.
Right-click Content Store, and then click Test.
Click Close when the test is complete.
to save the new configuration.
Click Save configuration
Click Close to close the Cognos Configuration dialog box after the
configuration is saved and all items have green check marks beside them.
to start the Cognos 8 service. You will receive a warning about

Click Start
the mail server message. It can be ignored.
9. When all services are started, click Close.
10. Close Cognos Configuration.
8.

SI-21
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Create Users in Third-party Authentication Providers

Task 1. Create users in the NTLM authentication provider.
1.
2.
From the Start menu, click Control Panel, and then double-click
Administrative Tools.
Double-click Computer Management.
3.
Expand Local Users and Groups.
4.
Right-click Users, and then click New User.
5.
In the New User dialog box, in the User name box, type admin and then in
the password and confirm password boxes, type Education1!.
6.
Clear the User must change password at next logon check box, select the
Password never expires check box, and then click Create.
7.
Repeat steps 4 to 6 to create the following three users:

Full name: Admin Person User id: admin password: Education1!
Full name: Harold Townsend User id: townsenh, password: Education1!
Full name: Brendon Pike User id: pikeb, password: Education1!
Full name: Alessandra Torta User id: tortaa, password: Education1!
Full name: Donald Chow User id: chowd, password: Education1!
Full name: Silvano Allessori User id: allessos, password: Education1!
Full name: John Sinden User id: sindenj, password: Education1!
8.
Click Close to close the dialog box.
9.
In the left pane, click Users to ensure that the users have been added.
10. Close the Computer Management window, and then close Administrative
Tools.
SI-22

SETUP
INSTRUCTIONS
Deploy and Import Cognos 8 Samples

Task 1. Prepare for deployment.
1.
2.
3.
4.
Open Windows Explorer.

Navigate to <Cognos 8 install location>\webcontent\samples\content.
Copy the Cognos_Samples.zip file.
Navigate to <Cognos 8 install location>\deployment, and then paste the
zip files.
Task 2. Import the samples.

1.
2.
3.
4.
Open Internet Explorer, and then in the Address box, type

http://localhost/cognos8, and press Enter.
In the User ID box, type admin, in the Password box, type Education1!, and
then click OK.
Under Administration, click Administer Cognos content, click the
Configuration tab, and then click Content Administration.
On the toolbar, click New Import
5.
On the Select a deployment archive page, ensure the Cognos_Samples archive

is selected, and then click Next.
6. On the Specify name and descriptions page, click Next.
7. On the Select the public folders content page, select GO Data Warehouse
(query) and GO Data Warehouse (analysis), and then click Next.
8. On the Specify the general options page, click Next.
9. On the Review the summary page, click Next.
10. On the Select an action page, ensure Save and run once is selected, and then
click Finish.
11. On the Run with options page, ensure Now is selected, click Run, and then
click OK.
12. Leave your browser open.

SI-23
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Import the Deployment Archives

Task 1. Prepare for deployment.
1.
2.
3.
Open Windows Explorer, and then navigate to

C:\Edcognos\C88382\Instructor Files.
Copy the OLAP reports.zip file.
Navigate to <Cognos 8 install location>\deployment, and then paste the
zip files.
Task 2. Import .
1.
In Cognos Administration, on the Configuration tab, click Content

Administration, and then click New Import
2.
On the Select a deployment archive page, ensure the OLAP reports.zip

archive is selected, and then click Next.
3. On the Specify name and descriptions page, click Next.
4. On the Select the public folders content page, select OLAP reports.zip, and
then click Next.
5. On the Select the directory content page, click Next.
6. On the Specify the general options page, click Next.
7. On the Review the summary page, click Next.
8. On the Select an action page, ensure Save and run once is selected, and then
click Finish.
9. On the Run with options page, ensure Now is selected, click Run, and then
click OK.
10. Leave your browser open.
SI-24

SETUP
INSTRUCTIONS
Add Data Sources

Task 1. Create data sources.
1.
In Cognos Administration, from the Configuration tab, click Data Source

Connections.
2.
On the toolbar, click New Data Source
3.
4.
5.
Under Name, type great_outdoors_warehouse , and then click Next.

Under Type, select Microsoft SQL Server (OLE DB), and then click Next.
In the Server name box, type localhost, and then under Database name, type
GOSALESDW.
Under Signon, select the Password check box.
6.
7.
In the User ID box, type sa, and in the Password and Confirm password boxes,
type Education1!, and then click Finish.

SI-25
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Restrict Access to Administrative Tools

1.
In Cognos Connection, in Cognos Administration, click the Security tab, and

then click Users, Groups, and Roles.
2.
Under the Name column, click Cognos, click Next Page

the System Administrators role, click Set properties
3.
4.
5.
SI-26
On the Set properties - System Administrators page, click the Members tab.
Click Add, select the Show users in the list check box, and then click Local
NT.
Select the Admin Person (admin) check box, click the green arrow and then
click OK.
You may need to click Next Page
6.
7.
, and then beside
to locate the Admin Person user.
Select the Everyone check box, click Remove, and then click OK.
Leave Cognos Connection open.

SETUP
INSTRUCTIONS
Copy Reports to Go Data Warehouse (query)

1.
2.
3.
4.
5.
Return to Public folders.

Click the OLAP reports folder.
Copy all reports.
Navigate to Go Data Warehouse (query) and paste the reports in this folder.
In Public Folders, delete the OLAP reports folder.

SI-27
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Enable Saving to File System in Report Studio.

Task 1. Create subdirectories that can be used.
Component: Cognos Administration (Administer Cognos content)
Configuration tab
Dispatchers and Services
1.
Click Define File System Locations
2.
3.
Click New.
In the Name box, type Output Reports.
This is the name that users will see in Cognos 8, when they save a file.
In the File system location box, type csv files, and then click Finish.
Click Close.
4.
5.
SI-28

SETUP
INSTRUCTIONS
Ensure Simple File Sharing is Off (for VMWare

images only)
1.
2.
3.
4.
From the Start menu, navigate to Control Panel\Folder Options.

Ensure the View tab is selected, and then deselect the Use Simple File
Sharing (Recommended) check box.
Click OK.
Close Control Panel.

SI-29
COGNOS
SI-30
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

Intro
Introduction
Cognos 8 BI
COGNOS
Intro-2
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

INTRODUCTION
Course Objectives
At the end of this course, you should be able to:
discuss the fundamentals of OLAP modeling
work with data sources and build a model
use multiple data sources and address uniqueness
work with measures and currency conversion
customize cube content
apply Cognos 8 security
maintain and optimize models and PowerCubes
model for drill-through access
identify common data structures

Intro-3
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Building a Model
The Time Dimension
Relative Time
Cognos 8 BI Transformer: Designing
OLAP Models (version 8.3)
Cognos 8 BI Transformer: Designing OLAP Models (version 8.3) is a four-day,

instructor-led course that teaches OLAP modelers how to design, build, and maintain
PowerCubes for use with Cognos 8 BI. Attendees will participate in hands-on demos
and workshops that illustrate key concepts while learning how to use the product.
Intended Audience:
OLAP Modelers who will build PowerCubes for use in Cognos 8 BI
Prerequisites:
Understand the business need for ad hoc queries and analysis
Cognos 8 BI: Reporting and Analyzing Data for Business Authors (version 8.3)
(recommended)
Experience using basic Windows functionality
Intro-4

INTRODUCTION
Uniqueness
Allocated Measures
Currency Conversion
Alternate Hierarchies within a Dimension
Advanced Dimensional Modeling
Customize Cube Content
Examine Cognos 8 Security
Applying Security

Intro-5
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Optimizing PowerCubes
Partition a PowerCube
Maintain Models and PowerCubes
Model for Drill-Through
Identify Common Data Structures
(Optional)

Intro-6

INTRODUCTION
Additional Training
After completing this course, please visit
http://support.cognos.com/training to find more
information about:
additional training to enhance your knowledge and

skills with Cognos products
the Cognos certification program, which:

recognizes
individuals who have obtained superior

knowledge and skills with Cognos products
provides
expertise
the flexibility to certify in a chosen area of

Intro-7
COGNOS
Intro-8
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

Cognos 8 BI
COGNOS
1-2
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

OVERVIEW
OF
COGNOS
BI
Objectives
At the end of this module, you should be able to:
Discuss Cognos 8 and Performance Management
Describe Cognos 8 BI components
Define Cognos 8 BI groups and roles
Explain how to extend Cognos 8 BI
Instructor Notes
This module is a shared module used in several courses. The intent of this module is to help students
understand where they fit into the Cognos 8 BI infrastructure. Tailor your delivery to your audience. You
can stay high level or go into as much detail as you think is appropriate.

1-3
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Examine Performance Management

(PM)
Good decisions are the building blocks of great
business performance.
Understand and improve your business based on:
How are we doing?
Why?
What should we be doing?
Cognos provides performance management through

software, services, best-practices, and partners.
Use Cognos 8 as an open enterprise-class platform to answer the following:

How are we doing? Measuring and monitoring performance with scorecards and
dashboards tracks your key metrics.
Why? Reporting and analysis let you see data, gain context, understand trends,
and spot anomalies.
What should we be doing? Planning, budgets, and forecasts let you set and share
a reliable view of the future.
Instructor Notes
Cognos 8 consists of planning, business intelligence and consolidation and financial reporting. It uses
one underlying architecture and the components are all part of one solution.
1-4

OVERVIEW
OF
COGNOS
BI
Cognos 8 BI Components
Cognos 8 Cognos Query Report Analysis
Viewer Studio Studio Studio
Portal
Framework Manager
Multidimensional
Relational
Event
Studio
Metric
Admin
Studio
Transformer
Files
More
Cognos 8
Content
Cognos 8 BI capabilities provide reporting, analysis, scorecarding, dashboarding,

business event management, and data integration. Cognos 8 BI includes a portal for BI
content presentation, management, and administration, and various studios to author
and analyze corporate data. You can access a wide array of data sources and leverage
your existing security infrastructure.
Framework Manager is a metadata modeling tool used to create basic query packages or
multidimensional analysis packages and Transformer is a modeling tool used to create
PowerCubes for multidimensional analysis. These sources are used by authors and
analysts in the Cognos 8 environment.
Instructor Notes
Metric Studio helps to manage your organization's performance by monitoring and analyzing metrics at
all levels.
Query Studio helps you quickly answer a focused question.
Analysis Studio performs analyses of data to discover trends, risks, and opportunities.
Report Studio builds sophisticated reports, including multi-page, multiple-query reports against multiple
data sources.
Event Studio notifies users of key operational or performance-related events that may affect their
business.

1-5
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Cognos 8 Groups and Roles

Cognos 8 provides default groups and roles for
security such as:
System
Administrators
Authors,
Query Users,
Analysis Users
Consumers,
Readers
Take advantage of Cognos 8 groups and roles to secure your Cognos 8 BI environment
and content. The group or role a user belongs to will determine how much access they
have to the Cognos 8 BI environment. For example, if you are a member of only the
Consumers role, you cannot access any of the Cognos 8 studios.
Besides the default groups and roles, you can create new groups and roles that are
specific to your Cognos 8 BI needs. Simply add users from your authentication source
to specific groups and roles as required.
Instructor Notes
You can use the groups and roles defined in the Cognos Namespace as well as in your authentication
provider to control access to content.
There are many different groups and roles the administrator can use to restrict what you can see, what
you can do etc.
See the Predefined Entries section of the Administration and Security Guide for detailed information on
the predefined groups and roles as well as the anonymous user.
1-6

OVERVIEW
OF
COGNOS
BI
Extend Cognos 8 BI
Cognos provides a wide variety of ways to extend
Cognos 8 BI.
For more information, please visit www.cognos.com.
Instructor Notes
Cognos products that Extend Cognos 8 BI include:
Cognos 8 Planning (helps you plan for the future through planning, budgeting, forecasting, and
modeling)
Cognos 8 Go! Office (integrate C8 content with MS Office)
Cognos 8 Go! Mobile (C8 content on mobile devices)
Cognos 8 Go! Search (expanded and integrated search capabilities for C8 content)
Cognos 8 BI Analysis for Microsoft Excel (multidimensional analysis on Cognos 8 BI data in a
MS Excel spreadsheets)
For developers, there is also Composite, which allows for access to an even wider variety of data
sources, and the Cognos 8 SDK for customization and application development.
Cognos Now delivers highly visual, interactive, and self-service dashboards, data integration, analysis,
and reports, all prepackaged in a hardware appliance.
This would be a good time for an ad hoc demo of the Cognos 8 BI portal and the studios. For example:
Show Cognos Connection and how reports are organized. Run an RS report to view it. Open Analysis
Studio and create a quick high level analysis. Drill down, and add a function (perhaps a top count).
Open Query Studio, create a quick list report, pivot to a cross tab, and then show a chart. Then open
the Query Studio report in Report Studio, add some formatting, a quick calculation, a company logo
and run. Save the report to Cognos Connection and point it out there.
1-7
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Summary
1-8
Discuss Cognos 8 and Performance Management
Describe Cognos 8 BI components
Define Cognos 8 BI groups and roles
Explain how to extend Cognos 8 BI

Cognos 8 BI
COGNOS
2-2
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

TRANSFORMER
FUNDAMENTALS
Objectives
discuss the basics of OLAP analysis
discuss the importance of business requirements
review Transformer and Cognos 8 BI components
define categories and members
Instructor Notes
If you intend to teach this module, students should be familiar with:
SQL
the business need for ad hoc data exploration and analysis

2-3
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Business Intelligence
Business intelligence helps people to:
use corporate data to support decision making
explore and analyze data to reveal trends within a

business
Raw Data
Organized Information
Better Business Decisions

Business intelligence is a broad category of application programs and technology used
to gather, store, analyze, and provide access to data.
Business intelligence is accomplished through activities of decision support, query and
reporting, Online Analytical Processing (OLAP), statistical analysis, forecasting, and
data mining.
Business intelligence provides you with the ability to apply comprehensive knowledge
and insights to manipulate the actual drivers of business performance.
Instructor Notes
With business intelligence software, your business can:
create an information infrastructure that supports nimble decision-making to maximize the
success of your organization
look inside the data to investigate and analyze the business
make it possible for all employees to contribute their business knowledge and insights to the
factors that drive your organization's performance
take action based on the information discovered to make better business decisions.
2-4

TRANSFORMER
FUNDAMENTALS
Dimensional Analysis Example

Comprehensive Analysis
When?
Time
(2007)
Who?
Customers
(Channels)
What?
Product
(Type)
Where?
Location
(Region)
Result?
Indicator
(Revenue)
Combination 1
Quarter
Month
Type
Customer
Line
Brand
Number
Country
Branch
Sales Rep
Quantity
Cost
Margin
Type
Customer
Line
Brand
Number
Country
Branch
Sales Rep
Quantity
Cost
Margin
Combination 2
Quarter
Month
Dimensional analysis is a process where you selectively extract and evaluate multiple
aspects of your business against your key performance indicators for the purpose of
decision support.
Dimensional analysis increases your understanding of the data and accelerates your
ability to make decisions.
Instructor Notes
Corporate data is organized in the way you think about your business, so that you spend more time on
value added analysis, rather than on data retrieval. You can find answers to your business questions
by navigating through the data to determine successes and failures, uncover trends, discover
opportunities, and find weaknesses. For example, a comprehensive sales analysis requires you to
examine key performance indicators within your business in relation to time, products, customers,
regions, sales reps, and sales channels. The combination of views to investigate is enormous. With
multidimensional analysis, you can examine each combination while you navigate the data. You
increase your knowledge, and can make immediate decisions to impact the business performance.
2-5
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Examine OLAP Data Structures

Products
Order Methods
Camping Equipment
Dimension
Golf Equipment
Cell
Fax
Outdoor Protection
Telephone
Members
Mountaineering
Equipment
Mail
Personal Accessories
E-Mail
Jan
Feb
Q1
...
Q2
2005
Web
Start
April 1
...
2006
...
Attributes
Time
Hierarchy/Levels
2005 Q1
Q2
End
June 30
Q3
Q4
The OLAP structure consists of the following elements:

dimensions - contain members/categories, which may be structured into
hierarchies and levels
members/categories - data entities that provide context to cell values
hierarchies - provide context to the level structures they contain
levels - provide structure for the members/categories of a hierarchy
attributes - provide additional information for members/categories
cells - are intersection points containing values (measures) for various
members/categories from different dimensions (also referred to as tuples)
2-6

TRANSFORMER
FUNDAMENTALS
Benefits of Transformer
Transformer is:
easy to customize, flexible, and portable
designed for production environments
Users
OLAP
Analysis
and
Reporting
PowerCube
Transformer models help you structure data from various sources into
multidimensional PowerCubes.
Begin by assessing the data and deciding how to organize it to support the types of
business analysis that are important to you.
Transformer accepts data from Impromptu files (.iqd), flat files, and most spreadsheet
and database applications, with or without column headings, and compresses the data
into a compact PowerCube.
Instructor Notes
Additional benefits of Transformer are:
automatic aggregate creation
advanced modeling capabilities
reads multiple data sources
leverages aggregate and fact tables
2-7
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Business Requirements
The business requirements impact every aspect of the
model and cube. By keeping these requirements at
the center of your design, you can better serve the
decision- makers in your organization.
Dimensional Technical
Modeling
Architecture
Design
Project
Physical
Planning and
Design
Business
Management
Requirements
Maintenance
Data Staging
and Growth
Design
Deployment End-User
Application
Planning
Specification
Understanding your users and the business is the cornerstone for success in
implementing a successful application.
Choose people who know the company's objectives and who can describe the
company's key performance indicators, top concerns, and expectations.
Involve people who know the technical infrastructure and the data sources, and who
will be involved in prototypes, production, and ongoing maintenance.
Find out what users need to do with the data, how they use the data, and what types of
reports they create with the data.
Instructor Notes
The slide discusses the importance of determining the business requirements. In some cases, this
information may help to determine the project scope and possible schedules. The business
requirements will impact several areas in your organization. Make sure you talk to people before you
start with the tools.
2-8

TRANSFORMER
FUNDAMENTALS
What is a Model?
A model is a structure that organizes data on the basis of dimensions.

A model can be used to build one or more cubes, and can be processed locally or on
the server.
Instructor Notes
Transformer compiles the following components into a model:
Source Files: Source files are data sources. Data sources can be structural (text) or
transactional (numeric). Refer to the module titled, "Data Sources in Transformer".
Dimension Map: A dimension map is a table that displays all the dimensions in the model and
the levels they contain. Refer the module titled, "Building a Model".
Measures: A measure is a value to be used as a key performance indicator for the business.
Custom Views: You can add custom views to a cube

2-9
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Model Types
Transformer can save models as the following two
types of files:
.mdl - a model stored in ASCII file format is a

smaller size, compatible between versions of
Transformer, and can be used for find and
replace activities
.pyj - a model stored in binary file format is a

larger size, version-specific, and quicker to load
An .mdl file can be opened in Transformer or any text editor. It will never be larger
than necessary as it replaces, rather than appends, and rarely corrupts.
We recommend that you periodically save the .pyj model file as an .mdl file, open the
file in Transformer, and then save it again as the default .pyj file to eliminate the
fragmentation associated with the .pyj file.
Instructor Notes
.mdl files: can also be a script to automate Transformer, contain only definitions of objects, files, are
upwardly compatible between versions, are backwards compatible within the same version, are slow to
open since the file is not compiled.
.pyj files: are not upwardly compatible between versions, are not backwards compatible within the
same version, are quick to open since the file is already compiled, can become excessively large, and
sometimes corrupt, with frequent modifications, actually contain the objects.
2-10

TRANSFORMER
FUNDAMENTALS
From Model to PowerCube

1. Import your data source
Do I have the data that meets my

needs and my user's needs?
2. Create and examine

your measures
Do they reflect how you measure the

performance of your business?
3. Create and examine

your dimensions and
levels
4. Create and test

your PowerCubes
Do they allow effective data

analysis?
Does it provide the right
information in a way that is easy
to understand and work with?
Building a PowerCube is an iterative process. You may build several PowerCubes

before you meet the requirements the users define.
Instructor Notes
Tips for model creation:
Avoid redundant processing with incremental builds.
Choose the right PowerCube creation process.
Perform regular model maintenance.

2-11
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
What is a PowerCube?
a structure that stores data dimensionally and
provides:
secure data access
fast retrieval of data
can be distributed across a network or to individual

computers.
From well-designed cubes, you can create reports in minutes (rather than days, weeks,
or months) that you can use to analyze your business to capitalize on the opportunities
presented.
PowerCubes are static, which means they must be updated periodically. PowerCubes
store data at summarized levels.
Instructor Notes
Example: a spreadsheet contains transaction data records. A cube contains the summary statistics
based on the transaction data records from the spreadsheet.
Traditional relational databases present data as a series of two-dimensional tables that show the
relationships among variables. A PowerCube structure expands the number of dimensions from two, to
three, or more. It is possible to store more detailed information in the PowerCubes. However, this is not
recommended because it increases the size of the PowerCubes considerably. As an alternative, drillthrough functionality is available. When you create a default or standard PowerCube, the resulting .mdc
file contains all the cube data.
2-12

TRANSFORMER
FUNDAMENTALS
Measures
A measure can:
provide quantifiable results that gauge the success

of your business
address primarily numeric questions
add perspective to your data
You must have at least one defined measure to build a PowerCube. Measures play a
valuable role in extending the use of the application because they:
represent the key performance indicators used to gauge the success of your
business
help you to view the performance of the business from a different perspective
typically come from Fact table data in a database
Instructor Notes
A regular measure is numeric data available in a corporate transaction file. A calculated measure is
new numeric data that is derived from other measures, functions, and constants. You can add
additional measures to the model, that are not included as part of the user requirements, to enhance
data analysis. For example, if a user requested measure values for revenue, quantity, and cost, you
might consider adding measure values for average cost and profit margin. This means that users can
analyze data in different ways.
2-13
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
What are Dimensions and Levels?
Question to
be answered
Dimensions
Levels
When
What
Where
Who
How
Dim 1
Dim 2
Dim 3
Dim 4
Dim 5
Time
Products
Regions
Years
Product line
Region
Quarters Product type
Country
Months
Product name
City
Employee
Dimensions are the highest levels of descriptive data. Common dimensions tend to
deal with the major aspects of the business, such as date, products, and regions. They
typically address the questions of when, what, where, who, and how.
Dimensions are made up of levels. Each subordinate level provides increasingly
detailed data that relates to the dimension.
Levels represent the hierarchy established by the organizational structures and data
models that your organization uses.
2-14

TRANSFORMER
FUNDAMENTALS
Additional Dimensions
Dimension
Levels
When
What
Where
Dim 1
Dim 2
Time
Years
2 Quarters
3
Months
Who
How
Dim 3
Dim 4
Dim 5
Products
Regions
Retailer
types
Margin
Ranges
Product
line
Regions
Retailer
type
Margin
Range
Product
type
Product
Name
Country
City
Employee
After you define the initial dimensions and their levels, you can determine whether
other descriptive data can be added to enhance the analysis of your application.
You can create exception dimensions, or new ways of slicing and dicing the data based
on a calculation from existing source columns. For example, you can use Margin Range
to track critical success factors that constitute an exception in the business.
Instructor Notes
Exception Dimensions are created using calculated columns. Calculated columns are expressions that
use other columns, functions, and constants to derive new data for the model. Calculated columns can
be used in a dimension structure to create new ways of slicing and dicing data.
If (Margin < .30) then (LOW) else if (Margin > .70) then (HIGH) else (MEDIUM)
When you add a new exception dimension in the sales analysis model, you can address how many
products are sold within a given margin range and in what margin range different products are selling.
Exception dimensions are created either in the source data or within Transformer by using a
calculation.
2-15
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Categories/Members
In Transformer, categories are individual data items
that populate a level in a dimension.
In Cognos 8, these items are called members.
Level:
Region
Level:
Country
Level:
City
Category/
Member:
Categories/
Members:
Category/
Member:
Norway
Northern
Europe
Sweden
Denmark
Kista
Finland
Categories/Members are the individual data elements that describe or classify details of
your organization. Each level in a dimension has its own set of categories/members.
Instructor Notes
IMPORTANT: Member is the C8 terminology. However the Transformer 8.3 product uses the term
"category" inside the product. Have a small discussion that a category and member are different names
for the same object. When working inside the C8 studios, you will often see the terminology of
"member" but when working inside the Transformer product - the terminology will be "category".
Categories can be different levels of information within a dimension or can be grouped into more
general categories. For example, a set of dates could be grouped into a month, months into quarters,
and quarters into years.
2-16

TRANSFORMER
FUNDAMENTALS
Summary
discuss the basics of OLAP analysis
discuss the importance of business requirements
review Transformer and Cognos 8 BI components
define categories and members

2-17
COGNOS
2-18
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

The Transformer Development

Process
Cognos 8 BI
Instructor Notes
Unless specified otherwise in demo or workshop steps, instructors and students will always log on to
Cognos 8 in the Local NT namespace using the following credentials:
User ID: admin
Password: Education1!
COGNOS
3-2
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

THE
TRANSFORMER
DEVELOPMENT
PROCESS
Objectives
describe the purpose of a model plan
match business requirements to the model
discuss an approach for creating a model plan
review the relationship of the model plan to the

Transformer model
Instructor notes:
Students should be familiar with:
Transformer model concepts
Multidimensional analysis

3-3
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Model Requirements
Us
er
Re
qu
ire
m
en
ts
P
el
od
lan
PowerCube
r
po
e
R
ir
qu
e
tR
em
Ad
di
Re tion
qu al R
ir e
me epor
n ts t
ts
en
Before you create a model plan, you should complete these tasks:
1. Meet with users to gather requirements.
2. Translate user requirements into report requirements.
3. Consider adding report requirements that were not requested by users but
would enhance analysis of the overall application.
4. Transfer the report requirements onto a model plan.
Instructor Notes
Identifying and confirming user requirements is critical to user satisfaction and the success of a project.
Before you develop the model, you should give users the opportunity to approve the final design phase
of the model plan. The model plan should be consulted and updated at regular intervals throughout
your development phase, particularly when modifications are made to the information being included in
the model.
3-4

THE
TRANSFORMER
DEVELOPMENT
PROCESS
Model Plan
helps identify required data
helps assess required work
proposes the model design
guides the creation of the model
The model plan outlines the design and data requirements of the Transformer model. It
is the starting point in the development of any Transformer model and is created and
controlled by the administrator.

3-5
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Create a Model Plan

Considerations when creating a model plan:
select the appropriate measures
seven dimensions or less can be viewed at a

glance
five to seven levels per dimension are easier to

navigate
a parent-child ratio of 1:10 for categories from

level to level makes it easier to analyze the data
When designing your model plan:

Select measures that address the critical success factors of the business area in
question.
Visualize how it will appear to the end user. Consider the position of the first
two dimensions, the first measure, and the level structure.
Instructor Notes
Q. Why is including more information into a model not necessarily better? A. It may not improve the
quality of the analysis. An application that contains less data provides increased performance.
Q. Why do you recommend approximately seven or less dimensions in the model? A. Fewer
dimensions make an application easier to use.
Q. Why do you recommend five to seven levels in a dimension? A. the application will be faster and
easier to navigate.
Q. Why do you recommend a Drill Ratio 1:10 from level to level? A. Better design. When the ratio is
large, consider introducing an intermediary level to accommodate the unbalanced dimension.
3-6

THE
TRANSFORMER
DEVELOPMENT
PROCESS
Model Plan Components

Questions to
answer:
When
What
Where
Who
How
Dim 1
Dim 2
Dim 3
Dim 4
Dim 5
Dimension
Name:
Time
Products
Regions
Retailers
Margin
Range
Levels:
Year
Product
Line
Region
Retailer
Type
Margin
Range
Quarter
Product
Type
Country
Retailer
Name
Month
Product
Name
City
Measures:
Revenue, Quantity, Product cost
The model plan:

is a design document that provides a visual representation of the dimensions,
levels, and measures to be analyzed in the Transformer model.
summarizes the business requirements into a structure that the model is based
on.
By planning the model, you can establish which data sources are required and what data
is missing.
Instructor Notes
Components of the plan include:
questions to be answered, based on the results your users require
dimensions, which are determined by the data required to answer the questions
levels, which are established by the users and the degree of exploring information needed
measures, which are required in the exploration and analysis of the results

3-7
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Add Components to the Transformer

Model
A Transformer model includes four main components.
Dimension
Map
Data Sources List
Measures List
PowerCubes List
You create or modify a Transformer model by applying the values outlined in the
model plan. By adhering to the model plan, you can make sure that the application
design meets the user's needs.
Instructor Notes
Discuss the four main components of the model and how the model plan relates to each of the
components.
The Dimension Map is used to build and display the model dimensions and their level structure based
on the data source. Use the model plan, along with the data from the Data Sources list, to build the
dimension map. The dimension map is a table that shows:
dimensions located in its top row.
levels in a vertical hierarchy for each dimension (the hierarchy of levels represents the drill path,
and each level contains attributes for all its member categories).
3-8

THE
TRANSFORMER
DEVELOPMENT
PROCESS
Demo 1: Set Preferences

Purpose:
You want to set the default directory preferences for the location of
models, data sources, PowerCubes, and log files.
Task 1. Start Transformer and set the directory preferences.
1.
2.
3.
4.
5.
6.
7.
8.
9.
Start Transformer.
From the File menu, click Preferences.
Click the Directories tab.
All the files you need are located in folders in C:\Edcognos\C88382;
therefore, you want to set this location as your default for models, data sources,
PowerCubes, and log files.
Under Models, click Browse.
Navigate to C:\Edcognos\C88382, and then click OK.
Under Data source, change the path to C:\Edcognos\C88382.
Under PowerCubes, change the path to C:\Edcognos\C88382.
Under Log files, change the path to C:\Edcognos\C88382.
Close the Preferences dialog box, and leave Transformer open.
Results:
You started Transformer and set the directory preferences to
C:\Edcognos\C88382.
Instructor Notes
Point out that the Temporary file location specifies the name of the directory to create a temporary file
while you work on the model. The temporary file is also used to recover a suspended model at strategic
checkpoints should a fatal error occur.

3-9
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Demo 2: The Transformer Model

Purpose:
In this demo, you will identify the four main components of
Transformer and learn to recognize dimensions, levels, measures,
and categories.
Task 1. Open an existing model in Transformer.
1.
Open Sales and Marketing.mdl.

Location: C:\Program Files\cognos\c8\webcontent\samples\Models\
Transformer8\EN\Sales and Marketing.mdl
Task 2. Identify the four main components in Transformer and

review the dimensions, levels, and measures in a
model.
1.
2.
3.
3-10
Click the Data Sources list title bar.

The Data Sources list title bar and the data source named GO Data Warehouse
(query) are highlighted.
Expand the GO Data Warehouse (query) data source.
This package appears as a single container data source, and it has one query
belonging to it.
Expand the GO Data Warehouse query.
The columns in the GO Data Warehouse query provide the data required to
build the application. A query has its own definition, where you can add or
modify columns, as necessary, as well as preview data and SQL.

THE
4.
5.
6.
7.
8.
TRANSFORMER
DEVELOPMENT
PROCESS
Click the Dimension Map.

The dimension map title bar is highlighted. The dimension map was created
using the columns from the data source.
On the dimension map, click the Time dimension label.
This dimension is the first in the model. Other dimensions are Products,
Product brand, Retailers, Promotions and Order method.
In the Time dimension, click the Year level label.
This level is the first in the Time dimension. Lower levels in the Time
dimension are Quarter and Month. This order illustrates the drill-down path for
the Time dimension.
Click the Measures list.
The Measures list title bar is highlighted. There are numerous defined measures
in this model. The measures will appear in the same order in the Insertable
Objects pane in the Cognos 8 Studios.
Click the PowerCubes list.
The PowerCubes list title bar and the Sales and Marketing PowerCube are
highlighted.
Task 3. Identify categories in a model.

1. On the dimension map, click the Products dimension.
2.
Click Show Diagram
3.
Maximize the dimension diagram window, click in the dimension diagram, and
then press Home.
This is one method to fit the dimension diagram in your window.

3-11
COGNOS
4.
5.
6.
7.
8.
9.
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Locate the Product line label, which has a light blue label color.
The categories for Product Line are Camping Equipment, Personal Accessories,
Outdoor Protection, Golf Equipment, and Mountaineering Equipment.
Expand Personal Accessories.
The Product type categories for Personal Accessories are Watches, Eyewear,
Knives, Binoculars, and Navigation.
Expand Knives.
The categories are Single Edge, Double Edge, Edge Extreme, Bear Edge, Bear
Survival Edge, and so on.
Close the dimension diagram.
From the View menu, click Default View.
You would typically create a PowerCube based on the model.
By default, the PowerCube generation process generates categories and a
PowerCube called Sales and Marketing is added to the PowerCubes list. You
can publish this PowerCube directly to Cognos Connection for consumption
within the studios.
Close the model without saving.
Results:
You identified the four main components of Transformer and
identified dimensions, levels, measures, and categories.
3-12

THE
TRANSFORMER
DEVELOPMENT
PROCESS
Summary
describe the purpose of a model plan
match business requirements to the model
discuss an approach for creating a model plan
review the relationship of the model plan to the

Transformer model

3-13
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Workshop 1: Create an Example Model Plan

You are asked to develop a system to track performance against a quality measurement.
Your objective for the pilot stage of this project is to create an application that meets
the needs of the Finance and Inventory Control organizations.
Read the company's method of analysis and user requirements. Use this information to
complete the design on a blank model plan. Identify the following:
a time dimension
three primary dimensions
an exception dimension
levels for each dimension
measures
Instructor Notes
Following the workshop slide in the PowerPoint presentation is an additional slide called "Example
Model Plan Results". This slide can be shown after Students have completed the workshop.
3-14

THE
TRANSFORMER
DEVELOPMENT
PROCESS
The company analyzes their business and makes decisions based on several factors:
Factor
Description
Dates
Dates are organized in three levels - Year, Quarters, and Months based on a fiscal year of March to February.
Products are analyzed by Product line. For Product line analysis, the
company sells multiple product lines; each product line has more than
one Product type, and each type has more than one Product name.
The company sells to different geographic regions worldwide. Within
each region are countries and cities, in which employees are based.
Products
Regions
Retailer
Types
% Late
Shipment
Ranges
Each Retailer is categorized into multiple types, depending on the

retailer's business emphasis. Each Retailer type has more than one
Retailer.
Analysis is performed on % Late Shipment Ranges orders. The records
are flagged with a rating of GOOD, AVERAGE, or POOR,
depending on what percentage of the shipments are late.

3-15
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
To define the reporting objectives, the Finance and Inventory Control organizations
provided the following user requirements.
User
Requirements
Finance
Inventory
Control
3-16
Monitors success by analyzing the revenue figures, number of units

shipped, price of the orders being placed for all products, and percentage
of late shipments. For retailer accounts, you must know the total number
of units that are shipped. Of those units shipped, you need to determine
how many were shipped late. If the percentage is high, you need to be
informed so that you can rectify the problem. Our retailers should not
suffer because products are shipped late.
Revenue is the primary performance indicator used to measure our
success. To get an accurate picture of revenue, you want to know how
much revenue is generated from all the product shipments. Of that
revenue, you are interested in how much revenue was derived from late
shipments.
Finally, it is valuable to know what the average shipment revenue is for all
products and retailers. You may be able to identify a more efficient way
for the retailers to place orders if you study their ordering trends.
You need to monitor how many units in total that are shipped and how
many units are sent out late. Inventory control is based on individual
product instead of the type or line it belongs to. Therefore, you need an
easy way to organize our view of the product list.

THE
TRANSFORMER
DEVELOPMENT
PROCESS
Discussion Questions
1.
2.
3.
4.
5.
Why are date and product the first two dimensions?

Why is Date in the model when the problem is shipments?
Is there enough detail in the time dimension?
Why is it important to include fiscal year in our model plan?
In the Product dimension, Inventory Control does not use the Product type or
Product line. How does this help address end-user requirements?
6. Do Finance and Inventory use the same terminology?
7. What do we stock? How do we tell if a product is manufactured in-house?
8. How can you find all customers of a particular type?
9. Do you need to drill down to the individual order or line item level?
10. What is the significance of the order of measures and the choice for default?
11. What additional dimensions could there be?
12. What is the cost of late shipment?

3-17
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
MODEL PLAN FOR: Quality Analysis

Questions:
When
Dim 1
Dimension
Name
Time
Levels
1
2
3
4
What
Dim 2
Where
Dim 3
Who
Dim 4
How
Dim 5
Products Locations Retailer % Late

Types Shipment
Ranges
Years
Product
Regions Retailer
% Late
line
Type
Shipment
Ranges
Quarters Product
Country Retailer
type
Name
Months
Product
City
name
Staff
5
6
7
8
10
Measures
3-18
Order Price, Average Shipment Revenue, Shipment

Revenue, Late Shipment Revenue, % Late Shipments,
Total Units Shipped, Total Units Shipped Late

Cognos 8 BI
Instructor Notes
User ID: admin
COGNOS
4-2
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

DATA
SOURCES
IN
TRANSFORMER
Objectives
discuss the types of data used by Transformer
create data source files
define properties
add Cognos 8 data sources to the model
Instructor Notes
Suggested modules to reference:
Transformer_Fundamentals
The_Transformer_Development Process

4-3
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Identify Your Data

When completing the model plan:
determine whether data defined in the model is

available
analyze the gap between the available and

required data and the implications of having to
obtain the required data
After the model plan has been designed according to the business and user
requirements, the next step is to ensure that the data needed to develop the application
is available.
You must determine where the data is, how to access it, and what security or network
restrictions apply.
Instructor Notes
If the same piece of data is derived from multiple data sources, you must ensure that the data reflects
the same information.
Think about the following items when identifying the required data:
Data source: What is the quality of the data, and how frequently is it updated?
Business owner: Who is responsible for the data (the person that can help define what is in the data).
IS owner: Who is responsible for the system the data is stored on?
Platform: What is the operational environment where the data source is coming from?
System: Can you describe the purpose of the system and the data it produces?
Location: Where is the physical location of the system producing the data?
4-4

DATA
SOURCES
IN
TRANSFORMER
Data Types
Transformer uses three types of data:
date, text, and numeric

Dimensions
Order Date Country City

06/21/2007 U.S.A. Dallas
10/15/2007 France Paris
08/08/2007 Japan Tokyo
Date
Text
Measures
Staff Name
Bill Gibbons
Jean Proulx
Akiko Odi
Quantity Revenue
85
1700
24
480
45
900
Numeric
Date: used to support the time periods.

Text: Descriptive data used to define dimension structures and categories, also referred
to as structural data.
Numeric: Numeric data used to define measure values, also referred to as transactional
data.
Most data included in a data source file is either numeric (quantitative) or text
(qualitative), or a combination of both.
Instructor Notes
Data sources can be either strictly structural and contain only the text data required by a dimension
structure or primarily transactional and contain the data representing the various measure values used
in the application. A data source may contain only structural data. However, a data source cannot
contain only numeric data. Numeric data must be supported by minimal context for values to be rolled
up properly. Text can contain any alphanumeric character.

4-5
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
What is a Data Source File?

A relational database, dimensional cube, file, or other
physical data store that can be accessed though
Cognos 8.
may contain either the actual subset of the data or
only the metadata that Transformer needs to access
the appropriate data when building the model.
By querying the data in the specified sources, you create the multidimensional
PowerCubes required by users of the Cognos 8 components, such as Analysis Studio.
Data source files contain the data that the model needs to build the cube. They can be
Cognos packages or reports, .iqd files, flat files, Microsoft Access tables and queries,
Microsoft Excel crosstabs and databases, and so on
.
Instructor Notes
Q. The Insert Data Source dialog box does not list Oracle Table, SQL Server Table, etc. Can
Transformer not use these as data sources? Must the cube administrator or DBA batch the data out
to one of the formats available in the drop-down?
A. Transformer is a data modeling/ transformation application. Query/extraction is performed outside of
this environment for various reasons.
Transformer supports .iqds and flat files created in other applications (such as .csv files in Excel). One
advantage of flat files is that they may be quicker to build. You are not locked into one "time-window"
for both the extract and the cube build stage. For example, you won't have to directly access a
mainframe system to build your cubes.
4-6

DATA
SOURCES
IN
TRANSFORMER
Demo 1: Create a .csv File in Report Studio to Use as a Data

Source
Purpose:
You want to use a .csv file as a data source in Transformer to build
the PowerCube. In Report Studio, you will create a list report, and
schedule it to be saved on your file system every week. You will
open the flat file to ensure that all the items you require are
included.
Components:
Report Studio
Package:
GO Data Warehouse (query)
User ID:
admin
Password:
Education1!
Task 1. Create a Report Studio report to use as a Data

Source.
1.
2.
3.
4.
Open Cognos Connection.

URL: http://localhost/Cognos8
Username: admin
Launch Report Studio.
Package: Go Data Warehouse (query)
Create a new list report.
Expand Sales and Marketing (query) > Sales (query).

4-7
COGNOS
5.
6.
7.
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Insert the following items into the list:

Time dimension > Day key
Product > Product line, Product type
Sales fact > Revenue, Unit cost, Quantity, Gross margin
Save the report.
Name: Product_Sales
Location: Public folders > GO Data Warehouse (query)
Close Report Studio.
Task 2. Schedule the report to run and create a .csv file.

1.
2.
3.
4.
5.
6.
7.
4-8
Navigate to Public Folders > Go Data Warehouse (query).

Beside Product_Sales, click Schedule.
You can schedule how frequently you want the report to run. Each time the
schedule runs, you want to create a .csv output to your file system. You want
the csv to be updated every week at the same time.
On the By Week tab, ensure the current day is selected.
Set Start to 2 minutes later than the current time.
Under Options, select Override the default values.
Under Formats, clear the HTML check box and then select the Delimited
text (CSV) check box.
Under Delivery, clear the Save check box, and then select the Save to file
system check box.
To save to the local file system the administrator needs to modify settings in
Cognos Configuration and Cognos Administration to specify where the files
can be saved on the external file system.

DATA
SOURCES
IN
TRANSFORMER
8.
After at least two minutes have passed, navigate to C:\Edcognos\C88382.

The schedule ran successfully. The csv files folder appears and contains the .csv
file that was generated.
9. Double-click the csv files folder.
10. Open the .csv file in Microsoft Excel.
You will notice that all the required columns were created, and that the first row
contains the column title, as shown below:
11. From the File menu, click Save As, and in the Save as type list select CSV
(Comma delimited) (*.csv).
12. Close Microsoft Excel, and close Windows Explorer.
Results:
In Report Studio, you created a list report, and scheduled it to save
on your file system every week. You opened the flat file to ensure
that all the items you required are included.
Instructor Notes
Step 11: You are saving at this point due to a product issue. If you didnt save it as .csv, the file would
not appear correctly as a data source in the next demo, even if you change it to Unicode. Saving the
file in the correct format is a workaround.

4-9
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Data Source Design Guidelines

Columns:
The lowest level of every dimension requires a

column.
Higher levels usually require a column.
Every regular measure requires a column.
Column names: Column names in the same data

source must be unique.
Time: If there is a time dimension, include a date
column.
Where possible, design your data so that one source provides the structural information
for each dimension.
Instructor Notes
Transformer automatically maintains levels that are associated with your source data columns and
detects the required changes when you generate categories against an updated data source. If your
source data does not have columns for higher levels, you can create them manually using Transformer.
However, you must remember to update these levels manually if your source data changes.
It is not necessary to have a time dimension For example, your model might provide point-in-time
analysis. A time dimension is irrelevant if you are looking at data from one year without further time
breakdowns or if all your data is for the same day.
4-10

DATA
SOURCES
IN
TRANSFORMER
Define Data Source Properties

Define settings related to each data source, such as:
data source name
data source information
general parameters
descriptive information
Some properties are associated with a specific source type, such as the named range for
an Excel spreadsheet.
The source type you select determines what additional settings you must specify.
Instructor Notes
If you move your data source, edit the Properties to define the new location in the Source tab or the
PowerCube will not build.

4-11
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Define Column Properties

Define settings related to each column, such as:
general parameters
date settings
array information
descriptive information
For most of the supported source data types, Transformer can automatically identify
columns in the data sources and assign default column names and properties.
Column properties are relevant during the AutoDesign process because Transformer
uses them to determine where to map the columns when performing the statistical
analysis. Properties are also useful for the process of maintaining the connection
between the data source file and the model.
Instructor Notes
General Tab - Presents the general properties of a data source column, such as name, origin, data
class, and position in the data source.
Time Tab - Format of input date values and the interval at which measure values were recorded
(degree of detail).
Array Tab - Identifies sets of monthly or quarterly summary measure values that are stored as adjacent
columns in the data source.
Description Tab - Lets the user input a text description of the data source column.
4-12

DATA
SOURCES
IN
TRANSFORMER
Preview Source Data and SQL

Preview the data from a data source without
generating categories.
The preview will update as modifications to columns are made in Transformer.

You can control how many rows display in the preview sample, format the width of the
columns, and add the data source viewer to the default view.
Instructor Notes
For .iqd source files only, expert users can modify the SQL in the Data Source Viewer to optimize,
customize, or refine queries.
After modifying SQL, the relationship between columns in your .iqd file and your model may be lost if:
there is an expression in your SQL
there is an input scale in your .iqd file
the column names of the items below the END SQL line do not match with those column names in
the SQL

4-13
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Confirm Data Source Origin

Confirm the origin of data source columns
associated with the dimension map and see how
each is used.
Using the Show Reference command you can view information about the
columns.
You can determine the impact a column change has on the model (for example,
if you rename a column or you want to determine whether a column can be
safely deleted without affecting any interdependencies).
Instructor Notes
If someone else designed the model, you may want to see the original name of a column, what column
in the data source the information came from, or what columns are sorted.
The slide example illustrates that Year, Quarter, and Month are referenced from the Order Date
column. Notice that Year, Quarter, and Month have been sorted in this model.
4-14

DATA
SOURCES
IN
TRANSFORMER
Demo 2: Examine Property Sheets

Purpose:
You want to examine the properties of columns in a .csv file data
source to gain a better understanding of what data is brought into
Transformer.
Components:
Transformer
User ID:
admin
Password:
Education1!
Task 1. Create a new Transformer model.

1.
2.
Open Transformer.
Create a new Model.
Model name: Product Sales
Data source name: Product Sales
Data source type: Delimited-field text with column titles
Data source location: C:\Edcognos\C88382\csv files
Source file: Product_Sales-en-us.csv
Hint: Do not use AutoDesign
Instructor Notes
The isolation level essentially describes how you want to lock the database tables.

4-15
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Task 2. Examine the properties of date, text, and numeric

columns.
1.
2.
3.
4.
5.
View the properties of the data source.

Hint: Right-click menu
The property sheet for the Product Sales data source appears.
Click Cancel to close the property sheet without making any changes.
Expand the data source.
The result appears as shown below:
View the properties of the Day key column.

Hint: Right-click menu, General tab
The data class for all columns is unspecified when you use a .csv file as a data
source. A .csv file, or comma separated value file, is a flat file format that can be
opened in many applications including Excel and Notepad. The data is retained
in the file, but not the data class.
Close the model without saving and leave Transformer open for the next demo.
Results:
You examined the properties of columns in a .csv data source.
4-16

DATA
SOURCES
IN
TRANSFORMER
Examine Cognos 8 Data Sources

You can create data source queries using Cognos 8
reports that were created in Query Studio or Report
Studio using relational or DMR packages.
Data source queries using Cognos 8 reports perform
most efficiently when the report is a list.
When the Cognos 8 data source is a relational or dimensionally modeled relational

package, you can import query items to create your structural or transactional queries.
You can have multiple data source queries associated with each package or report you
create as a data source.
When using a Cognos 8 report or a Cognos 8 package as a data source, you may be
asked to provide values for existing prompts. Transformer asks you for these values
only the first time you add a query from a report data source. Any values you provide
are cached.
Instructor Notes
You cannot create data source queries using Cognos 8 OLAP reports. You cannot import dimensional
packages using the Insert Data Source feature.
Graphs, dashboards, crosstabs, and complex reports do not provide appropriate data to cube builds
and therefore cannot be used for data source queries.

4-17
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Add Additional Queries to Existing

Cognos 8 Data Sources
You can add a second query to your Cognos 8
package or report data source.
Query 1
Query 2
When you create the new query, it is imported as an additional query under the package
or report data source.
Each Cognos 8 package and report data source is shown in the Data Sources list as a
single data source with multiple associated queries.
Instructor Notes
Add Query from Package or Report option: Add Query from Package or Report opens the Query
Definition dialog box, where you can create the new query.
4-18

DATA
SOURCES
IN
TRANSFORMER
Demo 3: Add a Data Source with Multiple Queries.

Purpose:
You want to add a data source with multiple queries using a
Cognos 8 Package.
Components:
Transformer
Package:
User ID:
admin
Password:
Education1!
Task 1. Create a new Model.
1.
2.
You can import query items from relational or dimensionally modeled relational
packages and reports, and the associated filters and prompts.
Start the New Model wizard.
Hint: File menu
Model Name: Sales
Data Source name: Leave blank. It will default to GO Data Warehouse
(query)
Data Source type: Cognos Package
Log on: User ID: admin, Password: Education 1!
Package Location: Public Folders > GO Data Warehouse (query)
Query Name: Orders
Expand Sales and Marketing (query), and Sales (query).

4-19
COGNOS
3.
4.
5.
6.
7.
4-20
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Select the following and add to the Query definition details:

Time dimension > Date
Order method > Order method
Product > Product name
Sales Fact > Quantity, Gross profit, Revenue, Planned revenue, Gross
margin
The Preview tab shows rows that will be retrieved from this query. You can also
view the SQL, Native SQL, and MDX if available.
Click OK.
You want to manually design the cube, so clear the Run AutoDesign check
box, and then click Finish.
Expand the GO Data Warehouse (query) data source.
You can see the Orders query that you just created.
Each package or report appears as a single container data source, and each one
can have multiple queries belonging to it.
Expand Orders.
Each query has its own definition, where you can add or modify columns and
preview data and SQL. Queries for Cognos packages and reports must be
defined one at a time by using the Add Query From Package or Report option
on a package or report data source.
You want to add another query to the data source.

DATA
SOURCES
IN
TRANSFORMER
Task 2. Add another query to the data source.

When adding queries, Transformer displays the source query using the query
results definition name (for example, Query 1.0). Transformer does not display
the query name as defined by the Query Name property in Query Studio or
Report Studio.
1. Right-click GO Data Warehouse (query) and select Add Query From
Package or Report.
2. For the Query Name, type Products.
3. Expand Sales and Marketing (query), Sales (query), and then Product.
4. Add Product line, Product type, and Product name, and Product key to the
Query definition details pane.
5. Click OK.
Products is added as a new query.

4-21
COGNOS
6.
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Expand the Products query.

You can examine the query items that you have selected.
7. Close the model without saving and leave Transformer open for the next demo.
Results:
You added a data source with multiple queries using a Cognos 8
Package.
4-22

DATA
SOURCES
IN
TRANSFORMER
Demo 4: Import Query Items from a Cognos 8 Report

Purpose:
You want to create a Cognos 8 report to use as a structural data
source in Transformer. You will use a report as a data source in the
Transformer model.
Components:
Report Studio, Transformer
Package:
User ID:
admin
Password:
Education1!
Task 1. Create a Report Studio report to use as a Data

Source.
1.
2.
3.
4.

Username: admin
Create a new List report.
Data source queries using Cognos 8 reports perform most efficiently when the
report is a list.
Expand Sales and Marketing (query) > Sales (query) > Employee by
region.

4-23
COGNOS
5.
6.
7.
8.
9.
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

Region
Country
City
Employee name
Date hired
Employee level
Position name
Group Region, Country, and City.
Title the report Global Employees.
Center the list report in the page body.
Run the report.
10. Save the report.

Name: Global Employees
4-24

DATA
SOURCES
IN
TRANSFORMER
Task 2. Add a Cognos report to the Transformer Model.

1.
2.
3.
In Transformer, create a new model.

Model name: Employees
Data Source name: Global Employees
Data Source type: Cognos Report
Report Location: Public Folders > GO Data Warehouse (query)
Report Name: Global Employees
Add all of the items in Query1.0 to Query definition details, and then click
OK.
If the report contains multiple queries, as in the case of some Report Studio
authored reports, each query will be shown with its relevant query items.
Click Finish.

4-25
COGNOS
4.
5.
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Expand the Global Employees data source, and the query below it.
The results appear as shown below:
The Cognos Report is added as a data source in the model.

Close the model without saving and leave Transformer open for the workshop.
Results:
You created a Cognos 8 report to use as a structural data source in
Transformer.
4-26

DATA
SOURCES
IN
TRANSFORMER
Take Advantage of the Data Filtering in

Cognos 8 Reports
filter by value on specific columns
return a specific number of rows
return only unique records if the data source contains
many duplicate records
When you use a list report as a data source, create the report to include prompts to test
a subset of the data that would be included in the full cube build.
Prompts from reports can be handled either interactively or silently as part of a batch
script.
Instructor Notes
filter by value on specific columns: for example, you can include data for only a few of your regions
when generating categories for the Regions dimension in the model.
return a specific number of rows: For example, if the server data source contains two million records,
you can use only the first 10,000 records for your model prototype.
Adhoc Demo: Create a report in Report Studio, add a mandatory prompt on Region. Create a new
model in Transformer and add it as a data source to show specifying and editing prompt values.
4-27
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Edit Existing Prompts in Cognos 8

Reports and Packages
You can use a Cognos 8 report that contains prompts
that add interactivity for users.
Prompts are mandatory or optional. Mandatory
prompts require values before Transformer can
execute queries.
Prompts act as questions that help users customize the information to suit their own
needs. For example, a prompt may let users select a product type. Only products
belonging to the selected product type are retrieved.
Instructor Notes
When creating a model based on a report data source, Transformer requires that you define values for
mandatory prompts or delete the prompts. When using Cognos 8 packages as data sources, you are
required to define values for mandatory prompts or delete the prompts only before executing queries.
For optional prompts in Cognos 8 report or package data sources, Transformer does not require that
you provide values.
To edit the prompt values, right-click a query in the model and click Edit Prompts.
4-28

DATA
SOURCES
IN
TRANSFORMER
Summary
discuss the types of data used by Transformer
create data source files
define properties
add Cognos 8 data sources to the model

4-29
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Workshop 1: Create a Cognos 8 Report and add it as a Data

Source
The Finance department requires a new PowerCube to review sales. The data you
require is available in several different query subjects. You will create a Report Studio
report with only the items you require. Next, in Transformer, you want to create a new
model without building the dimensions, and then review the column properties.
To accomplish this:
Create a list report titled Sales.
Create a new model using the report as a data source.
Explore data source properties, column properties, and column data types.
For more detailed information outlined as tasks, see the Task Table on the next page.
For the final query results, see the Workshop Results section that follows the Task
Table.
4-30

DATA
SOURCES
IN
TRANSFORMER
Workshop 1: Task Table

Task
1. Create a Report
Studio list report to
use as a Data
Source.
Where to Work
Hints
Report Studio
Report items: Date, Region,

Country, Retailer type, Retailer
GO Data Warehouse
name, Product line, Product type,
(query) package
Product name, Revenue, Unit cost,
and Quantity.
Sales and Marketing
(query) folder, Sales
Save the report as Sales.
(query) namespace
Insertable Objects
pane
2. Add a Cognos
Transformer
report to the
Transformer Model. New Model wizard
Model name: Sales

Data Source name: Sales
Report Location: Public Folders >
Report Name: Sales
Query definition details: Query 1.0
If you need more information to complete a task, see the Step-by-Step Instructions at
the end of the workshop.

4-31
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Workshop 1: Workshop Results

At the end of Task 2, the results appear as follows:
4-32

DATA
SOURCES
IN
TRANSFORMER
Workshop 1: Step-by-Step Instructions

Components:
Report Studio, Transformer
Package:
User ID:
admin
Password:
Education1!
Task 1. Create a Report Studio list report to use as a Data

Source.
1.
2.
3.
4.
5.

Username: admin
Create a new list report.
Expand Sales and Marketing (query) > Sales (query).
Employee by region > Region, Country
Retailer site > Retailer type, Retailer name
Product >Product line, Product type, Product name
Sales fact > Revenue, Unit cost, Quantity

4-33
COGNOS
6.
7.
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Save the report.

Name: Sales
Close Report Studio.
Task 2. Add a Cognos report to the Transformer Model.

1.
2.
3.
4.
5.
6.
4-34
In Transformer, create a new model.

Model name: Sales
Data Source name: Sales
Report Location: Public Folders > GO Data Warehouse (query)
Report Name: Sales
Add all of the items in Query1.0 to Query definition details, and then click
OK.
Click Finish.
Expand the Sales data source, and the query below it.
The Cognos Report is added as a data source in the model.
Explore data source properties and column properties.
Close the model without saving, close Transformer, and then close Internet
Explorer.

Building a Model
Cognos 8 BI
Instructor Notes
User ID: admin
COGNOS
5-2
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

BUILDING
MODEL
Objectives
create model structures
generate categories to populate the model
modify the model using the dimension diagram
verify the model
create a PowerCube
publish a PowerCube as a data source and
package
Instructor Notes
Transformer_Fundamentals
The_Transformer_Development_Process
Data_Sources_in_Transformer

5-3
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Create Model Structures

Create Model structures:
manually: move columns to the Dimension Map

and Measures list.
automatically: use AutoDesign to create a

preliminary model based on the available source
data.
Besides manually creating a dimension with levels, you can also run AutoDesign to
complete the model.
AutoDesign examines the properties of the data source columns and looks for
relationships. It then assigns the various columns in the source file(s) as dimensions,
levels, or measures.
Instructor Notes
AutoDesign functions best in a single data source model. It is data-driven. The quality of the structures
created is affected by the quality of the data. Typically, AutoDesign is used to create a preliminary
design of the model. It may require customization to meet the expectations outlined in the model plan.
You can import dimensions as model structures from packages based on OLAP data sources. This can
be useful in creating conformed or shared dimensions and, to some extent, to reusing portions of the
published metadata from the source dimension.
5-4

BUILDING
MODEL
Dimension Property Sheet

Defines the properties associated with a dimension.
You can:
change the name of the dimension
define it as a time dimension
provide a description
prevent the automatic addition of new categories

to the dimension when categories are regenerated
By default, a dimension will take the name of the first level in the dimension.
Instructor Notes
Dimension type: Defines a dimension as a regular dimension or a time dimension.
Prohibit automatic creation of categories: Locks a dimension to prevent new categories from being
added automatically when categories are generated. Transformer ignores records with source values
that are unrelated to the existing categories in the dimension.
Description: Adds a personalized business description of the dimension.
5-5
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Level Property Sheet

Defines the properties associated with a level.
You can:
specify a source column to populate the level

if different from the default
set a sort order to sort items in a column based on

information in another column
specify associations
Instructor Notes
Associations: Specifies the relationships between an item in the model, in this case a level, and its
associated columns in the source data.
Source: Defines the column that supplies the categories for the level. You can specify a different
column other than the default.
Label: Used when the labels in the source columns have cryptic names, but the labels for the same
items in a related column have more meaningful names.
Category code: Specifies the name of the column in the structure data source that Transformer uses as
a source value.
Order By Tab: Defines the sort and order sequence of the level categories.
Through model properties and preferences, you can specify that all categories use a particular sort
order, rather than setting the order-by preference for each category.
5-6

BUILDING
MODEL
Demo 1: Build a Model

Purpose:
You want to manually create and modify the All Products dimension
in a Transformer model, and then manually complete the model.
Components:
Transformer
Package:
User ID:
admin
Password:
Education1!
Task 1. Create a new model.

1.
2.
3.
Open Transformer.
Create a new model:
Model name: Sales
Data source name: Leave the default
Data Source Type: Cognos Package
Username: admin
Package: Public Folders > GO Data warehouse (query)

5-7
COGNOS
4.
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Add the following items to the Query definition details.

Time dimension >Date
Employee by region > Region, Country, City, Employee name,
Employee key
Retailer > Retailer type, Retailer name, Retailer code
Employee by region > Employee name, Employee key
Product > Product line, Product type, Product name
Sales fact > Gross margin, Revenue, Unit cost, Quantity
Note: Do not use AutoDesign
Task 2. Manually build the Products dimension.
1.
2.
3.
4.
5.
5-8
You can create dimension structures manually by dragging columns that contain
text or date data to the Dimension Map. Use the hierarchies established in the
model plan to create dimension structures.
Expand the Go Data Warehouse (query) data source and then expand the
query.
Drag Product line to the Dimension Map title bar.
Product line is added as a dimension label with Product line as the first level.
You want to add the other levels to the Product line dimension.
Drag Product type below the Product line level.
The level takes the name of the data source column by default.
Drag Product name below the Product type level.
Examine the properties of this dimension.
Hint: Dimension map, right-click menu

BUILDING
6.
MODEL
Rename the Product line dimension.

Name: All Products
Providing a unique dimension name makes it easier for users to distinguish
between the dimension and the level if they do not use the same name.
Task 3. Complete the model.

1.
2.
3.
4.
5.
6.
7.
Drag Date to the Dimension Map title bar.

Date is added as a dimension label with Year, Quarter, and Months as levels.
Drag Region to the Dimension Map title bar.
Drag Country, City, and Employee name below the Region level.
Drag Retailer type to the Dimension Map title bar.
Drag Retailer name and Retailer code below the Retailer type level.
Make the Date dimension the first dimension.
Drag Quantity, Revenue, and Unit cost to the Measures list.

5-9
COGNOS
8.
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Rename the Retailer type dimension to Retailers.

The dimension map appears as shown below:
Leave the model open for the next demo.

Results:
You manually built a new model by adding dimensions, levels, and
measures.
5-10

BUILDING
MODEL
Import Dimensions from Packages

You can import dimensions from packages based on
OLAP data sources.
Dimension Map
This feature provides for dimensions to be created efficiently to resemble the original
dimensional structure from your OLAP or DMR package as closely as possible.
When the data source is a Cognos 8 OLAP package, you must import the dimensions
from the package directly from the dimension map. You subsequently import the
measures from any other data source Transformer supports.
Instructor Notes
Right-click in the Dimension Map area and select Insert Dimension from Package. The dimension will
appear inside the dimension map and a new data source will be created.
If you want to use the measures from an OLAP source, we recommend that you create a relational
query against the source data used to build the original OLAP source. This approach will provide the
best possible performance.
5-11
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Generate Categories and Show

Category Counts
When you generate categories the model is populated
with categories for each level in a dimension.
Categories in
the dimension
Root categories, drill
categories, special
categories, relative
time categories, and
categories within
subdimensions
Categories within
the level
Category count values
When you generate the categories, Transformer reads the data source and populates the
Dimension Map with the categories that define each dimension. It also establishes the
hierarchy of categories within a dimension by determining the parent-child relationships
for each category.
Show Category Counts: counts the values in a category and assesses ratios.
Instructor Notes
Categories are visible only in the dimension diagram. You can create PowerCubes once you create
one dimension and one measure (the minimum required). This automatically generates the categories
prior to building the PowerCube.
Mention that categories and members are referring to the same object.
Show Category Counts is useful in determining your drill-ratio count.
5-12

BUILDING
MODEL
Dimension Diagram
a tool for customizing a dimension
the only place category information is available
Root
Category
Drill
Category
Level
Category
You can:
add, remove, rename, move, or hide and show categories and levels
filter, suppress, connect, and order categories
define a set of levels or categories and apply operations or calculations to them
add and remove subdimensions and drill-down paths
Instructor Notes
You can re-attach categories to create a structure other than that which the data suggests. The root
category Products is the dimension label. This name displays as the highest level category.
The drill category By Products acts as a placeholder to define the starting point of a drill path. It must
be the immediate descent of a root category and is used to describe the properties of the drill-down
structure, which, by default, is not seen by the user.
5-13
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Category Property Sheet

Defines the properties associated with a category
You can:
specify a category label that is different from the

default label retrieved from the source value
change the Inclusion setting to exclude a category

from the PowerCube
Modifying the category label changes the name of the category as it appears in the
model and to end users.
Instructor Notes
Category code: uniquely identifies the category within the dimension.
Source value: Displays the original value of the category in the source data.
Inclusion: By including categories in cubes only when they occur in the model's data source, you can
prevent the cubes from containing many zero values for categories that lacked data. The cubes are
more compact and help users to focus on the relevant data. For example, you may have 200 products but
only sales figures for 180. You can exclude the extra 20 products to save space.
Partition Number: Specify a partition number you want to assign to this category. The same number
must be assigned to every category in the same partition
5-14

BUILDING
MODEL
Verify the Model

Use the Check Model command after each
modification to a model to check for potential
problems.
Check Model issues warnings and error messages:
Warnings do not prohibit PowerCube generation.
Error messages prohibit PowerCube generation.
Check for potential problems after each major modification to a model and before
cube generation. Transformer checks model items (such as categories) to detect
problems in the drill-down path.
Check Model does not check the entire data set of the data source.
Instructor Notes
Transformer creates a Log file for each model. Log files consist of:
Processing Date/Time: indicates when the message was written to the log file.
Message Severity: Falls under one of four categories: Severe Error, Error, Warning, and Information.
Object ID: Identifies the ID of the processed object.
Message Text: processing and timing information.
Checking the model will show an error when you do a weighted average calculation with measures from
two separate sources. Transformer analyzes one source at a time; therefore, it would indicate that this
calculation is not possible.
5-15
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Demo 2: Work with Items in the Dimension Map and

Dimension Diagram
Purpose:
You want to determine the number of categories in each dimension
and then view its structure in the Dimension Diagram. Reorder the
Countries alphabetically, and then view the results in Analysis
Studio.
Components:
Transformer
Package:
User ID:
admin
Password:
Education1!
Task 1. Show the counts and generate the categories.

1.
Click the Dimension Map title bar, and then click Show Category
Counts
The zero (0) beside each level indicates that there are no categories in the
current model because you have not yet generated categories. The bracketed
numbers in the dimension labels indicate the total number of categories, and the
bracketed numbers under the dimension labels indicate the default number of
categories. By default, two categories are generated for each regular dimension
(primary path and drill-down path) and ten categories are generated for the time
dimension.
5-16

BUILDING
2.
MODEL
Click Generate Categories

, and then click OK to the warning.
3.
Transformer reads the source file data, and the dimension structure is then
populated with categories. The number of categories within each level is now
shown in brackets next to each dimension label.
On the Dimension Map, click the All Products dimension label.
4.
Click Show Diagram
You can maximize the dimension diagram to view all dimensions. The Date
dimension is automatically created with additional special categories because it is
a time dimension.
Task 2. Reorder the categories in the Region dimension.
1.
2.
In the dimension pane, click Region.

In the dimension diagram, expand the Central Europe category.

5-17
COGNOS
3.
4.
5.
6.
7.
8.
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Move France below Belgium.

Hint: Point to the left side of the France category. Do not drag France so far
down that the link jumps to Asia Pacific.
Ensure that the pointer is an arrow . The arrow moves or repositions an
item. If you point to the right, a crosshair appears which can be used to create a
new level or category or define new relationships between categories.
You can continue to manually sort all countries. However, you can also
automatically sort the countries for accuracy and ease of maintenance.
Double-click the Country level.
Click the Order By tab, and then click Add.
Click More, select Country, and then click OK.
This will sort the categories by country.
Ensure that the Sort order is Ascending and Sort as is Alphabetic, and then
click OK.
You reordered all categories within the Country level. Order By affects all
categories within a level and is automatically maintained by Transformer.
Results:
For each dimension, you determined the number of categories,
viewed its structure in the Dimension Diagram, reordered the
Countries alphabetically, and then viewed the results in Analysis
Studio.
5-18

BUILDING
MODEL
Create a PowerCube
The model must have at least one dimension with at
least one level, and its Measures list must show at
least one measure.
You can generate a default PowerCube, or manually
define it to meet the specific needs of users.
Each cube uses Structured Query Language (SQL) to retrieve the specified query items
and their relationships from the data sources in your model. When you create or
modify a cube, you can also apply security to it to control your users' access to
information.
You can define each cube to meet a set of broadly defined, but related, OLAP
reporting needs.
Instructor Notes
Examples of items that you can customize include the location of the PowerCube or the dimensions
and measures to include.

5-19
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Publish as a Data Source and Package in

Cognos Connection
When the Cognos 8 environment is properly
configured, you can publish any object in the
PowerCubes list from Transformer directly to Cognos
Connection.
You can publish a single cube using
the Publish PowerCube as Data Source and

Package wizard
settings stored in the model
an .xml publish specification that you run from the

command line or the Run menu
If user authentication is enabled, you will be prompted to log on.

You can publish one cube, or all the cubes in the model. You can also publish Cognos 8
Transformer cubes from:
Cognos Connection: deploy single cubes
Framework Manager: publish multiple PowerCubes in a single package or mix
your PowerCube data source with other data sources
Once the PowerCube is published as a data source and package, it can be consumed in
the Cognos 8 Studios.
Instructor Notes
You must specify the location from where the Cognos 8 server accesses each cube and, if user
authentication is enabled, the external Cognos-supported namespace to use. Before you proceed, it is
recommended that you test to ensure that the relevant connection strings are valid.
You can organize by publishing your cubes to hierarchical folders, and under existing packages, in
Cognos Connection.
5-20

BUILDING
MODEL
Demo 3: Create the PowerCube and View in Analysis Studio

Purpose:
You want to create the PowerCube and then view the results in
Analysis Studio.
Components:
Transformer, Analysis Studio
Package:
User ID:
admin
Password:
Education1!
Task 1. Create a PowerCube.

1.
Click Check Model
A window may appear to indicate that Transformer is verifying security. If

prompted to log in, use admin, Education1!.
There should be no issues in the model.
2.
.
Click Create PowerCubes
A message indicates that a cube based on the currently active model is created.
By default, the PowerCube generation process generates categories, and a
PowerCube called Sales is added to the PowerCubes list.

5-21
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Task 2. Publish the PowerCube directly to Cognos Connection.
1.
2.
5-22
You can publish a single cube using the Publish wizard, the settings stored in
the model, or the command line. You will use the wizard.
Right-click the Sales PowerCube, and then select Publish PowerCube as
Data Source and Package.
Method: Start publish wizard.
Data source name: Sales
Windows location: C:\Edcognos\C88382\Sales.mdc (set by default)
Test the Connection to the data source.
Package name: Sales
Package location: Public folders
View the package in Public Folders.
Username: admin
Notice the Sales package you just created as shown below:

BUILDING
MODEL
Task 3. Create a basic Analysis.

1.
2.
3.
4.
5.
6.
7.
Launch Analysis Studio (using the Sales package).

Create a Blank Analysis.
Analysis opens and displays a blank analysis with data available from the Sales
PowerCube.
In the Insertable Objects pane, notice the All Products dimension. This is the
Products dimension that you renamed in Transformer.
Expand All Products and Outdoor Protection.
Expand Sunscreen to view the members within it.
Product names are displayed at the lowest level of the hierarchy.
Drag Sunscreen to the Columns drop zone.
Expand Measures and drag Quantity to the Measure drop zone.
Expand Region and Central Europe.

5-23
COGNOS
8.
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Right-click Central Europe, point to Insert, and then click As Rows.

The analysis appears as shown below:
Notice the changes you made previously in Transformer. The countries within
Europe display in alphabetical order.
9. Close Analysis Studio without saving.
10. Close the model without saving and leave Transformer open for the workshop.
Results:
You created a PowerCube and viewed the results in Analysis Studio.
5-24

BUILDING
MODEL
Summary
create model structures
generate categories to populate the model
modify the model using the dimension diagram
verify the model
create a PowerCube
publish a PowerCube as a data source and
package
Instructor Notes
If you have reached the end of a teaching day, you can show students how to remove packages and
data source connections in Cognos Connection (except Go Data Warehouse (query), and Go Data
Warehouse (analysis). This will "unclutter" public folders. You can also delete the cubes, log files etc.
from C:\Edcognos\C88382

5-25
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Workshop 1: Create a Model Manually

You want to create a preliminary model in Transformer to generate a PowerCube. All
the data you require is in the GO Data Warehouse (query) package, and the column
properties accurately reflect the data types.
Create a new model manually:
Use the GO Data Warehouse (query) in the Public Folders.
Create a new model called Promotions.
The model must include the following:
Dimension1: Date
Dimension2: Campaign name, Promotion name
Dimension3: Product line, Product type, Product name
Dimension4: Country, Employee name
Measures: Quantity, Gross margin, Revenue, Gross profit
modify the order of the Data Source columns
build the dimension map based on the above dimensions
generate categories and perform a category count
reorganize the countries in alphabetical descending order
publish the PowerCube as a data source and a package.
5-26

BUILDING
MODEL

Task
Where to Work
1. Create a new model. Transformer
New Model wizard
Hints
package - Sales and Marketing
(query) folder, Sales (query)
namespace
Data source items: Date,
Promotion name, Campaign name,
Product line, Product type, Product
name, Country, Employee name,
Quantity, Gross margin, Revenue,
Gross profit.
2. Manually build the

dimensions.
Dimension Map
Date, Campaigns, Product line,

Country
Measures: Quantity, Gross margin,
Revenue, Gross profit
Generate Categories.
3. Determine the
number of
categories in each
dimension and sort
the countries.
Dimension Map
4. Publish the
PowerCube to
Cognos
Connection.
Right-click menu
5. Verify the result in

Analysis Studio.
Cognos Connection
Rows: Date
Analysis Studio
Columns: Promotions
Show Category Counts

Dimension Diagram
Sort by: Country

Sort ascending, alphabetic
Create the PowerCube
Publish wizard
Promotions package
Measure: Quantity
5-27
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

At the end of Task 2, the results appear as follows:
After creating an analysis, the result appears as shown below:
5-28

BUILDING
MODEL

Components:
Transformer
Package:
User ID:
admin
Password:
Education1!

1.
2.
3.
Create a new model:

Model name: Promotions
Username: admin
Package: Public Folders > GO Data Warehouse (query)
Add the following items to the Query definition details pane.
Promotions > Campaign name, Promotion name
Employee by region > Country, Employee name
Sales fact > Quantity, Gross margin, Revenue, Gross profit

5-29
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Task 2. Manually build the dimensions.

1.
2.
3.
4.
5.
Expand the data source and then expand the query.

Modify the order of the Data source columns if necessary.
Create the dimensions:
Date: Year, Quarter, Month
Campaigns: Campaign name, Promotion name
Product line: Product line, Product type, Product name
Country: Country, Employee name
Examine the properties of these dimensions.
Hint: Rename the dimension labels
Add Quantity, Gross margin, Revenue, Gross profit to the Measures list.
Task 3. Determine the number of categories in each

dimension and sort the countries.
1.
2.
3.
4.
5.
6.
7.
8.
5-30
Check the model and generate the categories, and click OK to close the
message.
On the toolbar, click Show Category Counts.
On the toolbar, click Show Diagram.
In the Dimensions pane, select Country.
Right-click the Country Level label, and then click Properties.
Click the Order by tab
Under Sort-by column, click Add.
Click More, select Country, and then click OK twice.

BUILDING
MODEL
9.
Ensure Ascending and Alphabetic is selected, and then click OK.

The countries are sorted alphabetically in ascending order.
10. Close the dimension diagram.
1.
2.
3.
On the toolbar, click Create PowerCubes.

Right-click the Promotions PowerCube, and then click Publish PowerCube
as Data Source and Package.
Method: Start publish wizard.
Data source name: Promotions
Windows location: C:\edcognos\C88382\Promotions.mdc (set by default)
Test the Connection to the data source
Package name: Promotions
Package location: Public folders
Username: admin

1.
2.
3.
4.
5.
6.
Launch Analysis Studio (using the Promotions package).

Expand Date, and then drag Date to the Rows drop zone.
Drag Campaigns to the Columns drop zone.
Expand Measures, and then drag Quantity to the Measures drop zone.
Close Internet Explorer, and then close Transformer without saving the
changes.

5-31
COGNOS
5-32
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

The Time Dimension
Cognos 8 BI
Instructor Notes
User ID: admin
COGNOS
6-2
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

THE
TIME
DIMENSION
Objectives
discuss the purpose of a time dimension
review properties of a time column
define a regular time dimension
examine standard and nonstandard time

dimensions
Instructor Notes
Building a model
6-3
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
What is a Time Dimension?

built by default from a data source column classified
as date data type
lets users create reports based on different time
periods, such as a fiscal quarter or year
Date Dimension
The time dimension answers the "when" question.

If you drag a column from the Data Sources list that has a data class of Date onto the
Dimension Map, Transformer automatically creates a regular time dimension with the
levels Year, Quarter, and Month.
On the Dimension Map, a small clock appears before the name of the dimension,
indicating it is a time dimension.
Instructor Notes
The time dimension hierarchy is automatically based on a calendar year. Time periods used to view
data can also represent:
industry specific time periods, such as 13-week manufacturing periods
nonstandard time periods, such as fiscal years, hours, or minutes
lunar time periods, or a division of time based on thirteen 28-day months
relative time periods, such as year-to-date or previous quarter.
Display formats for the time dimension can be customized from the Time level property sheet.
6-4

THE
TIME
DIMENSION
Types of Time Dimensions

Standard time dimension:
created from a single column
most aspects are predefined by Transformer
customizable
Nonstandard time dimension:
can be created from more than one column
relationships between the categories are

completely defined by you
A standard time dimension is created with categories supplied by a single data source
column. The standard time dimension is assumed to be a set of successive levels that
includes some combination of Year, Quarter, Month, Week, and Day.
Instructor Notes
Categories can be generated in the levels of a standard time dimension without processing a data
source, based on "predefined" time categories. If you want levels lower than Month (weeks and days),
then you have to create the Date dimension using the Date Wizard.

6-5
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Calendars
Gregorian Calendar (default):
the Year Begins property controls the date on which

the year starts
divides data into Year, Quarter, Month
Lunar Calendar:
comprises 52 weeks
the Year Begins and Week Begins On properties must

coincide
divides data into Lunar Year, Lunar Quarters, Lunar

Months, and some common reporting periods (4-4-5,
4-5-4, or 5-4-4 weeks in a month)
The Gregorian calendar is the most common time calendar used for reporting; it
consists of a standard 12-month, 365- or 366-day year.
However, if your business does not organize its time period based on a Gregorian
calendar, Transformer allows you to organize your time using a lunar calendar or a
nonstandard time period.
Instructor Notes
Use a lunar year when your time dimension must reflect a year that consists of 52 weeks with 7 days
each week. This type of time dimension is typically used in the manufacturing sector, where production
lines are working continuously and labor schedules are matched to the production schedules.
For example, an auto parts manufacturer may have machines that run almost 24 hours a day, 7 days a
week, 52 weeks a year. The company may organize employee schedules using a lunar year calendar
that may change from week to week, rather than a Gregorian calendar, where shifts are planned for an
entire month or quarter.
6-6

THE
TIME
DIMENSION
Define Date Formats

Source Data
Transformer
Date column
property sheet
Set degree
of detail
Is the
data source
column
defined as a
date data
class?
No
Yes
Set date
input format
Set data
class to date
To create a time dimension, Transformer requires information about how dates are
formatted in the source data to correctly interpret them.
Some data sources include information about their columns (metadata), while others do
not. If a data source does not predefine this information, you must define the column
in Transformer.
Instructor Notes
Transformer defaults to YMD for .csv and flat files. AutoDesign can determine date formats during its
analysis. You can define the properties for a date column on the column properties sheet.
When defining a Date Input Format, it is important to select the correct degree of detail. The degree of
detail on the Date tab defines the level at which Transformer allows reporting to occur, you cannot
specify a degree of detail that is lower than the lowest level indicated by the input format.
In the time dimension, if Transformer generates a category named Invalid Dates, the date format is
probably not defined (or not defined correctly).
6-7
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Limit the Range of Dates Included in the

Model
focus analysis on a specific time period.
When you create the time dimension, you can limit the range of acceptable dates so
that categories that are irrelevant to your users do not appear in their OLAP reports.
Categories for Early Dates and Late Dates are automatically generated if dates from the
source fall outside the range specified for any time dimension. By changing the date
range, you can incorporate out-of-range dates into your model.
Instructor Notes
If a data source file contains data for two specific years, beginning with Jan 1, 2006, you can set the
absolute range of date values to match that range. If Transformer encounters dates in the data source
that fall outside that range (due to invalid data entry, for example), it notifies you with an Early Dates or
Late Dates category in the time dimension.
The Earliest date is the upper boundary for the range of dates declared in the Time tab of the Time
Dimension property sheet. The Latest date is the lower boundary for the range of dates declared on the
Time tab of the Time Dimension property sheet.
6-8

THE
TIME
DIMENSION
Set up Fiscal Years, Quarters, and Months

The Year begins date sets the month and day in
which every year begins. It can be modified to
correspond to the start dates of your business.
For the Great Outdoors,

the fiscal year begins in
March, and the work
week begins on Monday.
Use the Year begins box to customize the beginning of the business year or reporting
periods used by your organization.
The fiscal start date of a business year can be incorporated into a Transformer model
by using the time dimension Drill Category property sheet. For example, if an
organization's fiscal year starts on March 1 and ends on February 28 of the following
year, you can set up a time dimension that recognizes March 1 as the start of the year.
The first quarter of the year will contain March, April, and May.
Instructor Notes
The ability to set the fiscal start date can be accessed only through the time dimension diagram. You
would use the Date tab on the Drill Category property sheet, which specifies how Transformer should
handle dates in the current drill-down path for a date dimension.
Transformer uses the Year begins value when performing calculations during date category generation.
All years, both forward and back from the specified start date, are constructed based on the given
value.
6-9
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Demo 1: Set up the Fiscal Year

Purpose:
You are required to set up a fiscal year start date of March 1st and
change the display format of the month level.
Components:
Transformer
Package:
User ID:
admin
Password:
Education1!
Task 1. Create a new model using a Cognos 8 Package as the

data source.
1.
2.
6-10
Start the new model wizard.

Model name: Sales (Time)
Data source name: leave the default
Data source type: Cognos Package
Note: User ID - admin, Password - Education1!
Location: Public Folders > GO Data Warehouse (query)
Expand Sales and Marketing (query) and Sales (query).

THE
3.
TIME
DIMENSION
Add the following items to Query definition details:

Time dimension> Date
Employee by region > Region, Country, City
Retailer > Retailer name
Sales fact > Revenue
Note: do not use AutoDesign
Task 2. View the properties of the Date dimension.

1.
2.
3.
4.
Expand GO Data Warehouse (query) data source and the query.

View the properties of the Date column.
Notice that the Data class is set to Date.
Click the Time tab.
The Date input format is Predefined.
Click OK.
Task 3. Build the Dimension Map and change the display

format of the month level.
1.
Drag Date to the Dimension Map title bar.

A time dimension called Date is added to the Dimension Map, with three time
levels automatically created by Transformer. Notice the small clock before the
dimension name, indicating a time dimension.

6-11
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
2.
Complete the dimension map as follows:
3.
4.
Drag Revenue to the Measures list.

Modify the format of the Month level to change the date format to control
how all dates in a specific level appear.
Hint: level properties, Time tab
Modify Format: MMMM, yyyy
Task 4. Reset the fiscal year start date.

1.
2.
3.
4.
5.
6.
7.
6-12
Generate the categories, and then click OK to accept the warning.

On the Dimension Map, click the Date dimension.
Click Show Diagram.
Expand 2005 and 2005 Q 1.
Look at the values in the Month level. Notice that the year begins in January,
and the first quarter consists of January, February, and March.
Right-click the By Date drill category and click Properties.
Click the Time tab.
Set the Year begins date to 20070301.
You changed the year to run from March to February; therefore, the first
quarter month will start in March.

THE
8.
9.
TIME
DIMENSION
Click OK.
A warning message appears stating that these changes will cause existing date
categories to be removed.
Click OK to accept the warning.
Task 5. View the newly defined time categories.

1.
2.

Expand 2005 and all the quarters within this year.
The fiscal year 2005 begins in March 2004. Because you changed the year to run
from March to February, the first quarter consists of March, April, and May.
The dimension diagram appears as shown below:
3.
Close the dimension diagram and leave Transformer open for the next demo.
Results:
You reset the fiscal year start date and modified the display format
of the month level.

6-13
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Create a Time Dimension Using the

Date Wizard
Default Path
Time Dimension
Source Column
Years?
Type of Years?
The Date Wizard is an
integrated set of dialog
boxes that prompt you to
define a date dimension.
Calendar?
Lunar?
Quarter Years?
Months?
Weeks?
Days?
First Day of Year?
Generate Categories?
The Date Wizard simplifies creating a time period by defining:

the source column that contains the date values
the number of levels
the structure of categories at intermediate levels
the start and end points for the time dimension
6-14

THE
TIME
DIMENSION
Demo 2: Create a Time Dimension Using the Date Wizard and

Manually Add a Level to the Time Dimension
Purpose:
You built a model to show the change in revenue for all Regions and
product lines based on a lunar calendar and including detail to the
week and day levels.
Components:
Package:
User ID:
admin
Password:
Education1!
Task 1. Use the Date Wizard to create the time dimension.

1.
Delete the Date dimension from the dimension map. (remove all categories)
2.
to create a new time dimension with the

Click the Date wizard button
following settings:
New dimension name: Date
Source column: Date
Do you want years in this dimension?: Yes
Please choose the kind of years you want: Lunar year of 52 weeks
Do you want quarter-years in this dimension?: Yes
Do you want months in this dimension?: Yes
Please choose the type of month for this dimension: 4-5-4 week pattern
Do you want weeks in this dimension?: Yes

6-15
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Do you want days in this dimension?: No

Please choose the first day of your week: Sunday
Under what conditions should an extra week be added to a year: When
there are 5 extra days at year end
Please enter the first day of one particular year (yyyymmdd): 20070107
Do you want to generate the categories now?: No
Task 2. Manually create a Day time level.
1.
2.
3.
4.
5.
6.
7.
6-16
Insert a new level under Week.

Hint: Right-click Week level
Level name: Day
Add an Association.
Association role: Source
Column name: Date
Click the Time tab, and in the Date function list, click Day.
Click OK.
An error message appears, stating that the time dimension levels are not in their
natural order.
Click OK.
Drag the new Day level below Week.
Drag the Date dimension to the left of the Product line dimension.

THE
TIME
DIMENSION

1.
2.
Check the model, generate the categories, accept the warning, and then create
the PowerCube.
Right-click the Sales (Time) PowerCube, and then select Publish
PowerCube as Data Source and Package.
Method: Publish the PowerCube using current settings.
This option publishes the PowerCube using settings stored in the Model. You
do not have to use the wizard with this option.

1.
2.
3.
4.
5.
6.
7.
8.
9.
Log on to Cognos Connection.

Username: admin
Launch Analysis Studio.
Package: Sales (Time)
Drag Product line to the Columns drop zone.
Drag Region below the Product line column.
Expand Measures and drag Revenue to the Measure drop zone.
Expand the Date folder, and then expand Date.
Expand 2005 and 2005 Q2 to the month level.
Expand 2005/04, 2005/05 and 2005/06 to the week level.
Notice the structure for weeks per month (4-5-4) that you selected in the Date
Wizard is reflected here in the distribution of weeks for our lunar months.

6-17
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
10. Expand 2005/04/10 to the day level.

The lowest level in this dimension is Day.
11. Drag 2005/04/10 to the Rows drop zone.
The report appears as shown below:
You can see a change in revenue for all regions including detail to the week and
day levels.
12. Close Analysis Studio without saving the report.
13. Close the model without saving the changes, and leave Transformer open for
the next demo.
Results:
You built a model to show the change in revenue for all Regions
based on a lunar calendar and including detail to the week and day
levels.
6-18

THE
TIME
DIMENSION
Nonstandard Time Dimensions

monitor measure values over time periods that
Transformer does not generate by default.
can be:
irregular time periods, such as biweekly pay

periods that do not coincide with the months of the
year
a time period that does not follow typical intervals
You may need to create a time dimension that does not contain any of the "standard"
date levels. You do this by creating a nonstandard time dimension.
You must manually create all the structure for a nonstandard time dimension.
Instructor Notes
Another example is the growing seasons of a farm when harvests occur at various times throughout the
year. These time periods probably do not follow typical time intervals and require manually constructed
time dimensions.
After you have created a nonstandard time dimension, you can set up relative time categories for the
periods within the dimension. For example, if you are tracking the number of patients monitored within
nursing shifts, you could find the number of patients monitored in the same hour on a previous shift.
Nonstandard time dimensions make no assumptions about the nature of the levels they contain, other
than the fact that they represent time periods and are therefore ordered in time.
6-19
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Demo 3: Create a Nonstandard Time Dimension

Purpose:
The product manager wants to report on seasonal product sales.
Specifically, the manager wants to know which products sell best in
which season. You will create a nonstandard time dimension to
make this possible.
Components:
Package:
User ID:
admin
Password:
Education1!

1.
2.
Start the new model wizard.

Model name: Seasonal Sales
Data source name: leave the default
Data source type: Cognos Report
Location: Public Folders > GO Data Warehouse (query) > Seasonal_Sales
Under Query 1.0, add all of the query items to Query definition details.
Note: do not use AutoDesign
Instructor Notes
Option: Show students the Seasonal Sales report in Report Studio before adding it as a data source
in Transformer.
6-20

THE
3.
4.
Expand the Seasonal_Sales data source and query.

Create the following dimensions:
5.
Drag Revenue to the Measures list.
TIME
DIMENSION
Task 2. Create a nonstandard time dimension.

1.
2.
3.
4.
5.
Insert a new dimension.

Hint: Click the Dimension Map, Insert Dimension (Ins).
Name: Season
Dimension type: Time
Click the Time tab.
Select Do not create levels, and then click OK twice.
The Season time dimension displays.
From Data Sources, drag Season under the Season time dimension.
Move Season to the left of the Products dimension as shown below:

6-21
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Task 3. Create the PowerCube and publish it to Cognos

Connection.
1.
2.
Check the model, generate the categories, and create the PowerCube.
Publish the PowerCube to Cognos Connection as a Data Source and Package.
Hint: Right-click menu, Publish PowerCube as Data Source and Package.
Method: Publish the PowerCube using current settings.

1.
2.
6-22

Username: admin
Package: Seasonal Sales

THE
3.
4.
5.
TIME
DIMENSION
Create a Default Analysis.

The revenue for each product line displays by season. The product manager can
now determine which products sell best in which season.
Close Analysis Studio without saving, and then close Internet Explorer.
Close the model without saving and leave Transformer open for the workshop.
Results:
The product manager can now determine which products sell best
in which season.

6-23
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Summary
discuss the purpose of a time dimension
review properties of a time column
define a regular time dimension
examine standard and nonstandard time

dimensions
Instructor Notes
from C:\Edcognos\C88382.
6-24

THE
TIME
DIMENSION
Workshop 1: Work with the Time Dimension

You want to create a Model to support joint reporting between the Finance and the
Orders and Inventory departments. The data required is available in the Go Data
Warehouse (query) data source.
Create a new model called Sales using Go Data Warehouse (query). Add:
Date, Product line, Product type, Product name, Region, Country, City,
Revenue
To conform to the company's fiscal reporting period, modify the start of the
fiscal year to March 1st.

6-25
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

Task
Where to Work
New Model wizard
Hints
Model name: Sales
package - Sales and Marketing
(query) folder, Sales (query)
namespace
Data source items: Date, Product
line, Product type, Product name,
Region, Country, City, Revenue

dimensions.
Dimension Map
Date, Product line, Region
Measures
Revenue
3. Modify the start of

the fiscal year.
Dimension Diagram
Generate the categories.

Set the Year begins date to
20080301.
6-26

THE
TIME
DIMENSION

After creating your model, it should appear as shown below:
After modifying the start of the fiscal year to March 1st, the result appears as shown
below:

6-27
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

Components:
Transformer
Package:
User ID:
admin
Password:
Education1!

1.
2.
3.
In Transformer, create a new model:

Model name: Sales
Username: admin
Package: Public Folders > GO Data warehouse (query)
Sales fact > Revenue
6-28

THE
TIME
DIMENSION

1.
2.
3.
4.

Region: Region, Country, City
Examine the properties of these dimensions.
Add Revenue to the Measures list.
Task 3. Modify the start of the fiscal year.

1.
2.
3.
4.
5.
6.
7.
8.
9.
Check the model, and then generate the categories.

If necessary, in the Dimension pane, click Date.
Right-click the By Date drill category, and then click Properties.
Click the Time tab.
Set the Year begins date to 20080301, and then click OK twice.
Expand 2005 and 2005 Q1.
Close the Dimension diagram, and leave the model open for the next
workshop.

6-29
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Workshop 2: Work with the Date Wizard

In the current model, you want to recreate the Time dimension using the Date wizard.
You want the dates to be based on a calendar year and reflect a six-day work week
starting on Monday and ending on Saturday.
Once complete, view the categories in the Time dimension.
6-30

THE
TIME
DIMENSION

Task
1. Use the Date
Wizard to
create the time
dimension.
Where to Work
Hints
Toolbar
6-day work week

(Monday-Saturday).
Date wizard
Based on a Calendar
year.
Split, but do not
create 1-day weeks.
2.
Verify the
result.
Show Diagram
Generate the
categories.
Verify 6-day work
week.

6-31
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

6-32

THE
TIME
DIMENSION
Workshop 2: Step - by-Step Instructions

Components:
Package:
User ID:
Password:
Transformer
admin
Education1!
Task 1. Use the Date Wizard to create the time dimension.

1.
Delete the Date dimension from the dimension map. (remove all categories)
2.
to create a new time dimension with the

Click the Date wizard button
following settings:
Hint: Dates must reflect a six-day work week (Monday to Saturday)
New dimension name: Date
Source column: Date
Do you want years in this dimension?: Yes
Please choose the kind of years you want: Calendar years of 365 (or 366)
days
Do you want quarter-years in this dimension?: Yes
Do you want months in this dimension?: Yes
Do you want weeks in this dimension?: Yes
Do you want days in this dimension?: Yes
Please choose the first day of your week: Monday
How should a week which spans a month boundary be treated?: Split, but
do not create 1-day weeks
Please enter the first day of one particular year (yyyymmdd): 20060101
Please select the days that are in your week: All, except Sunday
Do you want to generate the categories now?: No
Drag the Date dimension to the left of the Product line dimension.
3.

6-33
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Task 2. Verify the result.

1.
2.
3.
4.
6-34

Expand 2005, 2005 Q 2, 2005/May, 2005/05/02.
Sunday is suppressed because you specified a 6-day work week.
Close Transformer without saving the changes.

Relative Time
Cognos 8 BI
Instructor Notes
User ID: admin
COGNOS
7-2
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

RELATIVE
TIME
Objectives
customize relative time categories
Instructor Notes
Building a Model
The Time Dimension

7-3
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Compare Trends Over Time

As dates in your data source change, the data in your
report can automatically change to reflect data for the
current time period.
Transformer automatically creates several standard
relative time categories and organizes them into
groups so that they are easier to understand and
customize.
By including the most commonly required relative time categories in your cubes, you
avoid the need to calculate them when you analyze the data. Relative time categories
can make it easy for your users to answer these time-comparison questions:
Have you ever wondered how sales this month compare to those from last
month or during the same month last year?
Have sales of a particular product in the last two months of this quarter increased
over sales during the last two months of the previous quarter?
Instructor Notes
Example: You can create custom relative time categories to track moving annual totals. Current MAT
(Moving Annual Total) could be to November 2005 (Prior MAT would therefore be to November 2004).
If you opened a report in May 2006, the values would change to reflect May 2006 (Current MAT) and
May 2005 (Prior MAT). Transformer updates relative time categories automatically according to the
current period set for the dimension.
7-4

RELATIVE
TIME
Relative Time Categories

Relative time categories are special categories that
can apply to either Standard time or Nonstandard
time.
In Standard time, relative time categories are generated by default. In Nonstandard

time, relative time categories must be created.
Relative time categories are special time categories that track measure values for a
specific period of time, relative to the current time period.
Transformer updates relative time categories automatically according to the current
period set for the dimension.
Instructor Notes
In the Slide, the Date dimension has Year, Month, and Quarter. 8 default relative time categories are
created: Current Month, Last Month, QTD, Prior QTD, QTD Grouped, YTD, Prior YTD, YTD Grouped.
If the Date dimension had Year, Month, Quarter, and Week,11 relative time categories are created:
Current Week, Last Week, MTD, Prior MTD, MTD Grouped, QTD, Prior QTD, QTD Grouped, YTD,
Prior YTD, YTD Grouped.
7-5
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Types of Relative Time Categories
Today
Q1
Q2
Q3
Q4
Q1
Q2
Q3
Q4
Q1
Q2
Single
Period-to-Date
Running Total
Single Category: Month, Quarter, Shift

Period-to-Date: Week-to-Date, Year-to-Date Grouped, Quarter-to-Date Grouped
N-Period Running Total: 6 Months running total from last year, 1 Quarter running
total from 6 months ago
Instructor Notes
By creating a special category, you can create additional time categories relative to the current period.
The slide shows examples of three types of relative time categories:
The Single period is Same Month, Prior Year. Changes as the current month changes. If the current
month is January 2005, the Same Month, Prior Year will be January 2004.
The Period-to-date is life-to-date: changes as the current period changes. New data is added to the lifeto-date total.
The N-Period Running Total is Prior 8 weeks. changes as the current period changes. However, the
total still reflects only eight weeks before the current week.
Transformer organizes relative time categories into groups (QTD Grouped and YTD Grouped) to make
it easier to understand time comparison questions. When using relative time categories, ensure the
Inclusion property is Always Include for each level in the time dimension so that Transformer can
calculate the correct relative date values.
7-6

RELATIVE
TIME
Grouped Relative Time

A group of relative time periods that consists of:
prior period-to-date
period-to-date
calculation showing change
calculation showing growth
Grouping compares two relative time categories that share the same specification but
differ in terms of context offsets.
The grouped special categories appear only when the time dimension contains one or
more levels higher than the current period. Those categories are required to calculate
the values of Change and Growth.
Instructor Notes
It is possible to add/remove special categories to/from the group either by modifying the group category
specification or by adding/removing them through the diagram.
A group category cannot contain other group categories. A relative time group category contains at
least one relative time category based on the group category specification. If none of these categories
exist in the group, the group category becomes a regular special category. When a new time dimension
is created, a default relative time group category will be created for Period To-Date/Period To-Date,
Prior Period for the highest period in the time dimension.
7-7
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Set the Current Period

Transformer reads all of the model date values and
assigns the latest one as the current period.
The current period is the time period that
Transformer uses as the benchmark to determine
the valid date categories for the relative time
categories generated by default.
The current period can be set automatically or manually. By setting the current period
manually, you can select the time category to define the current period.
To set the current period manually, you must make sure that categories have been
generated. Setting the period manually is required if your data includes future values for
measures, such as forecasts or deliveries.
Instructor Notes
If the current period is defined as December 2007, Transformer makes the following declarations:
For the relative time category Last Month, Transformer assigns November 2007.
For the relative time category Last Year, Transformer assigns 2006.
If you have limited the Range of Dates, and the current period in the data found by Transformer falls
within Early Dates, Transformer will set no current period. No relative time categories will be generated.
To correct this, select a different current period, or select a different range of dates.
7-8

RELATIVE
TIME
Demo 1: Set the Current Time Period Manually and Create

Additional Relative Time Categories
Purpose:
You want to measure past performance by quarter, where the third
month of the quarter is the critical month and is used as the
performance benchmark. The current period is set to the third
month. The Director of Sales requires two additional relative time
categories, one for the same month in the prior quarter and another
for the same month in the prior year.
Components:
Model:
Sales and Marketing.mdl
User ID:
admin
Password:
Education1!
Task 1. Set the current time period.

1.
2.
Open a Transformer Model.

Transformer8\EN
Name: Sales and Marketing.mdl
Generate the categories, and click OK to accept the warning, if necessary.
Note: If prompted, User ID - admin, Password - Education1!

7-9
COGNOS
3.
4.
5.
6.
7.
8.
7-10
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Double-click the Time dimension label.

Click the Time tab.
Under Current period, the Automatically set the current time period check box
is selected. As a result, your current period is July 2007, which is the last date in
the data source. This date is used as the benchmark for creating the default
relative time categories in Transformer.
Clear the Automatically set the current time period, and then click OK.
Click the Time dimension, and then click Show Diagram.
Maximize the window and diagram to fit your screen, and close all expanded
relative time categories.
Click the Time category label, and then from the Diagram menu, click Set
Current Period.

RELATIVE
TIME
Task 2. View the default relative time categories.

1.
View the default relative time categories.

There are eight: Current Month, Last Month, QTD, Prior QTD, QTD
Grouped, YTD, Prior YTD, and YTD Grouped. The dimension diagram
should appear as follows:

7-11
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Task 3. Create a single - category relative time category.

1.
2.
3.
4.
5.
Collapse each relative time category.

Create a Same Month, Prior Quarter special category.
Hint: Click the right side of the Time root category label, and then drag the
crosshair under the default relative time categories.
Category label: Same Month, Prior Quarter
Click the Relative Time tab.
Under Relative time, click Same Month, Prior Quarter.
The Basic approach is a Single Category with a Context period of Quarter and a
Context offset of -1.
Transformer uses these parameters to create a relative time category of April
2007. Transformer looks at the Current Period of July 2007 and determines that
it is the first month in the third quarter. Transformer then determines the first
month of the second quarter, which is April 2007, and displays those values.
Only a custom relative time period can be modified in the Details area.
Click OK.
Task 4. Create a second single-category relative time

category.
1.
2.
7-12
Create a Same Month, Prior Year special category.

Hint: Click the right side of the Time root category label, and then drag the
crosshair under the default relative time categories.
Category label: Same Month, Prior Year.

RELATIVE
3.
4.
5.
TIME
Under Relative time, click Same Month, Prior Year.

You see that your Basic approach is a Single Category with a Context period of
Year and a Context offset of -1.
Transformer uses these parameters to give you a relative time category of July
2006. Transformer looks at the Current Period of July 2007 and determines that
it is the first month in the third quarter of 2007. Transformer then goes to the
first month of the third quarter in the prior year, which is July 2006, and
displays those values.
Click OK.
You created two relative time categories - Same Month, Prior Quarter, and Same
Month, Prior Year - as displayed in the dimension diagram.
Close the Time dimension diagram.

1.
2.
3.
Check the model and generate the categories, and then click OK to accept the
warning.
Right-click the Sales and Marketing PowerCube, and click Properties.
Set the PowerCube file name to C:\Edcognos\C88382\
sales_and_marketing.mdc.

7-13
COGNOS
4.
5.
6.
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Create the PowerCube.

Right-click the Sales and Marketing PowerCube.
Select Publish PowerCube as Data Source and Package.
Method: Publish the PowerCube using current settings

1.
2.
3.
4.
5.
6.
7.
7-14
Logon to Cognos Connection.

Username: admin
Package: Sales and Marketing
Expand Time to display the relative time periods.
Drag Same Month, Prior Quarter to the Rows drop zone.
Drag Same Month, Prior Year and Current Month to the rows below Same
Month, Prior Quarter.
Drag Products to the Columns drop zone.

RELATIVE
8.
TIME
Drag Quantity to the Measures drop zone.
9. Close Analysis Studio and Internet Explorer without saving.

10. Close the model without saving and leave Transformer open for the next demo.
Results:
You created two additional relative time categories, one for the
same month in the prior quarter and another for the same month in
the prior year.
Instructor Notes
This model is used in the next demo. However, you will close it and re-open it to use an unmodified
copy. If you choose you use the same model and build the cube, the cube may be locked if you attempt
to build it without enough time passing for the lock to be released. You can use the PCConn utility to
get around this. See Maintain Models and PowerCubes module. Be sure to close Analysis Studio to
prevent the locking of the cube.
7-15
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Customize Relative Time Categories

A custom relative time category is a special category
used to track measures over time periods that
Transformer does not support.
You can create a custom category using one of these
basic approaches:
Single category
Period-to-Date Total or Period-to-Date Total

Grouped
N-Period Running Total or N-Period Running Total

Grouped
If the default relative categories do not meet your needs, you can create custom relative
time categories.
When you create a custom relative time category, Transformer displays the detailed
options associated with a relative time category, allowing you to explicitly control the
specific relative time period you want to create.
Instructor Notes
These categories are based on time periods you choose. For example, you can create a custom
relative time category that spans a specific time period, either in the past or in the future.
For any relative time category type other than Custom, you can view the detailed options, but you
cannot change them. To construct a customized relative time category, you can start with one of the
predefined categories, make it a custom category, and then modify the settings.
When setting up a custom relative time category, you may find it helpful to refer to the properties of
existing category examples that are similar to what you need.
7-16

RELATIVE
TIME
Customize: Single Category

A single time period such as last week.
Properties of single category of last week

Target period: Week
Target offset: -1
Context period: Year
Context offset: 0
Note: if Context offset was -1, the period would be last year,
prior week
Target period: Indicates the periods for which you want to create a relative time
category.
Target offset: Sets the time position relative to the current period.
Context period: Indicates a time period within which the Target period occurs.
Context offset: Sets the position of the Context period relative to the current period,
where 0 corresponds to the current period.

7-17
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Customize: Period-to-Date
Period-to-Date is a sequential set of periods, which
start at the beginning of a period and end at
another specific period, such as Month-to-Date.
Properties of month-to-date for the previous 6 months
Basic Approach: Period-To-Date Total
To-date period: Month
Target period: Week Target offset: 0
Context period: Month Context offset: -6
Period-to-Date (Grouped) creates a range of to-date categories.

If selecting the Period-To-Date, you will have to set the To-Date period, which
specifies the period for which you want to-date totals.
Context Offset sets the position of the Context period relative to the current period,
where 0 corresponds to the current period.
Target offset: Sets the time position relative to the current period.
7-18

RELATIVE
TIME
Customize: N-Period Running Total

N-Period Running Total is a fixed period of time
that moves as the current period progresses.
6 month running total for 2
quarters before the current
quarter.
In some cases, you may want to set up relative time categories that span several specific
time periods, either in the past or the future. Unusual reporting periods that are not
covered by Transformers built-in relative time categories can be created in a custom
category.
A three-month rolling total from the end of the last month sums the values from the
previous three months, no matter what those months are.
If you enter positive numbers for the Target offset or the Context offset, the current
period should not be the most recent period for which you have data. You must
include time periods later than the current period so that Transformer can use them in
positive (Future) contexts.

7-19
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Demo 2: Create a Custom Relative Time Category

Purpose:
The financial advisors want to view the company's current moving
annual total (MAT). They also want to compare the company's
revenue performance to the previous MAT to analyze year-over-year
performance. To do this you will create custom relative time
categories.
Components:
Model:
User ID:
admin
Password:
Education1
Task 1. Open a model.

1.
2.
Open a Transformer Model.

Transformer8\EN
Generate the categories, and click OK to accept the warning.
Task 2. Create a custom relative time category with an

N-Period running total basic approach.
1.
2.
7-20
Click the Time dimension label, and then click Show Diagram.
Close all relative time categories to make it easier to display the categories you
will add to the dimension diagram.

RELATIVE
3.
4.
5.
TIME
Create a Moving Annual Total (MAT) category.

Hint: Click the right side of the Time root category label, and then drag it
under the default relative time categories. The pointer should be a
crosshair.
Category label: MAT
Change the settings as indicated in the following table:
Option
Setting
Explanation
Relative
Custom
This option controls the specific time period for
time
which you want to create a relative time category by
using the following options: Basic approach,
Number of periods, Target and Context period,
and Target and Context offsets.
Basic
N-Period This option specifies the basic type of relative time
approach Running
category. N-Period Running Total is a fixed period
Total
of time that moves as the current period
progresses. In this demo, you are going to use a 12month running total. In other words, this category
will return the sum of the values from the previous
12 months, no matter what those months are.
Number 12
This option specifies how many periods will be
of periods
included in the calculation.
Target
Month
This option indicates that the target period will
period
occur at the month level.
Context
Year
You specified the period for which you want to
period
create a relative time category.

7-21
COGNOS
6.
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Leave the Target offset and Context offset box set to 0, and then click OK.
The dimension diagram displays the new time category MAT.
If you created an analysis in Analysis studio, you can view all values for the last
year from the current period (1 year ago starting at July, 2007).
7-22

RELATIVE
TIME
Task 3. Create a MAT Comparison special category.

1.
Create a MAT Comparison category.

under the default relative time categories. The mouse pointer should be a
crosshair.
Category label: MAT Comparison
Task 4. Compare current MAT values with previous MAT

results.
1.
2.
3.
Create the Current MAT category.

Hint: Click the right side of the MAT Comparison category label, and then
drag it under the Year categories. The mouse pointer should be a
crosshair.
Category label: Current MAT
In the Relative time box, click Custom.

7-23
COGNOS
4.
5.
7-24
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Set the following properties:

Basic approach: N-Period Running Total
Number of Periods: 12
Target period: Month
Context offset: 0
Target offset: 0
Click OK.
The dimension diagram displays the new time category Current MAT.

RELATIVE
6.
7.
8.
9.
TIME
Create a Previous MAT category.

Hint: Click the right side of the MAT Comparison, and then drag it under the
Year categories.
Category label: Previous MAT
In the Relative time box, click Custom.
Set the following properties:
Basic approach: N-Period Running Total
Number of Periods: 12
Target period: Month
Context offset: -1
Target offset: 0
The Context offset of -1 provides information from the previous year.

7-25
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
10. Click OK.

The dimension diagram appears as shown below:
You can now view all values for the last year from the current period (1 year
ago starting at July, 2007) and compare it against the Moving Annual Total from
the previous year.
11. Close the dimension diagram.
7-26

RELATIVE
TIME

1.
2.
3.
4.
5.
Insert a new PowerCube called MAT Comparison.

Check the model, generate the categories, and then click OK to accept the
warning.
Right-click the MAT Comparison PowerCube, and then click Create
Selected PowerCube.
Right-click the MAT Comparison PowerCube.
Task 6. View the result in Analysis Studio.

1.
2.
3.
4.
Launch Analysis Studio and create a Blank Analysis.

Package: MAT Comparison
Drag MAT Comparison to the Rows.
Drag Products to the Columns.

7-27
COGNOS
5.
6.
7.
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

Your analysis appears as shown below:
You can now compare your current moving annual total with the results from
the previous year.
Close Analysis Studio, and Internet Explorer without saving the report.
Close the model without saving, and leave Transformer open.
Results:
You added custom relative time categories to view the current
moving annual total (MAT) and to compare the company's revenue
performance to the previous MAT for analyzing year-over-year
performance.
7-28

RELATIVE
TIME
Future Relative Time Categories

Display future projections. Your data source must
contain future time periods and values.
Revenue/
Projected
Revenue
2006
984501
2007
1278476
2008
3495600
2009
4325900
Date
10084477
Revenue
Projected Revenue
Example (current period set at Dec. 2006): Its projected that by 2009,
there will be a four-year total of over $10 million in revenue
If your data source contains forecasting values, you can build future relative time
categories to determine projections into the next quarter or even into the next year.
Instructor Notes
For example, if your Queries list includes a forecasting query with future revenue projections for 2008
and 2009, you can create future relative categories to display the forecasting projections. Based on
your forecasting projections, you can make informed business decisions about your organization.
The slide example illustrates available forecasting revenue results for 2006 - 2009 in the data source.
With the creation of future relative time categories, users can display projected revenue values for the
year 2009.
Because forecast values project beyond the current period into the future, it is important to ensure that
the current period is not set to the latest date in your model.
7-29
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Considerations
Avoid multiple time dimensions in a PowerCube.
Define the date input format.
Limit the range of dates included in the model.
If you make modifications to the time dimension only,
use Generate Date Categories to update the model,
instead of regenerating all the categories.
When Transformer reads date values from the data sources you set up, it requires that
you define how the dates are formatted when the data sources fail to include date
information.
Avoid multiple time dimensions. Multiple time dimensions can cause confusion for
users if they try to filter on more than one time dimension at the same time. While it
might seem logical to add separate time dimensions to a model based on columns such
as Date and Ship Date, use a single time dimension and then use measures based on
calculations for elapsed time between two date values.
Instructor Notes
You cannot create more than one time dimension in a single PowerCube that has a time-state measure
because Transformer is designed to use values from a single time dimension when performing timestate rollups.
7-30

RELATIVE
TIME
Summary
customize relative time categories

7-31
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Workshop 1: Custom Relative Time Categories

You are asked to create a PowerCube that shows the running totals for Sales for the last
three months with values for change and growth over that period. They will be
compared with the same parameters for last year. The data required is available in Sales
and Marketing.mdl, located in C:\Program Files\cognos\c8\webcontent\
samples\Models\Transformer8\EN. The following modifications are required:
Create a new relative time category called Last 3 Months - Running Total.
Custom N-period running total (grouped) time categories for a three-month period,
target period of one month, context period of year, and context range of -1.
Publish the PowerCube and view the result in Analysis Studio.
7-32

RELATIVE
TIME

Task
1. Open the model.
Where to Work
Hints
File menu
2. Create a custom
relative time
category.
Show Diagram
Category label: Last 3 Months Running Total

Custom N-period running total
(grouped)
three-month period
target period = month, context
period = year
context range of -1
3. Publish the
PowerCube directly
to Cognos
Connection.
PowerCube List.
4. View the result in

Analysis Studio.
Blank Analysis
Right-click menu
Insert and create a PowerCube

called Custom Grouped.
Publish PowerCube as Data
Source and Package.
Rows: Last 3 Months, Running
Total
Columns: Products
Measure: Revenue

7-33
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

After creating the new relative time category, the result appears as shown below:
7-34

RELATIVE
TIME
Workshop 1: Step - by - Step Instructions

Components:
Package:
User ID:
admin
Password:
Education1!
Task 1. Open the model.

1.
In Transformer, open a Model.

Transformer8\EN
Task 2. Create a custom relative time category.

1.
2.
3.
4.
Click the Time dimension label, and then click Show Diagram.
Close all relative time categories to make it easier to display the categories you
will add to the dimension diagram.
Create a new relative time category.
under the default relative time categories. The pointer should be a
crosshair.
Category label: Last 3 Months - Running Total

7-35
COGNOS
5.
BI
TRANSFORMER:
7.
OLAP
MODELS
(VERSION
8.3)
Change the settings as indicated in the following table.

Option
Setting
Relative time
Basic approach
Number of periods
Target period
Context period
Context range
6.
DESIGNING
Custom
N-Period Running Total (Grouped)
3
Month
Year
-1
Click OK.
The dimension diagram displays the new relative time category.

1.
2.
3.
4.
5.
7-36
Insert a new PowerCube called Custom Grouped.

Check the model, generate the categories, and then click OK to accept the
warning.
Right-click the Custom Grouped PowerCube, and then click Create Selected
PowerCube.
Right-click the Custom Grouped PowerCube.

RELATIVE
TIME

1.
2.
3.
4.
5.
6.
7.

Package: Custom Grouped
Drag Last 3 Months, Running Total to the Rows drop zone.
Drag Products to the Columns drop zone.
Close Analysis Studio, and Internet Explorer without saving the report.
Close the model without saving, and close Transformer.

7-37
COGNOS
7-38
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

Cognos 8 BI
Instructor Notes
User ID: admin
COGNOS
8-2
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

USE
MULTIPLE
DATA
SOURCES
Objectives
discuss the use of multiple data sources
Instructor Notes
the Transformer development process
Transformer data sources
how to build a model
8-3
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Why use Multiple Data Sources?

use data from different data source types
add a new data source to an existing model
improve performance
make data easier to manage
Multiple data sources reduce the total volume of data that Transformer processes,
which speeds up category generation and PowerCube creation.
Instructor Notes
Some data is static, while other data is updated frequently. If you separate static data from dynamic
data into different data sources, you do not have to manage the static data as often. Multiple data
sources offer even greater benefits if database joins are simple (or non-existent),index creation is kept
to a minimum, cube builds are performed only for dimensions with categories that have changed, fact
processing is done during category generation.
Sales information systems do not usually include information about staffing levels for each branch. By
including a data source that provides this in a model, you can help identify valuable information, such
as the average sales per employee. For example:
A) Human Resources have staff information in an Excel spreadsheet, Finance has staff payee
information in a data mart, and Sales has staff sales records in an .iqd data source.
B) Management is now tracking performance indicators in a new database. This information can be
added as a new source to an existing model.
8-4

USE
MULTIPLE
DATA
SOURCES
Multiple Data Sources

There is no limit to the number of data sources.
After all data sources are read, sorting and processing
occurs.
Columns in a data source adds structure to a model.
To properly associate measure values, Transformer
must be able to identify each category through the
structure in the measures data source.
If you have a high volume of data, you can achieve better performance by getting the
data from multiple sources. For large volumes of data, you can read values for the
lowest-level categories of each dimension from a single data source.
Instructor Notes
Guidelines that to improve performance of processing multiple data sources are:
create one structural data source for each dimension, and then set up one transactional data
source to provide the measures for those dimensions (simple dimensions and most time
dimensions do not require a separate data source)
relate data sources and check the model for any potential issues
When data is read from the separate data sources, Transformer directly associates column values with
the lowest-level categories in the model. As a result, it does not have to read and drill up to the higherlevel categories (which provide the structure of the model) when building PowerCubes.
By creating smaller queries based on multiple data sources (each with data pertaining to a single
dimension), only less memory is required to obtain the results. This is the case even though the total
number of rows being processed is slightly higher.
8-5
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Structural vs. Transactional Data Sources

Structural
contains structural data

(usually text) used to create
dimensions and levels
Transactional
contains transactional
data (usually numeric)
representing the
measures
Guidelines for structural data sources: Create one data source for each dimension, Place
structural data sources before transactional data sources.
Guidelines for transactional data sources: Create one or more data sources to provide
measures, include enough structure in the transactional data sources to roll up measures
in each dimension.
Instructor Notes
Structural data sources: primarily contains columns with text data, contains columns that define levels,
which defines the model structure, primarily used as dimensions in Transformer.
Transactional data sources: primarily contains columns with numeric data and primarily used as
measures, contains text columns that reference the categories in a dimension structure.
Q. Why would you include more than one transactional data source in a model?
A. If your data comes from a data warehouse and is organized with two Fact Tables (transactional
data). It is better to organize two transactional data sources than to merge the data from the tables.
8-6

USE
MULTIPLE
DATA
SOURCES
Plan the Data Sources

Data Source 1
Structural
Data Source 2
Structural
Data Source 3
Structural
Data Source 4
Transactional
If you use multiple data sources, consider creating:

a single structural data source for each of Dimension 1, Dimension 2, and
Dimension 3
one or more data sources with measure values
Instructor Notes
Each data source contains a column that exists in both the Structural and Transactional Data Sources.
This makes it possible for the measures to be associated with Dimension 1, Dimension 2, and
Dimension 3.
Each structural data source provides category values for the levels in a single dimension. Each data
source provides category values for the lower levels in each dimension and also in the model
measures.
Structural data sources do not have to provide level columns down to the lowest level in the dimension.
8-7
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Demo 1: Integrate Multiple Data Sources into a Model

Purpose:
You want to create a multipurpose PowerCube that provides an
overview of the company. You will build a model based on multiple
data sources. The model will contain product, location, and retailer
information, as well as basic measures for Great Outdoors.
Components:
Transformer
User ID:
admin
Password:
Education1!
Task 1. Create a new model using a Cognos report.

1.
2.
8-8
Start Transformer.
Create a new model.
Model Name: Great Outdoors
Data source name: Product Information
File location: Public Folders > GO Data Warehouse (query) > Product
Information
Query definition details: All Query1.0 items
Hint: Do not run AutoDesign.
The product information data source is added to the Data Sources list. This is a
structural data source.

USE
MULTIPLE
DATA
SOURCES
Task 2. Add Region information to the model.

1.
Insert another data source to the model.

Hint: Data Sources list title bar, Insert Data Source (Ins)
Data source name: Regions
Location: C:\Edcognos\C88382\Regions.csv
Task 3. Add Retailer Information to the model.

1.
2.
3.
Insert another data source in the model.

Data source name: Retailers
Expand Sales and Marketing (Query) > Sales (Query) > Retailer Site.
Add Retailer type, Retailer name, Retailer code, and Retailer site code to
the Query definition details pane.

8-9
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Task 4. Add basic measures to the model.

1.
2.
Insert another data source to the model.

Data source name: Basic Measures
Location: C:\Edcognos\C88382\Basic Measures.csv
The Basic Measures data source is added as the fourth data source. It contains
all the basic measures required for the model, as well as low-level structural data
used to map measure values to the dimensions. This is a transaction data
source.
Results:
You added the structural data sources for product information,
locations, and retailers to the Data Sources list, as well as the
transactional data source containing the critical success factors.
8-10

USE
MULTIPLE
DATA
SOURCES
Associate Columns with Levels

Rename columns to have identical names, or use the
Level property sheet to associate columns with a
level.
Associate each data source column with a level in the Dimension Map because
Transformer
does not support joins between columns
expects that each data source will generate some categories in the model
must be able to relate all categories to at least one measure
expects that categories for columns contained in more than one data source
are unique
Instructor Notes
When Transformer generates categories in multiple data source models, each data source is
processed separately against the model. Transformer does not perform database joins between data
sources. Instead, Transformer associates data source columns from each data source directly with
levels in the Dimension Map.

8-11
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Relate Data Sources by Renaming

Columns
How can you be sure that Revenue gets rolled up to
the Product Line level?
Structural Data Source 1

Product Line
Golf Equipment
Product Type
Putters
Outdoor Protect. Sun Shield
Transactional Data Source 2

Product Name
Course Pro Putter
Product
Revenue
Course Pro Putter
300
Sunscreen
Sun Shield
400
Rename the "Product" column

in Data Source 2 to "Product
Name"
Transformer relates columns from different data sources to the same level in a
dimension if the column names are identical in all data sources.
Be aware that when you rename columns, the names must be identical, including case
and punctuation.
8-12

USE
MULTIPLE
DATA
SOURCES
Relate Data Sources by Source

Association
How can we be sure that Revenue rolls up correctly?
Instead of renaming columns, you can use Source Association to relate data sources.
Source association specifies that even though columns have different names, they
contain the same data in each data source.
Instructor Notes
In Transformer, you can relate columns from different data sources to the same level in a dimension.
Slide: Employee code from the Regions data source and EMPLOYEE CODE from the Basic Measures
data source contain the same type of information. Using the Level property sheet, we can set the
source association.

8-13
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Set the Current Period

The current period is determined by the date you
define as the present date in the context of the
generated PowerCube.
Transformer uses this date as a benchmark to
determine the valid date categories.
Setting the current period for multiple data sources determines which data source will
define the date values in the time dimension.
When you create a model, by default, Transformer uses the date values in the data
source to set the current period. If no data source is set as the current period, and
several date columns exist, Transformer uses the latest date values in the multiple data
sources to determine the current period
8-14

USE
MULTIPLE
DATA
SOURCES
Demo 2: Define Column Properties

Purpose:
To meet the requirements of the multipurpose cube requested by
the president of The Great Outdoors Company, you need to modify
column properties of your four data sources. This will ensure that
the data source columns will work together when the president
prepares the reports for analysis.
Components:
Transformer
User ID:
admin
Password:
Education1!
Task 1. Define the Regions column properties.

1.
2.
3.
4.
Expand all the data sources so that all the columns display.
In the Regions data source, right-click Region and then click Properties.
The data class is unspecified because the file is a .csv file. Setting the data class
to Text identifies the data in the column as structural. Structural columns are
used to build dimensions. Setting the data class to Text is not required, but it is
a good practice.
In the Data class box, click Text, and then click OK.
Change the data class to Text for all columns in this data source.

8-15
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Task 2. Modify column properties in the Basic Measures data

source.
1.
2.
3.
4.
5.
6.
7.
8.
Employee code in the Regions data source, and EMPLOYEE CODE in the
Basic Measures data source must be named identically (including case
sensitivity) to make sure the two data sources are related.
In the Basic Measures data source, rename EMPLOYEE CODE to
Employee code.
Retailer site code in the Retailers data source, and RETAILER SITE CODE in
the Basic Measures data source must also be named identically to make sure the
two data sources are related.
Rename RETAILER SITE CODE to Retailer site code.
Right-click Date, and then click Properties.
In the Data class box, click Date to indicate that the column contains date and
time information.
Click the Time tab.
In the Date input format box, click MDY.
You can open the data source viewer to see that the format is MDY.
Transformer can now read the date values as entered (for example, 12-31-2006).
In the Degree of detail box, click Month.
This detail does not specify the lowest time level in your data, which is day.
Your .csv file contains a date column with month/day/year. This is too much
detail, therefore Month is chosen as the lowest level.
Click OK.
Instructor Notes
Point out the column relationships between data sources. Explain that each structural data source must
link back to the transactional data source, but structure data sources do not have to link to other
structural data sources.
8-16

USE
MULTIPLE
DATA
SOURCES
9. In the Basic Measures data source, right-click Quantity and click Properties.
10. In the Data class box, click Numeric.
It is good practice to specify the data in the Quantity column as numeric.
11. Click OK.
12. Set the data class for the Revenue and Product Cost columns to Numeric.
These columns are used to define measures.
Results:
You set properties of columns in the four data sources included in
the model so they will work together to build the PowerCube, and the
president can prepare the required reports for analysis.

8-17
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Demo 3: Build the Dimension Map

Purpose:
You will build a Dimension Map using the multiple data sources you
just added to the model.
Components:
Transformer
User ID:
admin
Password:
Education1!
Task 1. Create the dimensions.

1.
2.
3.
4.
5.
6.
8-18

Products: Product line, Product type, Product name, Product number
Regions: Region, Country, City, Position name, Employee name
Double-click the Employee name level.
Change the source Association to Employee key.
Add a label association: Employee name.
Create dimension:
Retailers: Retailer type, Retailer name, Retailer site code
Add the Date dimension to the left of the Products dimension.

USE
7.
MULTIPLE
DATA
SOURCES
Add Quantity, Revenue, and Product cost to the Measures list.

Results:
You built a Dimension Map from the multiple data sources in the
Data Sources list, and made modifications as required.

8-19
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Demo 4: Insert a Dimension from an OLAP Package

Purpose:
You want to add a dimension to the dimension map. The current
data sources do not have the required columns. You will add a new
dimension using an OLAP Package.
Components:
Transformer
User ID:
admin
Password:
Education1!
Task 1. Add a new dimension to the Dimension Map.

1.
2.
3.
8-20
Insert a new dimension from a package.

Hint: right-click the Dimension Map area, Insert Dimension from Package
Package: Sales and Marketing
Expand the Promotions dimension and hierarchy.
Add all levels within the hierarchy.
Hint: Select the Promotions check box to select the entire hierarchy.

USE
4.
MULTIPLE
DATA
SOURCES
Click OK when complete.

The Promotions dimension appears in the dimension map. The Sales and
Marketing data source is added to the Data Sources list as shown below:
The data sources are added to the model. In order to generate a PowerCube
from this model that contains multiple data sources, you must specify
uniqueness.
Close the Transformer without saving the model.
Results:
You added a dimension to the dimension map using an OLAP
Package.
Instructor Notes
Uniqueness is covered in the next module.

8-21
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Summary
8-22
discuss the use of multiple data sources

Uniqueness
Cognos 8 BI
Instructor Notes
User ID: admin
COGNOS
9-2
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

UNIQUENESS
Objectives
identify and resolve conflicts between data sources
validate a multiple data source model
Instructor Notes
9-3
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Validate Multiple Data Source Models

identify dimension and level relationships within a
model.
Direct
(yellow)
Indirect
(light yellow)
Conflicts in
the model (red)
Unrelated
(white)
Models are valid when the data sources and the dimensions in the model are correctly
related. Before you generate categories, you should validate the model to resolve
potential structural problems and reduce the duration of processing.
Instructor Notes
Data source scope levels:
Yellow: Level derived directly. The level is directly related to a source column from the data source.
Light Yellow: Level derived indirectly. The level is not related to a source column from the data source.
Instead, another level in the dimension is related through a source column from another data source.
White: Level not derived. The level is not related to a source column by name from the data source.
Red: Level referenced but not derived. The level is related to a source column by name from the data source.
However, the data source is missing columns within the dimension structure.
9-4

UNIQUENESS
Demo 1: Data Source Scope

Purpose:
You want to validate the model to ensure that there are no problems.
If there are errors, you can examine the data source using the Show
Scope command and decide how to resolve the issues.
Components:
Transformer
User ID:
admin
Password:
Education1!
Task 1. Identify how each data source relates to the different

dimensions.
1.
2.
3.
4.
5.
6.
Open Transformer.
Open the model.
Location: C:\Edcognos\C88382\PPT-Uniqueness
Name: Demo 1_Start.pyj
Check the model for warnings or errors.
Hint: User ID - admin, Password - Education1!
Three errors and three warnings exist. If you receive warnings, you can still
build a PowerCube. However, you cannot generate a PowerCube until the
errors are corrected. Use Data Source scope to correct these issues.
Click OK.
Expand the Product Information data source, and then right-click the Product
Information query.
Click Show Scope.

9-5
COGNOS
7.
8.
9.
9-6
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Select Data Sources, and then in the list, click Product Information.
The Data Source scope Dimension Map appears.
The levels in this dimension are dark yellow, indicating that data values for these
levels come from the product information data source (Cognos 8 Report).
In the Data Sources list, click Regions.
The levels in the Region dimension are dark yellow, indicating that data values
for these levels come from the Regions data source (a .csv).
In the Data Sources list, click Retailers.
All the levels in this dimension are dark yellow, indicating that all data values for
these levels come from the Retailers data source (Cognos 8 package).

UNIQUENESS
10. In the Data Sources list, click Basic Measures.
Red indicates the level is derived from a data source that has missing parental
data. There is currently no link between the Basic Measures data source and the
levels above the Product Number, Employee name, and Retailer site code
levels. For example, a Product Number column exists in the Basic Measures
data source but no Product name, Product type, or Product line columns.
Therefore, Transformer cannot roll up the measure values contained in the
Basic Measures data source from Product Number to Product line.
These red levels caused the errors and warnings in step 2.
Results:
You validated the model and found three errors and three warnings.
To troubleshoot the errors and warnings, you used the Show Scope
command and found that the Basic Measures data source is missing
parental data.

9-7
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
What is Uniqueness?
Data Source 2 is independent of Data Source 1.
How can you ensure that Revenue is rolled up to the
Region level?
Structure Data Source 1
Transaction Data Source 2
Employee Code
124
125
126
Employee Code
124
125
126
Revenue
9000
110850
57780S
Declare unique to indicate that

Employee Code in Data Source 1 is
the same as in Data Source 2.
Level uniqueness means that no two categories in a level can represent identically
named distinct categories.
Level uniqueness is required so that Transformer identifies each category in the level by
its source value alone, without reference to its ancestor category.
Instructor Notes
In multiple data source models where some data sources contain details about the dimension structure
and other data sources supply measure values but lack details about dimension structure, you must
declare level uniqueness to roll up measure values to the structural data. Rollup values are a summary
of the lowest level of transaction values from the source data.
9-8

UNIQUENESS
Level is Not Unique: The Issue
Records from Data Source 1
Staff Name
City
Staff Name
Revenue
Jake Cartel
Melbourne, Australia
Jake Cartel
110850
Emile Clermont Paris, France
Emile Clermont 57795
Jake Cartel
Jake Cartel
London, U.K.
45650
Staff Name is not unique, therefore you do not

know to which City the revenues should roll up.
When you combine two data sources on the Dimension Map, you are trying to create a
relationship between two independent data sources so that more information can be
presented to the user. You are creating this relationship at a particular level. This level
must be unique. It is unique in that no other category, or combination of category and
parent categories, is the same.
Instructor Notes
In Data Source 1, two Employees with the same name exist in two different cities; therefore, Staff
Name is not unique. This is okay for Data Source 1 because the combination of Staff Name and City is
unique (that is, the Jake Cartel working in Melbourne, Australia is different from the Jake Cartel in
London, U.K.). Transformer can distinguish between the two categories.
In Data Source 2, Staff Name is not unique. However, this time there is no city context to help make it
unique. The question is: Does revenue for Jake Cartel roll up to Melbourne or London?
9-9
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Level is Not Unique: A Solution

Add the City column to Data Source 2.
Staff Name
Staff Name
Jake Cartel
City
Melbourne, Australia
Jake Cartel
Rev
City
110850 Melbourne, Australia
Emile Clermont Paris, France
Emile Clermont 57795 Paris, France
Jake Cartel
Jake Cartel
London, U. K.
45650
London, U. K.
New column
By adding the City column to Data Source 2, Transformer can differentiate between
the values in the Staff Name column, and can roll up the data to the correct city.
Instructor Notes
Another solution is to add more structure to both data sources by concatenating two columns to create
a new field so that this new column is unique. The new column can be created in both the original data
sources, or it can be added to the data sources in Transformer.
9-10

UNIQUENESS
Declare Levels Unique

You can prevent model errors caused by changes in
the source data by designating a unique level.
A unique level specifies that categories in that level
are identified by their source values alone, without
reference to their ancestors.
Transformer verifies category uniqueness during PowerCube generation.
Instructor Notes
It is possible that the source data contains columns that populate levels that you thought were unique
but are not. In this case, a message appears to inform you when you attempt to generate categories or
build a PowerCube. If categories for some levels are derived from transactional data sources
(containing measures), Transformer may not be able to detect uniqueness conflicts.
After you have successfully generated a PowerCube with no uniqueness warnings, you can disable
uniqueness verification (Data Source property sheet) to improve performance in the PowerCube.
9-11
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Identify Model Issues

The Check Model command helps you identify:
insufficient context
levels that cannot be reached in the current drilldown path
uniqueness issues
an unbalanced category tree
Transformer always checks the model before generating categories or creating

PowerCubes, but you can run a manual check at any time.
When Check Model runs before category generation, the tests are intended to validate
the setup of data sources and dimensions so that categories are generated appropriately.
Instructor Notes
It is good practice to run Check Model at key stages in the design process and again at time of cube
creation to alert you of potential model issues.
9-12

UNIQUENESS
Demo 2: Declare Levels Unique

Purpose:
You will correct the data values that have missing parental data by
setting the levels as unique.
Components:
Transformer
Task 1. Set levels as unique, and validate the model.

1.
2.
3.
4.
In the Data Source scope Dimension Map, right-click the Product number
level, and click Properties.
Select the Unique check box to declare the level unique.
Click Yes to confirm that the Product number level has unique categories.
Click OK.
Product number is dark yellow to indicate a direct relationship to the Basic
Measures data source. Its parent levels are light yellow to indicate an indirect
association and that it allows for roll up to the Product line level.

9-13
COGNOS
5.
6.
7.
8.
9.
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Set Employee name and Retailer site code as Unique.

The results appear as shown below:
Currently, there are only shades of yellow. This indicates that there is sufficient
information to roll up measures in the Basic Measures data source to the
highest level in each dimension.
Check the Model.
You corrected the errors and warnings. No problems were found.
Save the model as Demo 2.pyj.
Location: C:\Edcognos\C88382\PPT-Uniqueness
Close the model.
Results:
You declared levels unique and generated a PowerCube.
Instructor Notes
You create the PowerCube and close the model to generate the log file, which you will use in Demo 3,
Task 2.
9-14

UNIQUENESS
Demo 3: Uniqueness Violations (Instructor only)

Purpose:
The Great Outdoors has hired a new Sales Representative, Max
Caron. He will be working in Calgary, Canada. You must include him
in the Regions.csv data source file and then build the PowerCube to
reflect the changes.
Components:
Transformer, Microsoft Excel
Task 1. Modify Region.csv to include Max Caron.

1.
1.
2.
3.
Open Regions.csv in Microsoft Excel.

Location: C:\Edcognos\C88382
In the cells of row 974, type Americas, Canada, Calgary, Controller,
Max Caron, 999, 4972.
Save the spreadsheet as C:\Edcognos\C88382\Regions.csv.
Close the file in Microsoft Excel.
This file now contains a uniqueness violation. You have made an error in the
assignment of the Employee key. Employee key 4972 already belongs to
Penelope Tamrine. At cube creation time, Transformer should display a
message that there is one uniqueness violation.
Instructor Notes
This is instructor only for clarity and so that students remember the result rather than the process; they
are not going to edit source data to create these problems. Also, the source data will be used in other
demos throughout this course, so it is better that the student data files on the classroom machines
remain unmodified.

9-15
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Task 2. Update the PowerCube.

1.
2.
3.
4.
5.
In Transformer, open Demo 2.pyj.

Location: C:\Edcognos\C88382\PPT-Uniqueness\Demo 2.pyj
Check the Model.
There are no issues in the model.
Transformer issues the following error:
Transformer shows the Employee code uniqueness violation.

Click OK three times to accept the warnings.
Review the generated log file in Notepad.
Location: C:\Edcognos\C88382\Demo 2.log
Read through the log to find where Transformer identified the uniqueness
violation. The last line in the log file is "(TR0136) A uniqueness violation was
detected. The process has been aborted. [->OK]".
Instructor Notes
Although you added Max Caron to the region data source, you did not add any transactional data for
Max to the Basic Measures data source. By default, Transformer does not include categories for which
there is no transactional data.
NOTE: Although not typical, you are modifying the Employee key to illustrate a uniqueness violation.
9-16

UNIQUENESS
Task 3. Reset the data in the Regions.csv file.

1.
2.
3.
Open Regions.csv in Microsoft Excel.

Location: C:\Edcognos\C88382\Regions.csv
Remove all the data in row 974.
Save and close the file.
Task 4. Check the Model and Create PowerCubes.

1.
Check the Model and create the PowerCubes.

The uniqueness violation is rectified. The PowerCube generates successfully.
Results:
You updated the PowerCube by making modifications to the data
source.

9-17
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Unique Move
ensures the category you move within the level has

its data history move with it
avoids manually restructuring the categories in a

dimension when you change the parent category
that is tied to a unique level
The ability to move categories in unique levels to new contexts lets you keep the
structure of a current dimension without having to regenerate all categories in that
dimension.
Measure values, even those accumulated under the old structure, are thereafter rolled
up to the new path of the moved categories.
Instructor Notes
When you move a category from a unique level, a uniqueness violation is reported during category
generation because the moved category now appears in a different context.
With the Unique Move feature you can have uniqueness violations treated as a request to move the
category to a new context and to bring the information in lower levels with it. This prevents you from
having to manually restructure the categories in a unique level to conform to the changed ancestor
data.
If an employee moves from one city to another city, Transformer moves all the child data, including, for
example, past clients and revenue.
9-18

UNIQUENESS
Demo 4: Unique Move (Instructor Only)

Purpose:
A new sales representative, Rhonda Cummings, will be trained by
the Boston office and then moved to the Miami office. As a new
employee, Rhonda's history must begin in Boston, where her
Employee key is issued to her, and then move to her sales territory
in Miami.
Components:
Transformer, Analysis Studio, Microsoft Excel
User ID:
admin
Password:
Education1!
Task 1. Generate categories, check the model, and create the

cube.
1.
2.
3.
4.
Click the Regions dimension, and then click Show Diagram.

Expand Americas, United States, Boston, Level 2 Sales Representatives.
Notice in the diagram for the Region dimension there is Level 2 Sales
Representative in Boston named Rhonda Cummings.
Publish the PowerCube as a Data Source and Package.

9-19
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
5.
Log on to Cognos Connection:

Username: admin
6. Launch Analysis Studio.
Package: Great Outdoors
7. Create a Blank Analysis.
8. Expand the Date folder and drag Date to the Columns drop zone.
9. Expand Regions > Americas.
10. Drag United States to the Rows drop zone.
11. Expand Measures and then drag Revenue to the Measures drop zone.
The revenue for Boston is 71925209 and Miami is 41676818.

12. Close Analysis Studio without saving.
9-20

UNIQUENESS
Task 2. Modify Rhonda Cumming's record to reflect her move.

(Strategy: Assign a new key)
1.
2.
3.
4.
5.
6.
7.
You want to know what happens if you move Rhonda to Miami by adding a
new employee key for her at the new office, while maintaining her old one.
In Microsoft Excel, open the Regions.csv.
Below line 20, add a new row with the following:
Row order: Americas, United States, Miami, Level 2 Sales Representative,
Rhonda Cummings, 56, 5000
Generate the Categories, and then click OK to accept the warning.
Expand the following items: Americas, United States, Boston, and Miami.
For Boston and Miami, expand Level 2 Sales Representative.
Transformer generates two categories for Rhonda: the category under the
Boston office and the category under the Miami office. The measure values
associated with the Boston office will remain in Boston.
Task 3. Modify Rhonda Cummings record to reflect her move.

(Strategy: Perform a unique move)
1.
2.
Rhonda Cummings is re-locating to Miami and you will use the Unique Move
feature so that Rhonda and all of her history are assigned to Miami.
In Microsoft Excel, open the Regions.csv data source.
In cell G21, change the Employee key to 4019.
Additional Information
Strategy A demonstrates how all information for Rhonda Cummings could be moved to Miami. This
method does not consider that some information might need to stay associated with the Boston branch
(such as revenue).
Unique Move can be very powerful and should not be used without knowing the repercussions. You
should use it only if you want ALL transactional data for a category and all its child categories to move.
9-21
COGNOS
3.
4.
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Save the file.

Even though Rhonda Cummings is relocating from Boston to Miami, she
maintains the same Employee key. You will use the Unique Move feature so
that Rhonda and all of her history are assigned to Miami. The correct procedure
is to specify that the Employee name level is a unique level, and the switch in
location is a unique move.
In Transformer, generate the categories.
The following error appears.
5.
6.
7.
Close the error message.

Double-click the Employee name level, select Move, and then click OK.
Generate the categories, click OK to accept the warning, and then create the
PowerCube.
You do not need to republish as a Data Source and Package because these
already exist.
8. Launch Analysis Studio.
9. Create a Blank Analysis using the Great Outdoors package.
10. Expand the Date folder and drag Date to the columns.
11. Expand Region and Americas, and then drag United States to rows.
9-22

UNIQUENESS
12. Expand Measures and then drag Revenue to Measures.

The revenue for Boston decreased from 71925209 to 49858237; a difference of

22066972. The revenue for Miami increased by 22066972. This is because
Rhonda Cummings, along with her history moved from Boston to Miami.
13. Drill down on Boston.
Boston no longer has a Level 2 Sales Representative. This is because Rhonda

Cummings was the only representative at this level and she has moved to
Miami.

9-23
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
14. Drill up on rows, and drill down on Miami.

15. Drill down on Level 2 Sales Representative.
Rhonda Cummings exists in Miami.

16. Close the Analysis without saving.
Task 4. Reset the data.
1.
2.
3.
In Microsoft Excel, open the Regions.csv data source.

Remove row 21.
Save the file.

(Strategy: Create a calculated column)
1.
2.
3.
4.
9-24
You will create a new calculated column, which concatenates Employee Name,
City, and Employee key to create a unique level. When Rhonda Cummings
relocates, a new and unique code will differentiate her records in Boston from
those in Miami.
In the dimension map, delete Employee name.
Expand the Regions data source.
Right-click the Regions data source, click Insert Column, and then in the
Column name box, type Unique Rep.
Set the Data class to Text.

UNIQUENESS
5.
6.
7.
8.
9.
10.
11.
12.
13.
In the Column type area, click Calculated to select it, and then click
Calculation.
Create the following expression:
"Employee name" + "City" + "Employee key"
Click OK twice.
Drag the Unique Rep column to the Regions dimension.
Set the Unique Rep level as Unique.
Click Generate Categories.
Click Regions, and click Show Diagram.
Expand: Americas, United States, Boston, Level 2 Sales Representative.
In Boston, Rhonda Cummings has a Unique Rep code of Rhonda Cummings
Boston 4019. If you entered a new record for Rhonda in Miami, in the
Regions.csv, then a Unique Rep code for RhondaCummingsMiami4019 will be
created as a separate category. New orders for Rhonda Cummings could then
be reported on as they are entered into the data source.

1.
2.
3.
4.
5.
Delete the Unique Rep level.

From the Regions data source, drag Employee name to the Regions
dimension.
Set the source association to Employee key.
Add a label association and set it as Employee name.
Make the Employee name level Unique.

9-25
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

(Strategy: Change city, lose all Boston history )
1.
2.
3.
4.
5.
6.
7.
8.
9.
You now want to know what happens if you completely move Rhonda to
Miami and assign all of her Boston history to Miami.
In cell C20, change the City for Rhonda Cummings to Miami.
In Transformer, click Generate Categories, and then click OK to close the
warning.
Expand: Americas, United States, and Miami.
Expand Level 2 Sales Representative.
Rhonda Cummings and all her data is now associated with the Miami location.
Close the Transformer without saving the model.
If necessary, close Internet Explorer.

1.
2.
3.

In cell C20, change the City for Rhonda Cummings to Boston.
Results:
You modified a model to show the change when one of your sales
representatives moved office locations.
9-26

UNIQUENESS
Summary
identify and resolve conflicts between data sources
validate a multiple data source model

9-27
COGNOS
9-28
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

10
Cognos 8 BI
Instructor Notes
User ID: admin
COGNOS
10-2
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

WORKING
WITH
MEASURES
Objectives
discuss the purpose and uses of measures
describe regular and calculated measures
create calculations before or after rollups
Instructor Notes
The_Transformer_Development_Process
Data_Sources_in_Transformer
PPT-Building_a_Model

10-3
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Measures
Measures gauge the performance of your business.
Two types of measures:
a regular measure
a calculated measure
Measures are quantifiable results, or key performance indicators used to determine the
success of a business operation.
You can define each measure by modifying its settings in the property sheet.
Instructor Notes
Regular Measures: summary of available information taken directly from a source column in the data
source. Columns of numeric data are included where possible, in the data source to support the
measures outlined in the model plan. A column containing data related to cost can be used to support a
measure for Product Cost as well as Average Product Cost.
You can create a calculated measure which derives new numeric data for measures when no direct
source column is available. The calculation can involve existing transactional values, constants, and
arithmetic functions. To store the calculation and the measures that are used in it, create the
calculation in the model. If the calculation is used repeatedly in multiple cubes, it may be more efficient
to create it in the data source.
10-4

WORKING
WITH
MEASURES
Demo 1: Modify Measure Properties

Purpose:
You will build a Transformer model and customize it for the Finance
and Sales departments. Your task in the initial stage of model
creation is to assess and modify measures and their properties.
Components:
Transformer
User ID:
admin
Password:
Education1!

1.
2.
3.
Open Transformer.
Start the new Model wizard.
Model name: Measures
Data source name: Leave default
User ID: admin, Password: Education1!
Expand Sales and Marketing (query) and Sales (query).

10-5
COGNOS
4.
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Add the following items to the Query definition details items:

Time Dimension: Date
Product: Product line, Product type, Product name, Product number
Employee by region: Region, Country, City
Retailer Site: Retailer type, Retailer name
Sale fact: Revenue, Product cost, Quantity
Task 2. Build the Model.

1.
2.
Expand GO Data Warehouse (query) data source and query.

Build the following dimension map:
3.
Drag Revenue, Quantity, and Product cost to the Measures list.
10-6

WORKING
WITH
MEASURES
Task 3. Modify the Measure properties.

1.
2.
Modify the properties for Product cost.

Missing value: Zero
Users will see this value when the numeric value for a measure is missing in the
source data.
Storage type: 64-bit floating point
This storage type is for the measure value during PowerCube creation.
Precision: 2
Modify the display format of Product cost.
Hint: Format tab
Format: $#,##0
Decimal places: 2
Good model design includes appropriately formatted measures. When measures
are formatted at the model level, users do not need to perform this routine task.
This number will format the value with a dollar sign and a comma separator for
thousand values, and will scale it by 1,000.

10-7
COGNOS
3.
4.
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Click OK to apply the new display format.

Modify the properties for Revenue.
Storage type: 64-bit floating point
Precision: 2
Format: $#,##0
Decimal places: 2
Results:
You customized a Transformer model for the Finance and Sales
departments by modifying the Unit Cost and Revenue measures to
meet the model requirements.
10-8

WORKING
WITH
MEASURES
Regular and Non-Regular Rollup

Settings
Regular rollup settings determine how numeric
data is summarized.
Revenue
1,170,000.00
2,200,000.00
4,700,000.00
Regular
Rollup
Examples
Count
Minimum
1,170,000.00
Maximum
4,700,000.00
Average
2,690,000.00
Sum
8,070,000.00
Non-regular rollup settings are Time State rollups

that summarize data for a specified time period.
Rollup is the method used to summarize measure data. It specifies how Transformer
summarizes (rollup) measure values from the child categories to the parent categories.
Rollup options summarize your measure values in different ways, which provides the
opportunity to create several measures from a single column of source data.
Instructor Notes
Regular Rollup: Specifies the function applied when summarizing measure values from the lower levels
to the higher levels.
Time State Rollup: Specifies how Transformer represents the state of a measure at specific times.
Duplicates Rollup: Specifies how Transformer evaluates duplicate records in the source data. For
example, a source file may be very large and contain many records with duplicate non-measure values
(date, products, etc.). You can choose Average as the Duplicates Rollup function to combine the
duplicate records and reduce the size of the resulting cube.
Adding different rollups adds business value to the cube for minimal extra technical cost (a small
increase in cube size). For example, you could have a Revenue measure that rolls up to show the sum
value, or from the same column, you could have a Revenue measure that displays the minimum data
value.
10-9
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Calculated Measures
include data in the model that is not available in
the data source.
derive new numeric data from:
regular measures
other calculated measures
functions and constants
By customizing or calculating your measures, you can find trends that are not apparent
from your data source.
For example, if there is no source column for Profit Margin, you can calculate the
profit margin from the Revenue and Product cost columns. Profit Margin is a
calculated measure because there is no source column that directly contains this data.
Instructor Notes
After you create a calculated measure, you can control whether the measure is calculated before or
after rollup.
You can use If-then-else clauses in your measure calculations.
10-10

WORKING
WITH
MEASURES
Timing of Calculation
Before Rollup and After Rollup options determine
when the data of a calculated measure is
computed.
By default, measures are calculated after the rollup.
Calculated measures, by default, are calculated after all the transaction values for the
measure have been summarized.
Instructor Notes
You can modify the timing of measure calculations by using the Rollup tab on the Measure property
sheet. If you select Before Rollup, Transformer performs the operation for the calculated measure on
each record first and then summarizes the calculated measure. If you select After Rollup, Transformer
summarizes the numeric data first and then performs the calculation.

10-11
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Timing of Calculation: Before

Rollup
Revenue
Cost
Profit
Profit
Margin
Profit
Margin %
$400
$100
$300
300/400
75%
$300
$100
$200
200/300
67%
142%
Before Rollup: Profit Margin % for each record is calculated

first, and then these values are summarized.
Values for measures calculated before rollup are based on source values instead of on
summed values and are rolled up separately.
Performing calculations before the rollup may lead to incorrect results.
Instructor Notes
Slide: Profit Margin and Profit Margin % are performed for each record and are subsequently
summarized or rolled up. The result is an incorrect overall Profit Margin of 142%.
10-12

WORKING
WITH
MEASURES
Timing of Calculation: After Rollup
Total
Revenue
Cost
Profit
$400
$100
$300
$300
$100
$200
$200
$500
$700
Profit
Margin
Profit
Margin %
500/700
71%
After Rollup: Profit Margin % is calculated by dividing the

sum of the profits by the total revenue.
If you set the timing of the calculation for a calculated measure to After Rollup,
Transformer summarizes the numeric data and then performs the calculation.
Instructor Notes
Slide: Revenue and Cost are summarized first, and then calculations for Profit Margin and Profit Margin % are
performed. The result is a correct overall Profit Margin % of 71%.
On occasion, a measure may have to be calculated before summarizing occurs. For example, a
company collects data for sales transactions on extremely price-sensitive products, and it records price
and quantity information. To calculate revenue, it must multiply price by quantity. If After Rollup is the
timing for calculation, inflated revenues result. But Before Rollup will return accurate results.
10-13
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Category Count Measure

counts the number of categories, not the number of
rows.
specifies that the unique, non-missing, nonzero values
are counted for the dimension and level that you
select.
For example, you can create a count to show how many customers of each type bought
a specific product each month, quarter, or year. This count is a consolidation of all the
categories in the unique level Customer Number. For example, if the same customer
buys a product in two months, the quarterly rollup counts that customer only once.
Instructor Notes
Category Counts are associated with a specific data source column, and for any intersection, displays
the number of unique instances of the column that were contained in rows that contribute to a counting
rollup for a measure.
You should accept the default Activity Measure (All Measures) only if you are sure that no categories
are missing measures, and no measure values sum to zero when they are rolled up to the next higher
time period. You must use the Rollup tab of the Measure property sheet to specify the Activity Measure
for the category count. This Activity Measure cannot be any of the following:
a before or after-rollup calculated measure, an externally rolled up measure, another category count
measure
an allocated measure, if the allocation occurs in the same dimension as the category count and
above the counted categories level
10-14

WORKING
WITH
MEASURES
Demo 2: Create a Calculated Measure

Purpose:
You want to include a calculated measure in the model to rationalize
expenses.
Components:
User ID:
admin
Password:
Education1!
Task 1. Create a new measure called Profit Margin.

1.
2.
3.
4.
5.
6.
Insert a new measure.

Hint: toolbar, Insert Measure (Ins)
Measure name: Profit Margin
Click the Type tab.
Click Calculated.
Profit Margin is a calculation defined by: Revenue minus the Product Cost.
Click Calculation.
Create the expression: "Revenue" - "Product cost".
Note: To see a definition of each component click Tips.
Click OK to accept the new measure.

10-15
COGNOS
7.
8.
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Format Profit Margin.

Hint: Format tab
Format: $#,##0
Decimal places: 2
Click OK.
The Profit Margin calculated measure is added to the Measures list.

1.
2.
Check the model and create the PowerCube.

Publish the PowerCube as Data Source and Package to Cognos Connection.

1.
2.
3.
4.
10-16

Username: admin
Package: Measures
Expand the Date folder, and then drag Date to the Rows drop zone.

WORKING
WITH
MEASURES
5.
Expand Measures and drag Revenue, Quantity, Product Cost, and Profit
Margin to the Columns drop zone.
6.
7.
Close Analysis Studio without saving.

Click Log off
Results:
You added the company standard for profit margin as a calculation
in the Measures list and viewed the result in Analysis Studio.

10-17
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Demo 3: Create and Calculate a Rollup Measure

Purpose:
The Director of Finance wants to report on the average cost, and the
Director of Sales and Marketing expects to see profit margin
expressed as a percentage. You will create an average measure for
the cost using a predefined rollup function, Average. You will then
create both a before and after Time State rollup and use the
appropriate calculated measure.
Components:
User ID:
admin
Password:
Education1!
Task 1. Create the Average Cost measure, and give it a

regular rollup as an average.
1.
2.
3.
4.
5.
10-18
Insert a new Measure.

Hint: toolbar, Insert Measure (Ins)
Measure name: Avg Cost.
Click the Type tab.
Under Column, click Add.
Set the Association role as Source.
Click More, and select Product cost, and then click OK.

WORKING
6.
7.
8.
WITH
MEASURES
Modify the Format.

Hint: Format tab
Format: $#,##0
Decimal places: 2
Click the Rollup tab.
In the Regular rollup list, click Average, and then click OK.
Task 2. Create the Profit Margin % (After Rollup) measure.

1.
2.
3.
4.
5.
6.
7.
8.

Measure name: Profit Margin % (After Rollup)
Click the Type tab, and then select Calculated.
Click Calculation.
("Revenue" - "Product cost") / "Revenue"
Click OK to close the expression editor.
Change the Format.
Format: 0%
Decimal places: 2
Select a rollup option for the Profit Margin % (After Rollup) measure.
Hint: Rollup tab
Regular timing: Default (After Rollup)
Click OK to add the calculated measure to the Measures list.

10-19
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Task 3. Create the Profit Margin % (Before Rollup) measure.

1.
2.
3.
4.
5.
6.
7.
8.
10-20

Measure name: Profit Margin % (Before Rollup)
Click the Type tab, and then select Calculated.
Click Calculation.
("Revenue" - "Product cost") / "Revenue"
Click OK to close the expression editor.
Change the Format.
Format: 0%
Decimal places: 2
Select a rollup option for the Profit Margin % (Before Rollup) measure.
Hint: Rollup tab
Regular timing: Before Rollup
The Measures list appears as shown below:

WORKING
WITH
MEASURES

1.
2.
3.
4.
5.
6.
7.
8.
Insert a new PowerCube called Calculated Rollup.

Right-click Calculated Rollup and click Create Selected PowerCube.
Right-click Calculated Rollup and then click Publish PowerCube as Data
Source and Package.
Maximize Cognos Connection and click Log on again.
Log on as admin, Education1!.
Package: Calculated Rollup
Expand Date, and drag Date to the rows.
Add Product line to columns.

10-21
COGNOS
9.
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Expand Measures and drag Revenue, Quantity, Product cost, Profit

Margin, Avg Cost, Profit Margin %(After Rollup), and Profit Margin
%(Before Rollup) to nest with rows.
Your report appears as shown below:
Examine the values for Profit Margin % (Before Rollup) and Profit Margin %
(After Rollup). A Profit margin (Before Rollup) of 229,500.00% for 2004 seems
unreasonable. A Profit margin (After Rollup) of 35.18% seems reasonable. This
is because of the different rollup techniques. The values in the cells for Profit
Margin % (After Rollup) are the result of calculating the profit margin based on
total values for Revenue and Product Cost for all years.
10. Close Analysis Studio, and then click Log Off.
Results:
You created a model that includes a measure that calculates the
average transaction cost by using a regular rollup based on Average.
You also created an alternative method of presenting Profit Margin
expressed as a percentage for the Sales department.
10-22

WORKING
WITH
MEASURES
Demo 4: Create a Measure with a Time State Rollup

Purpose:
For order and inventory purposes, your Administration team has to
view the maximum quantity sold over the last month in each of the
2004-2006 time periods. They will be using this information for
forecasting inventory levels.
Components:
User ID:
admin
Password:
Education1!
Task 1. Create a new measure and specify Rollup options.

1.
2.
3.
4.
Create a new measure.

Measure name: Maximum Quantity (Last Month)
This measure will have a regular rollup of Maximum and a Time State rollup of
Last Period.
Click the Type tab.
In the Column section, click Add.
Association role: Source
Column: Quantity
Click OK.

10-23
COGNOS
5.
6.
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Modify Rollup settings.

Hint: Rollup tab
Regular rollup: Maximum.
Time State rollup: Last period
The time state for a measure is its value at a specific time. You set the Degree of
detail property to the lowest level of detail; that is, the values at the bottom of
the hierarchical tree. The lowest degree of detail in the model is Month.
Click OK.
Task 2. Publish the model.

1.
2.
3.
Insert a new PowerCube called Measures(Time State).

Right-click Measures(Time State) and then click Create Selected
PowerCube.
Publish the PowerCube as a Data Source and Package to Cognos
Connection.

1.
2.
3.
4.
5.
10-24
Maximize Cognos Connection and log on as admin (Education1!).

Package: Measures(Time State)
Expand Date, and then expand Date.
Drag 2004, 2005, 2006 to the Rows drop zone.
Add Product line to the Columns drop zone.

WORKING
WITH
MEASURES
6.
Expand Measures, and then drag Maximum Quantity (Last Month) to the
Measures drop zone.
7.
Examine the Golf Equipment column and its value for 2006.
The cell takes the value 1586, the value of the largest quantity purchased in the
last period, ending Dec 2006.
Examine the Outdoor Protection column and its value for Dec 2004.
The cell takes the value 9319, the value of the largest quantity in the last month
of 2004. Analysis Studio reports the maximum value of the last month of all
children for this measure as a result of the Last Period Time State rollup option
selected earlier.
The summary row always has the same values as the last detail row when the
rows are from the time dimension.
The summary value (Product line column) for each row is not a sum of the
different product lines, but instead takes the maximum value of each row. All
dimensions (except for the time dimension) return a maximum value for all
children instead of adding up the values in those categories.
8.

10-25
COGNOS
9.
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Drill down on the intersection of 2006 and Golf Equipment.
10. Examine the 2006 summary row.

In this row, each cell takes the last period value in each column because the last
month of 2006 is also the last month of Q4.
11. Exit Analysis Studio without saving the analysis.
12. Click Log Off.
Leave the Transformer model open for the next demo.
Results:
Your Administration team can now report on and view the maximum
quantity sold over the last period, providing them with forecasting
data.
10-26

WORKING
WITH
MEASURES
Demo 5: Create a Category Count Measure

Purpose:
You want to see how many retailers bought products from a specific
product line.
Components:
User ID:
admin
Password:
Education1!
Task 1. Create the new category count measure for Retailer

Name.
1.
2.
3.
4.
5.
6.
7.
Set the Retailer Name as Unique.

Levels used in a category count must be unique.
Measure name: Retailer Count.
Click the Type tab.
Click Category Count.
In the Dimension box, click Retailer type.
In the Level box, click Retailer name.
Click the Rollup tab.

10-27
COGNOS
8.
9.
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
In the Activity measure box, ensure All Measures is selected.

Notice that you can select the measure with which to associate your category
count in case some measures are inappropriate.
Click OK to accept the new measure.
The Retailer Count measure will be processed and values added to it during
model creation.
Task 2. Publish a PowerCube.

1.
2.
3.
4.
5.
Check the model, and then click OK to accept the warning.

Insert a new PowerCube called Measures (Calculated).
Right-click Measures (Calculated) and click Create Selected PowerCube.
Publish the PowerCube as a Data Source and Package to Cognos Connection.

1.
2.
3.
4.
5.
10-28
In Cognos Connection, click Log on again.

Log on as admin (Education1!).
Package: Measures (Calculated)
Expand Date, and drag Date to the Rows drop zone.
Add Product line to the Columns drop zone.

WORKING
WITH
MEASURES
6.
Expand Measures, and then drag Retailer Count to the Measure drop zone.
7.
8.
Close Analysis Studio without saving the analysis.

Close the model without saving, and then leave Transformer open.
Results:
You can now see how many Retailers bought products from a
specific product line.

10-29
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Summary
discuss the purpose and uses of measures
describe regular and calculated measures
create calculations before or after rollups
Instructor Notes
Warehouse (analysis). This will "unclutter" public folders. You can also clean up the .mdc and log files
in C:\Edcognos\C88382.
10-30

WORKING
WITH
MEASURES
Workshop 1: Create and Calculate a Rollup Measure

Sales Managers in each region want to analyze the average unit cost of products for
each year. To do this:
create a new model called Sales Info based on a package data source: GO
Data Warehouse (query)
add Date, Product line, Product type, Product name, Region, Country, City
Order Method, Revenue, Unit cost, and Quantity
add Revenue, Unit cost, and Quantity to the measures list
create a new calculated measure called Average Unit Cost
view the result in Analysis Studio

10-31
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

Task
Where to Work
New Model wizard
Hints
Model name: Sales Info
package
Data source items: Date, Product
line, Product type, Product name,
Region, Country, City, Order
Method, Revenue, Unit cost,
Quantity.

dimensions.
3. Create the Average

Unit Cost measure.
Dimension Map
Date, Product line, Region, Order

method
Measures
Add Measures
Measures
Output scale =2
Source > Unit cost
Average (regular rollup)
Format = $0, 2 decimal places
4. Publish the
PowerCube directly
to Cognos
Connection.
Transformer
Create and publish cube using

current settings

Analysis Studio.
Analysis Studio
Blank Analysis/Sales Info package

Rows = Date
Columns = Products
Measures = Average Unit Cost
10-32

WORKING
WITH
MEASURES

After creating your model, it should appear as shown below:
After creating the report in Analysis Studio, the result should appear as seen below:

10-33
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

Components:
Transformer
Package:
User ID:
admin
Password:
Education1!

1.
2.
3.
10-34
In Transformer, create a new model:

Model name: Sales Info
Username: admin
Package: Public Folders > GO Data Warehouse (query)
Order Method > Order Method
Sales fact > Revenue, Unit cost, Quantity

WORKING
WITH
MEASURES

1.
2.
3.

Region: Region, Country, City
Order method: Order method
Add Revenue, Unit cost, and Quantity to the measures list.
Task 3. Create the Average Unit Cost measure.

1.
2.
3.
4.
5.
6.
7.

Measure name: Average Unit Cost
Set the Output scale to 2.
Click the Type tab, and specify a new Source Association using Unit cost.
Click OK.
Select a rollup option for the Average Unit Cost measure.
Hint: Rollup tab
Rollup: Average (regular rollup)
Change the Format.
Format: $0
Decimal places: 2

10-35
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

1.
2.
Check the model, generate the categories, and create the PowerCube.
Right-click the Sales Info PowerCube, and then click Publish PowerCube as

1.
2.
3.
4.
5.
6.
7.
8.
10-36

Package: Sales Info
Expand Date, and then drag Date to the Rows drop zone.
Expand Measures and drag Average Unit Cost to the Measure drop zone.
Close Analysis Studio without saving the report, and then click Log off.
Leave the model open for the next workshop.

WORKING
WITH
MEASURES
Workshop 2: Create a Measure with a Time State Rollup

You want to view the minimum quantity sold over the last month in each of the
2004-2006 time periods. This information will be used for forecasting inventory
levels.
Create a new measure called Minimum Quantity (Last Month). This measure
should have a regular rollup of Minimum and a Time State rollup of Last Period.
View the result in Analysis Studio.

10-37
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

Task
1. Create the
Minimum Quantity
(Last Month)
measure.
Where to Work
Hints
Measures
Minimum Quantity (Last Month)

Source Association = Quantity
Minimum regular rollup
Time state rollup = Last Period
2. Publish the
PowerCube directly
to Cognos
Connection.
Transformer

Analysis Studio.
Analysis Studio
Insert a new cube called Time state.

Publish using current settings.
Time state package
Rows: 2004, 2005, 2006
Columns: Product line
Measure: Minimum Quantity (Last
Month)
10-38

WORKING
WITH
MEASURES

The result should appear as shown below:

10-39
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

Components:
Transformer
Package:
User ID:
admin
Password:
Education1!
Task 1. Create the Minimum Quantity (Last Month) measure.

1.
2.
3.
4.
5.

Measure name: Minimum Quantity (Last Month)
Click the Type tab, and specify a new Source Association using Quantity.
Click OK.
Select a rollup option for the Minimum Quantity (Last Month) measure.
Hint: Rollup tab
Regular Rollup: Minimum
Time state rollup: Last period

1.
2.
3.
10-40
Check the model, generate the categories, and insert a new PowerCube called
Time state.
Right-click the Time state PowerCube, and then click Create selected
PowerCube.
Right-click the Time state PowerCube, and then click Publish PowerCube as

WORKING
WITH
MEASURES

1.
2.
3.
4.
5.
6.
7.
8.
9.

Package: Time state
Expand the Date folder, and then expand the Date hierarchy.
Drag 2004, 2005, and 2006 to the Rows drop zone.
Expand Measures, and then drag Minimum Quantity (Last Month) to the
Measures drop zone.
Close Analysis Studio without saving the changes, and then close Internet
Explorer.
Close Transformer without saving the model.
Instructor Notes
You can also replace the Rows with the entire Date hierarchy. Ask students why the 2007 row will be
blank. Answer: The data in 2007 ends in July.

10-41
COGNOS
10-42
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

11
Allocated Measures
Cognos 8 BI
Instructor Notes
User ID: admin
COGNOS
11-2
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

ALLOCATED
MEASURES
Objectives
allocate measures as a constant and by another

measure
Instructor Notes
If you intend to teach this module, students should be familiar with:
working with Measures
Set the default directories for opening cubes and saving reports to C:\Edcognos\C88382.

11-3
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Allocation
Allocation is a way to compensate for incomplete
data.
Data source
Dimension
A data source may not contain data for all levels of a

dimension, or the measure may not apply to a
dimension.
Transformer offers two methods of allocation:

Constant allocation: The value remains the same throughout all levels in the
dimension.
By Measure allocation: The measure value is allocated as a proportion of another
measure.
Instructor Notes
Slide: The Product line dimension has 2 levels that do not exist in the data source: Product type and
Product name. To roll up the Forecast measure from the data source to the lowest level in the Product
line dimension, you must allocate. By default, Transformer allocates Forecast as a constant.
Allocation distributes data, which is specified at a summary level of a dimension, to lower levels. For
example, actual sales revenue may be tracked daily, but sales revenue is forecast quarterly. You may
find allocation useful for distributing quarterly forecasts to the month and day levels.
11-4

ALLOCATED
MEASURES
Allocation - An Example
How do we assign the hydroelectric power expense in
this business?
Per cost center?
Per workstation?
Per employee?
Per square foot?
As a location constant?
Allocating measures involves distributing data from a specified summary level of a

dimension to its lower levels.
Allocation occurs only when the model contains multiple data sources. In a single data
source model, all measures are associated to all dimension structures found in the
model, and therefore, allocation is not a concern. This means that each measure can be
applied at the lowest level of each dimension.
Instructor Notes
To allocate you must have a model with two or more data sources, defined the measures in that model,
and a dimension map.
By default, when Transformer allocates a measure, the categories within a level inherit the allocation
type from the higher level. You cannot allocate a calculated measure. You can, however, allocate a
regular measure in proportion to a calculated measure.
11-5
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Measure Scope Dimension Map
Direct relationship to
the selected Measure
No association to the
selected Measure
Constant or By
Measure allocation is
applied
The Measures scope Dimension Map shows the distribution of a particular measure
over various levels in the Dimension Map. The Show Scope command, when used on a
measure, provides a color-coded Dimension Map, which:
highlights the relationship between the selected measure and the levels within a
dimension
displays the distribution of a measure in a model
Instructor Notes
Yellow - direct relationship exists: all of the required data for the roll up comes from the data source
that contains the measure.
Green - the measure has been allocated to the dimension or label.
White - no relationship exists between the measure and the dimensions or levels, and the categories in
these levels will have no values.
11-6

ALLOCATED
MEASURES
Allocate as a Constant Value

A constant allocation allows a measure value to
remain unchanged throughout the various levels in
the dimension.
Allocate a measure as a constant value when that
measure holds no relationship to the data structure.
Transformer, by default, automatically assigns a constant allocation for a measure that

contains no apparent association with any level in a dimension.
When you drill down from one level to the next, the constant allocated measure value
remains the same as when the allocation was set.
Instructor Notes
You can recognize an allocated measure in Transformer as a constant in a particular level when values
are not summarized in the summary rows or columns. The measure displays the same value at both
the summary and detail level.

11-7
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Demo 1: Allocate a Measure as a Constant

Purpose:
The Great Outdoors Company is planning to hire new staff. You
need to create an analysis that illustrates the relationship between
revenue, and the total number of Employees used to generate those
numbers.
Components:
User ID:
admin
Password:
Education1!
Task 1. Open a model.

1.
2.
11-8
Open Transformer.
Open a Model.
Location: C:\Edcognos\C88382\PPT-Allocated measures
Name: Demo 1_Start.pyj

ALLOCATED
MEASURES
Task 2. Declare Branch code unique.

1.
2.
3.
Right-click the Employee Count data source, and then click Show Scope.
The red highlighting indicates that Branch code cannot take its values from the
Employee Count data source. The Employee Count data source does not
contain the ancestral columns necessary for rollup. However, you know that
Branch code contains unique categories.
Set Branch code as Unique.
Close the Data Sources scope Dimension Map.

11-9
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Task 3. Add a measure to the model, and then review the

existing allocations.
1.
2.
3.
Drag EMP_COUNT from the Data Sources list to the Measures list.
In the Measures list, right-click EMP_COUNT, and then click Show Scope.
The Measures scope Dimension Map appears as shown below.
The green highlighting in the Measures scope Dimension Map indicates that the
measure EMP_COUNT is allocated to all levels in the Product line dimension.
By default, the measure is allocated as a constant.
The levels that remain white indicate that no values for EMP_COUNT will
appear in its categories because no relationship is established. Analyses will
show blank values for these categories.
In the Measures box, click Revenue.
The dark yellow highlighting indicates that Revenue is directly related to all
dimensions in the Dimension Map. This is because Revenue is contained in the
same data source as all the dimension levels, all product information, regional
information, and date information.
Instructor Notes
Setting Branch code as unique tells us that categories in the Branch code level are identified only by
their source values, without reference to their ancestors (City, Country and Region).
11-10

ALLOCATED
4.
MEASURES
In the Measures box, click Product cost.

The dark yellow highlighting indicates the direct relationship between Product
cost and the dimension levels.
Task 4. Review the allocations of Product Line.

1.
2.
3.
4.
5.
6.
7.
On the Measures scope Dimension Map, right-click the Product line

dimension label, and then click Properties.
Click the Allocation tab.
Notice that the Allocation type is Constant.
Click Cancel.
In the Date dimension, right-click the Year level, and then click Properties.
Notice the Allocation type is N/A.
Because the Date column exists in the same data source as EMP_COUNT,
they have a direct relationship. However, the Date column in the Employee
count data source contains information only at the Year level. Therefore, in
Analysis Studio, blank values will appear in the lower levels of the Date
dimension until you allocate EMP_COUNT to those levels. Blank values
appear in the analysis, but you can choose to display zero by setting the Missing
Value in the property sheet of every measure.
Click Cancel.
Close the Measures scope Dimension Map.

11-11
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

1.
2.
Check the model, click OK to accept the warning, and then create the
PowerCube.
Publish the PowerCube as a data source and package.

1.
2.
3.
4.

Username: admin
Open Analysis Studio and create a Blank Analysis.
Package: Allocate
Expand the Date folder, drag Date to Rows.
Expand Measures and drag Revenue, Quantity, Product cost, and
EMP_COUNT to Columns.
Notice the EMP_COUNT for 2004 (223).
11-12

ALLOCATED
5.
6.
MEASURES
Drill down on 2004.

Because EMP_COUNT has not been allocated beyond Years (its lowest degree
of detail), no values appear in the quarter level.
Close Analysis Studio without saving the report and click Log off.
Task 7. Allocate the EMP_COUNT measure to the Quarter and

Month levels.
1.
2.
5.
In the Measures list, right-click EMP_COUNT, and then click Show Scope.
In the Measures scope Dimension Map, right-click Year, and then click
Properties.
Under Allocation type, right-click N/A, and then click Constant.
Allocation must be set from the level above the level you want to allocate.
Click OK.
6.
The Quarter and Month levels are highlighted in green. This means that the
EMP_COUNT measure will remain constant at the Quarter and Month levels
of the DATE dimension; that is, they have the same value as the Year level.
3.
4.

11-13
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Task 8. View the results in Analysis Studio.

1.
2.
3.
4.
5.
6.
7.
8.
Insert a new PowerCube called Allocate (Constant).

Right-click Allocate (Constant) and click Create Selected PowerCube.
Maximize your browser and click Log on again.
Launch Analysis Studio, and create a Blank Analysis.
Package: Allocate (Constant)
Expand the Date folder, drag Date to the Rows.
Expand Measures and drag Revenue, Quantity, Product cost, and
EMP_COUNT to the Columns.
Notice the EMP_COUNT for 2004 (223).
Drill down on 2004.
Notice the new values allocated by EMP_COUNT at the Quarter level. All
categories in the Quarter level have a constant EMP_COUNT of 223.
11-14

ALLOCATED
MEASURES
9.
Drill down on 2004 Q 1.

All categories in the Month level also have a constant EMP_COUNT of 223.
The column total for EMP_COUNT indicates an allocated constant value
because the column has a total of 223 instead of a summary value.
10. Drag Product line to the Columns.
11. Drag EMP_COUNT to the Measures.
Notice that the data for the product lines are the same for all months (223).
12. Drill down on Personal Accessories.
The data has remained constant throughout the drill-down action because
EMP_COUNT is established as a constant measure throughout the levels of
the Product line dimension.
13. Close Analysis Studio without saving, and then click Log off.
Results:
The Great Outdoors Company can analyze the relationship between
revenue and the total number of employees used to generate that
revenue.

11-15
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Allocate as a Proportion of Another

Measure
Regions
Americas
$50,000 (50%)
Countries
France
$10,000
$10,000 (29%)
Employees
Central Europe
UK
$100,000 (100%)
$20,000 (100%)
$35,000 (35%)
$20,000 (57%)
$7,000
$3,990
Asia Pacific
$15,000 (15%)
$3,000
Cities
$2,030
Belgium
Birmingham
$15,000 (75%)
$2,993
London
$5,000 (25%)
$997
$5,000 (14%)
$980
Total Revenue $100,000

Total Bonus
$20,000
You can proportionally allocate measure values to subordinate categories by using

weighted values from another measure.
Instructor Notes
Slide: bonuses are allocated based on the revenue per Region, Country, and City.
If you set the allocation type to By Measure, Transformer opens the Select a Measure dialog box,
where you can allocate the measure value as a multidimensional proportion to descendant categories
by using values from another measure as a weighting factor. For example, an advertising budget is
given for each product line, and you want to view the corresponding budget values for each individual
product type. Allocating the advertising budget value based on the revenue of each product type
provides an estimate of the overall advertising budget spent on each corresponding product type.
11-16

ALLOCATED
MEASURES
Demo 2: Allocate a Measure as a Proportion

Purpose:
The Managing Director of the Great Outdoors Company wants to see
a report containing a forecast measure allocated to dimensions and
levels according to the percentage breakdown of Revenue.
Components:
User ID:
admin
Password:
Education1!
Task 1. Add a new data source, to the model.

1.
2.
3.
4.
5.
Insert a new data source.

Data source name: Forecast
Location: Public Folders > GO Data Warehouse (query) > Forecast
Query definition details: All Query1.0 items
Expand the Forecast data source and query.
Double-click the Forecast query.
Click the General tab.
Clear the Sets the current period check box, and then click OK.

11-17
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Task 2. Relate Current Year in the Forecast data source to

the GO Data Warehouse (query) data source.
1.
Modify the Current Year column properties.
General tab:
Column name: Date
Data class: Date
Time tab:
Date input format: Y
Degree of detail: Year
Task 3. Change the allocation of the Product line dimension

to By Measure.
1.
2.
11-18
Drag Forecast revenue to the Measures list.

Change the format to $#,##0.

ALLOCATED
3.
4.
5.
6.
7.
MEASURES
In the Measures list, right-click Forecast revenue, and then click Show Scope.
The green highlighting indicates that Forecast revenue has been allocated to the
entire Product line dimension. This is because there is no association to Product
line information in the Forecast data source where Forecast revenue originates.
Therefore, by default, a constant allocation is assigned to the entire Product line
dimension.
In the Measures scope Dimension Map, right-click the Product line dimension
label, and then click Properties.
For Forecast revenue, change the Allocation type to By Measure.
Click Revenue, and then click OK twice.
This action informs Transformer to allocate the Forecast revenue measure to
the Product line dimension by a proportion of the Revenue measure.

11-19
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Task 4. Change the allocation of the Year level to By Measure.

1.
2.
3.
4.
In the Measures scope Dimension Map, right-click the Year level, and then
click Properties.
For Forecast revenue, change the Allocation type to By Measure.
Click Revenue, and then click OK twice.
You allocated the Forecast revenue measure, based on Revenue, to the Quarter
and Month levels. The green highlighting indicates this.
5.
Task 5. View the results in Analysis Studio.

1.
2.
3.
11-20
Insert a PowerCube called Allocate (By Measure).

Right-click Allocate (By Measure) and click Create Selected PowerCube.

ALLOCATED
MEASURES
4.
Maximize your browser and click Log on again.

5. Launch Analysis Studio and create a Blank Analysis.
Package: Allocate (By Measure)
6. Expand the Date folder, then expand Date and drag 2006 and 2007 to
Columns.
7. Expand Measures and drag Revenue and Forecast revenue to Rows.
8. Right-click Forecast revenue, point to Calculate, and click % of Total
(Forecast revenue).
This particular view demonstrates the allocation of the FORECAST measure as
a proportion of the REVENUE measure after you drill down.
9. Drill down on 2006.
Quarters are allocated Forecast revenue as a proportion of Revenue.
10. Replace the columns with Product line.
11. Drill down on Personal Accessories.
Product types are allocated to Forecast revenue as a proportion of Revenue.
12. Close Analysis Studio and Transformer without saving.
Results:
The Managing Director now has a report containing a Forecast
Revenue measure allocated to dimensions and levels according to
the percentage breakdown of Revenue.

11-21
COGNOS
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)
Do Not Allocate
Disable automatic allocation when:
a default allocation is inappropriate
you want to allocate as a constant value

throughout some, but not all, of the dimension
you do not want the measure values to appear in

your Analysis
When you disable allocation, Transformer creates data points with missing values,
which:
are displayed as blank values, by default
can be displayed as "na", depending on the display options selected
If allocation does not provide meaningful representation in a dimension level, use the
Do Not Allocate option.
Instructor Notes
Allocating bonuses to all Staff based on revenue may not work if half of your employees are part-time
and do not qualify for bonuses. You would then set the Do Not Allocate option for the Staff levels.
Depending on the measure setup, the Do Not Allocate option shows either zeros as default or N/A. N/A
can be used so that missing items are not misinterpreted as zero values. This option is defined from
the Missing value box on the General tab of the Measure property sheet.
11-22

ALLOCATED
MEASURES
Summary
allocate measures as a constant and by another

measure
Instructor Notes
from C:\Edcognos\C88382.

11-23
COGNOS
11-24
BI
TRANSFORMER:
DESIGNING
OLAP
MODELS
(VERSION
8.3)

W W W. C O G N O S . C O M

Cognos 8 BI Transformer Designing OLAP Models

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cognos 8 BI Transformer Designing OLAP Models

Uploaded by

Copyright:

Available Formats

Cognos Training

Cognos 8 BI Transformer: Designing OLAP

Copyright 2008 Cognos ULC (formerly Cognos

Portions of Cognos(R) software products are protected by

Part Number: 60556

While every attempt has been made to ensure that the

2008, Cognos ULC (formerly Cognos Incorporated)

2008, Cognos ULC (formerly Cognos Incorporated)

ADD DATA SOURCES ................................................................................... SI-25

2008, Cognos ULC (formerly Cognos Incorporated)

THE TRANSFORMER DEVELOPMENT PROCESS ...............................3-1

DATA SOURCES IN TRANSFORMER.......................................................4-1

2008, Cognos ULC (formerly Cognos Incorporated)

2008, Cognos ULC (formerly Cognos Incorporated)

DEMO 2: CREATE A TIME DIMENSION USING THE DATE WIZARD AND

2008, Cognos ULC (formerly Cognos Incorporated)

USE MULTIPLE DATA SOURCES..............................................................8-1

2008, Cognos ULC (formerly Cognos Incorporated)

WORKING WITH MEASURES..................................................................10-1

2008, Cognos ULC (formerly Cognos Incorporated)

2008, Cognos ULC (formerly Cognos Incorporated)

DEMO 2: CREATE AN ORPHANAGE (INSTRUCTOR ONLY) ............................14-17

2008, Cognos ULC (formerly Cognos Incorporated)

EXAMINE COGNOS 8 SECURITY............................................................16-1

2008, Cognos ULC (formerly Cognos Incorporated)

OPTIMIZING POWERCUBES ...................................................................18-1

2008, Cognos ULC (formerly Cognos Incorporated)

PARTITION A POWERCUBE ....................................................................19-1

2008, Cognos ULC (formerly Cognos Incorporated)

DEMO 3: OVERWRITE A PUBLISHED POWERCUBE .......................................20-23

2008, Cognos ULC (formerly Cognos Incorporated)

IDENTIFY COMMON DATA STRUCTURES........................................... B-1

2008, Cognos ULC (formerly Cognos Incorporated)

2008, Cognos ULC (formerly Cognos Incorporated)

Create alternate hierarchies within a dimension

2008, Cognos ULC (formerly Cognos Incorporated)

Important Course Changes

2008, Cognos ULC (formerly Cognos Incorporated)

Module 1: Overview of Cognos 8 BI

2008, Cognos ULC (formerly Cognos Incorporated)

Module 11: Allocated Measures

2008, Cognos ULC (formerly Cognos Incorporated)

Module 20: Maintain Models and PowerCubes

This module addresses data source, model, and cube updates. It

Module 21: Model for Drill-Through

2008, Cognos ULC (formerly Cognos Incorporated)

discuss Cognos 8 and

discuss the basics of OLAP

2008, Cognos ULC (formerly Cognos Incorporated)

The Transformer Development Process

describe the purpose of a

match business requirements

Data Sources in Transformer

discuss the types of data

2008, Cognos ULC (formerly Cognos Incorporated)

create model structures and

modify property sheets

confirm the data source origin

modify the model using the

verify the model and create a

publish as a data source and

The Time Dimension

discuss the purpose of a time

review properties of a time