Before using this information and the product it supports, read the information in “Notices” on page 377.
Product Information
This document applies to IBM Cognos Business Intelligence Version 10.1.1 and may also apply to subsequent
releases. To check for newer versions of this document, visit the IBM Cognos Information Centers
(http://publib.boulder.ibm.com/infocenter/cogic/v1r0m0/index.jsp).
This document is intended for use with IBM®Cognos®Transformer, the OLAP
modeling component delivered with IBM Cognos Business Intelligence.
The IBM Cognos Transformer User Guide describes PowerCube modeling procedures
and concepts, product functionality, and related terminology. It includes reference
information that supplements the task- and process-oriented topics, as well as
troubleshooting tips and detailed help for the more commonly encountered error
messages.
You can use this document to help you model and build PowerCubes with the
Cognos Transformer user interface, or to perform production-related tasks from the
Windows, UNIX, or Linux command line.
For information about creating automation scripts using Model Definition
Language (MDL), see the Cognos Transformer IBM Cognos Transformer DeveloperGuide.
For information about creating automation scripts using OLE automation, see the
IBM Cognos Transformer Automation Guide.
Audience
This information is for new IBM Cognos Transformer users and IBM Cognos Series
7 cube modelers who are seeking guidance as they migrate their PowerCubes and
related applications to the IBM Cognos environment. Advanced database
administration (DBA) or data modeling skills are not required. Business-relevant
examples, samples, and code examples are supplied in context.
Finding information
To find IBM Cognos product documentation on the web, including all translated
documentation, access one of the IBM Cognos Information Centers. Release Notes
are published directly to Information Centers, and include links to the latest
technotes and APARs.
You can also read PDF versions of the product release notes and installation guides
directly from IBM Cognos product disks.
Accessibility features
This product does not currently support accessibility features that help users with
a physical disability, such as restricted mobility or limited vision, to use this
product.
Forward-looking statements
This documentation describes the current functionality of the product. References
to items that are not currently available may be included. No implication of any
future availability should be inferred. Any such references are not a commitment,
promise, or legal obligation to deliver any material, code, or functionality. The
development, release, and timing of features or functionality remain at the sole
discretion of IBM.
Samples disclaimer
The Great Outdoors Company, GO Sales, any variation of the Great Outdoors
name, and Planning Sample depict fictitious business operations with sample data
used to develop sample applications for IBM and IBM customers. These fictitious
records include sample data for sales transactions, product distribution, finance,
and human resources. Any resemblance to actual names, addresses, contact
numbers, or transaction values is coincidental. Other sample files may contain
fictional data manually or machine generated, factual data compiled from
academic or public sources, or data used with permission of the copyright holder,
for use as sample data to develop sample applications. Product names referenced
may be the trademarks of their respective owners. Unauthorized duplication is
prohibited.
xivIBM Cognos Transformer Version 10.1.1: User Guide
Chapter 1. What's New?
This chapter contains a list of new and removed features for this release. It also
contains a cumulative list of similar information for previous releases. Knowing
this information will help you plan your upgrade and application deployment
strategies and the training requirements for your users.
For information about upgrading, see the IBM Cognos Business IntelligenceInstallation and Configuration Guide.
For an overview of new features for this release, see the IBM Cognos BusinessIntelligence New Features Guide.
For changes to previous versions, see “New Features in Version 10.1.0”
To review an up-to-date list of environments supported by IBM Cognos products,
such as operating systems, patches, browsers, Web servers, directory servers,
database servers, and application servers, visit the IBM Cognos Customer Center
http://www.ibm.com/software/data/cognos/customercenter.
New Features in Version 10.1.1
There are no new features in this release of IBM Cognos Transformer.
New Features in Version 10.1.0
These are the new features in this release of IBM Cognos Transformer.
Publishing Cube Groups
You can now publish all or selected PowerCubes in a cube group. The data source
connections and packages are automatically created or updated in IBM Cognos
Connection for all cubes in the group.
This solution does not change the way regular PowerCubes and time-based
partitioned cubes are published. For more information, see “Publishing
PowerCubes” on page 162.
Deprecated Features in Version 10.1.0
There are no deprecated features in this version.
Removed Features in Version 10.1.0
The following features are removed in version 10.1.0.
PowerCube Connection (PCConn) Utility
This utility is no longer supported by IBM Cognos Transformer. It was replaced by
the copy and activate functionality.
For more information, see “Updating Published PowerCubes and PowerCube
Connections” on page 186.
Framework Manager IQDs, or externalized queries, are no longer supported as
data sources in Cognos Transformer. Instead, you can use IBM Cognos packages
and reports as data sources.
For more information, see “IBM Cognos Package or Report” on page 14.
2IBM Cognos Transformer Version 10.1.1: User Guide
Chapter 2. Planning Your Model
IBM Cognos Transformer is a data modeling tool designed for use with IBM
Cognos 8 version 8.3 and subsequent releases.
You use this component to create a model, a business presentation of the
information in one or more data sources. After you choose a supported product
locale (language), add dimensional metadata, specify the measures (performance
indicators), and apply custom views, you can create PowerCubes based on this
model. You can deploy these cubes to support OLAP reporting and analysis.
This section provides a high-level overview of the modeling and planning process
to meet the OLAP needs of your users, as well as information about how to
upgrade an IBM Cognos Series 7 Transformer model.
The documented workflow follows a logical sequence, beginning with analyzing
your requirements and building a prototype model. If you have already completed
this planning stage, you can proceed to the sections of this document that deal
with data sources (Chapter 3), dimensions (Chapter 4), and measures (Chapter 5).
Dimensional Modeling Workflow
IBM Cognos Transformer is a proven and relatively simple tool for modeling
dimensional hierarchies and levels for PowerCubes.
After you relate the dimensions to your business performance indicators, you can
create powerful, secure cubes to be used for reporting and drill-through analysis in
the IBM Cognos studios.
v Carefully analyze your users' OLAP reporting requirements.
v If you have not already done so, build a prototype model.
v Choose your transactional and structural data sources and import the facts
(measures) and metadata (dimensions).
v Map your metadata into dimensions, and your facts into measures.
v Verify the model and resolve any ambiguities.
v Organize the data in your model into customized dimension views or cube
groups.
v Apply security and create custom views to control access to sensitive
information.
v Create and publish PowerCubes to IBM Cognos Connection.
v Manage and maintain your models, cubes, and reports for optimal effectiveness.
Troubleshooting tips are provided in this document and in the Administration and
Security Guide. This document also provides an overview of the functions
supported by Cognos Transformer, and how they may be used to create calculated
expressions. For more information, see “Cognos Transformer Functions” on page
99.
For information about scripting, see the Cognos Transformer Developer Guide and
the Cognos Transformer Automation Guide.
To ensure that you develop an effective business intelligence model, we
recommend that you begin by carefully analyzing your users, the OLAP reports
they require, and your source data.
Use the following questions to analyze your users' OLAP reporting needs:
v What reports do users currently use? Which reports do they use most
frequently? Which reports do they use only rarely?
v Does each group require different reports? Are there some reports that are
required by all user groups?
v Do users need higher-level (summary) reports, detailed drill-through reports, or
both?
v How frequently are the measures in the report updated? How frequently do the
reports themselves change? Does the frequency vary from group to group?
v How often are reports required? Can you trade off frequency to ensure
accuracy? For example, if your users ask for monthly reports and the data
source is refreshed weekly, the data will always be current. However, if your
users want daily reports, the data will only be up to date on the first day of the
weekly cycle.
Analyze your source data, using questions such as the following:
v Does the data come from one source or many? What format is it in: flat files,
spreadsheets, or databases? Does it need to be converted to a supported data
source type before it is imported?
v Can you optimize existing queries by building new Cognos Transformer queries
using the metadata modeled in IBM Cognos packages or reports?
v How many records are there? By how much do you expect the volume of data
to increase?
v How much of the data is static and how much changes gradually over time?
Can you create different data sources for static and non-static data to support
incremental updates (an option that shortens cube creation time by appending
new data to a cube instead of recreating it)?
v How much data preparation is required?
Ensure that the source values that feed the categories are unique and, if feasible,
that you aggregate or otherwise preprocess your data before importing it. For
more information, see “Preprocessing Your Data.”
v Are linked measures from different data sources updated at the same time?
v Must you create additional data sources to accurately model your organization?
When you have answered these questions, you are ready to begin preparing your
source data for import and designing your prototype.
Preprocessing Your Data
Presort, clean, or consolidate your data to maximize reporting flexibility and
performance.
Preprocess data to achieve the following benefits:
v Presorted records are processed more quickly in Cognos Transformer.
v When you streamline your source data to contain only the information needed
for the model, read times are faster in Cognos Transformer.
4IBM Cognos Transformer Version 10.1.1: User Guide
v You can use Cognos Transformer to presummarize the data when your users do
not require access to all the details in the source.
For example, if your organization processes 50,000 transactions daily, and you
create the cube weekly, you can summarize the transactions at the weekly level
before Cognos Transformer begins processing. This will greatly speed up cube
creation.
v Consolidation, combining records with identical non-measure values, reduces the
size of the cube and improves performance in your reporting application.
Consolidation is enabled by default in Cognos Transformer. Evaluate your data
to see if it can be further consolidated by using the Duplicates rollup or
Regular rollup features of Cognos Transformer.
For consolidation purposes, non-measure values are considered identical if they
meet any of the following criteria for the particular rollup:
– The source data contains transactions with identical non-measure values.
For example, two sales of the same product are made to the same customer
on the same day, but the colors differ. If colors are omitted from a dimension
view using the Suppress or Summarize command on the Diagram menu, the
sales records will have identical non-measure values.
– Records become identical when a dimension is omitted from the cube.
For example, two sales of the same product are made at different stores on
the same day. If the Stores dimension is removed from the model, these sales
records will have identical non-measure values.
– Records become identical because of the Degree of detail setting on the Time
tab of the Column property sheet.
For example, if the Degree of detail is set to Month for a column associated
with a time dimension that includes week and day values, Cognos
Transformer ignores the week and day values in the source transactions when
consolidating records.
v For queries based on relational packages, enabling the Auto summarize feature
on the General tab of the Data Source property sheet also helps reduce the
number of rows that Cognos Transformer retrieves from the source data, further
improving cube build performance.
Separate Your Structural and Transactional Data
Processing time improves when Cognos Transformer can query your structural and
transactional information separately. You must identify which data sources contain
purely structural information, which contain transactional information (measure
values or facts), and which contain a combination of the two.
When processing queries to create a PowerCube, Cognos Transformer orders the
queries, first reading the structural queries and then reading the transactional
queries.
Ideally, you should define each dimension or drill-down path with a separate
structural data source, and then add one or more transactional data sources to
provide the measures for those dimensions. This restructuring exercise helps to
partially normalize your data, speeding up both the category generation and cube
creation stages.
The best approach is to have unique levels near the bottom of the dimensions, and
to have the transactional queries link to the dimensions using those levels. This is
basically the star schema or snowflake method of creating dimensions in a
relational database. This type of design promotes faster processing because each
Chapter 2. Planning Your Model5
transaction record has fewer business keys to process when identifying the
category with which the measure values are associated.
Define any transactional data sources that change frequently so that they contain a
small, concise record set, with the minimum amount of information needed to
update the data in your PowerCubes. Whenever possible, save your model with
generated category structures, to eliminate the redundant processing required to
continually rebuild them. Similarly, if your model contains long descriptions,
generate cubes from a model that is already populated with the categories
associated with those descriptions.
For more information, see “Control When the Source Data Is Read” on page 46.
Additional Data Modeling Tips
Enhance your model design by analyzing the data flow, resolving uniqueness
issues and data dictionary terms, building flexibility into your plan, and reducing
the Cognos Transformer processing load.
Consider building the following steps into your process:
v Analyze the data flow from the point at which your data is generated until the
data is input into Cognos Transformer. Determine if the data can be streamlined
or rationalized at any point, perhaps by creating a data warehouse, a series of
data marts, or a data-extract process to reorganize it.
v Resolve uniqueness issues and data dictionary terms before you merge two sets
of data into one model. Ensure data integrity by checking your column joins;
outer joins or table aliases may be required. Remember that Cognos Transformer
is not a relational database tool, and cannot perform joins between the columns
of different data sources. If you need to set up database joins, use a modeling
tool such as Framework Manager to create the joins, and then publish the
Framework Manager package for use in Cognos Transformer.
v Wherever possible, build flexibility into your plan. Use a different source file for
each aspect of your business, and organize the data sources in your model so
that each data source supplies the data for a different dimension. That way, you
can add more information into your cube as your business evolves, even if the
data comes from different software applications, platforms, departments, or
locations.
v Improve performance by continually striving to reduce the Cognos Transformer
processing load.
Building a Prototype
To field-test the accuracy of your analysis, build an initial model or prototype that
reflects the needs of the key decision makers in your company.
Base your prototype on an existing set of frequently used, stable OLAP reports,
and use the following checklist:
Procedure
1. Identify Measures
Measures are the numbers you use to gauge your organization's performance.
You should choose the critical success factors in your business as your
measures. Examples of typical measures include sales revenues, profit margins,
and response times.
6IBM Cognos Transformer Version 10.1.1: User Guide
If you have multiple data sources, you must relate the dimensions and levels of
your model to the data source that contains the columns to be used for each
measure.
Your model is more effective if your measures are applicable to more than one
dimension. For example, if your dimensions are products, locations, and
customers, your measures should bridge these dimensions.
2. Specify a Time Dimension
To ensure that your users can make period-to-period comparisons and visualize
trends over time, choose a time dimension that reflects and synchronizes
accounting periods and reporting schedules.
In most cases, your requirements are met by models based on the calendar or
fiscal year. Month, Quarter, and Year categories can be supplemented by
relative time categories automatically generated by Cognos Transformer, such
as YTD Growth, the percent-growth year-over-year.
If your organization uses particular time periods, such as lunar weeks and
months, or three 8-hour shifts per day, Cognos Transformer supports the
definition of custom time dimensions. Even if your query objects originate in
Framework Manager, you should import the necessary time-related items into
Cognos Transformer, and then define your time dimensions there.
3. Select the Data to be Modeled
You begin by identifying the data sources that contain the data for the model
you want to create.
Suppose that information about your customers is stored in a Customers table
and information about your products is stored in a Products table. Related
tables called Customer_Details and Product_Details provide additional
information about customers and products. Order information is stored in two
tables called Orders and Order_Details.
In keeping with good design practice, you decide to set up the Customers,
Customer_Details, Product, and Product_Details tables as structural data
sources, to provide the information that Cognos Transformer uses to build the
Customers and Products dimensions in your model.
The information about transactions is stored in the Orders and Order_Details
tables. For efficiency, you decide to combine the information in these tables into
a single data source called Order_Info.
The Order_Info data source contains the following information, all of which
you use to associate sales with particular customers and products:
v The order dates generate categories for the time dimension.
v Data about customers and sales representatives generates the header
information.
v The product, order quantity, and sales amount for each line item in an order
provide the sales measures.
v The cost of the order and discounts applied to it provide supplementary fact
data.
Example - Your Prototype Sales Model, on Paper
You can create an initial dimension map on paper, to make sure you have
identified all of the dimensions, levels, and categories needed in your PowerCube.
The measures to be associated with this dimensional hierarchy are Sales, Order
Qty, Cost, and Discount.
You map the dimensions of your prototype as follows:
Chapter 2. Planning Your Model7
Order dateProductsLocations
YearProduct GroupRegion
QuarterProduct ClassOffice
MonthProduct NameSales Rep
Refining Your Model
Based on your paper prototype, you create the Dimension Map for your new
model in Cognos Transformer. You begin with one data source. You can enhance
the business value of your model later, by adding more sources or manipulating
the data derived from the existing data sources.
Suppose you are initially lacking information about the staffing levels in each
branch. You can either add another data source to provide this information or use
the Category Count feature of Cognos Transformer to provide this detail. The
resulting cube and OLAP reports can then deliver value-added information about
the average sales per employee.
Models can contain any combination of the following:
v regular measures, or the numeric fact data found in a transaction file
v calculated measures, or numeric data calculated from other measures,
mathematical operators, and numeric constants
v category counts, or the number of categories in a unique level for which the
measure values are not zero or missing
v calculated categories, whereby calculated expressions apply directly to any
measure
v calculated columns, whereby new data is based on values calculated from other
columns, functions, constants, and calculated columns
Product No
Use the following checklist to help refine your model:
v Add special categories to enable quicker data access.
Group your data based on attributes that may be contributing to the success of
your enterprise, such as product color or customer income.
v Add drill-down paths to provide more detail.
A dimension normally consists of a single drill-down path with one or more
drill-down levels, representing the hierarchical organization of the information.
However, you can further subdivide your dimensions, so your report users can
analyze their data at different levels of detail.
There are no restrictions on the number of levels and drill-down paths that you
use in a dimension. However, all alternate drill-down paths must converge at a
common unique level and, for performance reasons, it is best to keep a 1:10 ratio
or less between the categories in each level.
For information on drill through using categories from alternate drill paths, see
the Administration and Security Guide.
v Allocate measures to other levels or dimensions.
If your model uses multiple data sources, consider allocating measures to levels
or dimensions with which they are not normally associated. Allocation can
provide you with new insights into your data. For example, you can associate
resource-related data to financial data.
8IBM Cognos Transformer Version 10.1.1: User Guide
You can allocate measures over entire dimensions, over levels within an
individual dimension, or over categories within levels. When allocating
measures, use measures that come directly from your source data rather than
calculated measures, and avoid overloading your model with superfluous detail.
v Consider combining information from another functional area, such as materials
and resource planning or performance quality, with the finance or customer
profitability data already in your business model.
Begin by listing the data columns and determining if there are any gaps,
particularly in the area of cost of materials, or indicators of quality.
Next, map the new dimensions, checking that the time periods are consistent
with each other and with your financial statements. Ensure that revenue and
expense values map to those in the financial statements.
Finally, verify the relationships that exist between the various measures. If these
are not one-to-one relationships, confirm how each relates to your common
dimensions.
Example - Adding Customer Service Data to Refine Your Model
Suppose your initial model includes the following dimensional hierarchy, as well
as values for Inventory Status and Turnover Ranges.
You have data for an extensive list of measures: Sales, Order Qty, Material Cost per
Unit, Discount, Percent Gross Margin, Carrying Cost per Unit, Percent Material
Cost per Sale, Percent Carrying Cost per Sale, Sales per Customer, Percent Profit
per Segment, and Inventory Turnover.
You decide you want to monitor customer service, so you expand your model to
include indicators of service quality. The new dimensions and categories might be
encoded Reasons for Dissatisfaction or Causes of Poor Quality Service.
You must ensure that your source data provides the required measures, such as the
number of complaints, returns, and claims, or the dollar value of returns and
claims.
You can complete your model by incorporating response times, labor costs, time
lost to service claims, rework hours, scrap costs, or any other factor that
significantly affects service quality.
Diagnose and Resolve Any Design Problems
You can use any or all of the following tools and techniques to diagnose and
resolve problems in your model design.
Show Scope
To see how your measures and levels are associated with their corresponding data
sources by allocation, direct association or indirect association, use the Show Scope
command on the Edit menu.
Show Count
To verify that you have maintained a 1:10 ratio or less between the categories in
each level, use the Show Counts command on the Edit menu. Lower ratios allow
for efficient partitioning and faster cube creation times in Cognos Transformer, as
well as easier data exploration in your reporting component.
Chapter 2. Planning Your Model9
Show Reference
To confirm the origin of every data source column associated with your
Dimension Map and see how each is used, use the Show Reference command on
the Tools menu.
Generate Categories
To confirm how the categories in a specific data source relate to your model, use
the Generate Categories command on the Run menu, with the selected data
source. To prevent the generation of categories in specific levels or entire
dimensions, select the Prohibit automatic creation of new categories check box on
the General tab of the Level or Dimension property sheets.
Create Selected Cubes
During the prototyping stage, you may want to create only certain cubes. You can
enable or disable cube creation in one of following ways:
v Change the Cube creation option on the Processing tab of the PowerCube or
Cube Group property sheet.
v Use the Create Selected PowerCube command on the Run menu.
v Use the Model Definition Language (MDL) function CreateFromCubes. For more
information, see the Cognos Transformer Developer Guide.
Check Cube Build Status
When you build a cube in Cognos Transformer, you can check the status of the
cube build at any time without opening it by using the PowerCube Status
command on the Tools menu. You can check the status of all the cubes that are
defined for a model at the same time. If your model has more than one cube, you
can apply a filter to monitor the status of cubes enabled for creation, disabled
cubes, or both.
You can also filter the cube build status settings by selectively requesting one of
the following:
vAny status, to list all cubes associated with the model, regardless of their status.
vErrors, to list cubes that were not created because they are not valid, or failed.
vWarnings, to list all cubes for which warnings were detected during a previous
create.
vSuccessful, to list all cubes created without errors or warnings, having a status
of OK.
Consult the Error Message and Troubleshooting Help
In addition to the troubleshooting topics in the User Guide, help is available from
Help buttons in some error messages to help you resolve any model design
problems.
Review the Resulting Reports With Your Users
After you generate a few reports from your prototype, ask for feedback from
representative users by posing open-ended questions. If you are the IT specialist,
involve an experienced business analyst in the process.
10IBM Cognos Transformer Version 10.1.1: User Guide
Together, try to develop and maintain a list of follow-up questions, such as the
following:
v Does each dimension level generate valid data, with measures that are properly
associated or coordinated, for every data source?
Try to spot measures that do not roll up as expected, or that are not additive in
every dimension.
v Are ranges or qualitative values coded realistically? Are the values for key
performance indicators consistent, or is the integrity of the underlying data
suspect?
In some cases, you may need to add other measures that substitute average
figures, or industry standards, for unavailable or non-continuous values.
v Is the data at some of the lower drill-down levels too sparse to be useful?
Should the model be redesigned, or should drill-through targets be added?
Consider expressing some values as ranges rather than absolutes, to create
useful groupings such as responsiveness or rates of return, for example, or to
hide sensitive details, such as salaries.
v Could the data flowing from different databases, models, and reports be better
coordinated, perhaps by using normalized measures, to ensure that computer
resources are not overburdened?
v Has anyone developed a calculated column or exception dimension that could
be added to the standard reports for the benefit of all?
If you maintain regular contact with your report users, you can incorporate their
feedback into your model enhancements. If you change your model and cubes, use
the label and description fields for each dimension, level, and measure, so that
reports created from your model are clear and intuitive.
Upgrade an IBM Cognos Series 7 Model
To upgrade models created in earlier versions of Cognos Transformer, you must
save them in the Model Definition Language (MDL) format before you can import
them into Cognos Transformer version 8.x and later. This ensures that equivalent
definitions are created for all model objects. You can upgrade models from IBM
Cognos Transformer, versions 7.x.
You can open an IBM Cognos Series 7 model with secured cubes in Cognos
Transformer, and convert the IBM Cognos Series 7 user class views to IBM Cognos
custom views. You can then choose the authentication provider you want to use
with the custom views. For more information, see Chapter 7, “Adding Security,”
on page 147.
During the transition from a Series 7 namespace to an alternate security provider,
you can use the PowerCube property All applicable namespaces to associate all
applicable namespaces during migration testing. When you associate all the
applicable namespaces to the cube, you can ensure that the group, role, or user
dimensional filtering is consistent with that which had been applied for the IBM
Cognos Series 7 user class. This option is supported only for migration testing, and
cannot be used to deploy cubes in production environments.
You can change the data source association for IBM Cognos Series 7 .iqd files to an
IBM Cognos package or report to take advantage of the enhancements available
when using IBM Cognos data sources. You change the association after the
updated model is saved in Cognos Transformer 8.x. For more information, see
“Change a Data Source Type” on page 33.
Chapter 2. Planning Your Model11
When importing .mdl files from earlier versions, some features may not convert
correctly, such as legacy data that contains special characters, spaces, and quotation
marks. For more information, see the migration documentation delivered with
your version of the product.
Before you begin
Tip: If you plan to upgrade, ensure you save all your models as .mdl files before
you attempt to upgrade them.
Procedure
1. Open the model in the earlier version of Cognos Transformer and, from the
File menu, click Save As.
2. In the Save as Type box, click Exported Model Files (*.mdl).
Tip: By default, Cognos Transformer saves models in the My
Documents/Transformer/Models directory. You can set the default location to
which Cognos Transformer saves models by changing the Models directory
setting on the Directories tab of the Preferences property sheet.
3. Open your new .mdl file in the current version of Cognos Transformer, make
any required changes to the model design, and save it, again selecting the .mdl
format.
Tip: If your IBM Cognos Series 7 model includes security, you will receive a
message when you open the model in Cognos Transformer version 8.x and
later indicating that you must choose how to manage the security during the
upgrade process. For more information, see “Upgrade an IBM Cognos Series 7
Secured PowerCube” on page 158.
When you are ready to use the model in your production environment, you
may want to save it as a .py?-format file.
Models that are created using Cognos Transformer version 8.x and later (.mdl
and .pyj files) are not backward compatible with Cognos Transformer versions
7.x. As a result, we strongly recommend that you maintain the .mdl file for the
Cognos Transformer 7.x model for a period of time following an upgrade.
12IBM Cognos Transformer Version 10.1.1: User Guide
Chapter 3. Data Sources for Your Model
Models contain definitions of dimensions, levels, and measures. They also contain
features such as calculated measures, dimension views, or custom views that you
add to the basic PowerCube definition to meet your particular business intelligence
needs.
By querying the data in the specified sources, you create the multidimensional
PowerCubes or cube groups required by users of the IBM Cognos Business
Intelligence components, such as Analysis Studio.
Data sources can be one of the following:
v Structural (dimensional)
Contain the columns that define the model structure, such as the categories in
each dimension. Structural sources usually contain many columns and few rows.
v Transactional (fact)
Contain the columns for the measures to be tracked. They usually contain many
rows and few columns, typically one for each dimension and one for each
measure.
v Mixed
Contain the columns that define the model structure and the columns that
contain the measures to be tracked, using the same data source.
Techniques for Designing Data Sources
When setting up the data sources for your model, you should take into
consideration three principles.
These three principles are as follows:
v Where possible, design your data so that the structural information for each
dimension is provided by one source.
v Ensure that each data source contains enough information to generate the
categories for a dimension without database joins. If you must use database
joins, join queries from separate database tables using tools such as Framework
Manager, before you import the data.
v In addition to database security, be aware that different releases of Cognos
Transformer offer different options for protecting your cubes and controlling
access to information. For example, Cognos Transformer version 7.x supports
user class views whereas later versions of Cognos Transformer replace this
feature with custom views that can be associated with IBM Cognos security
objects (users, groups, and roles).
Data Source Types
Cognos Transformer supports IBM Cognos Series 7 data sources as well as
packages and reports that contain IBM Cognos query items.
This section lists the supported data sources, summarizes the information you
must specify for each data source, and identifies associated limitations.
Tip: You can also click the Help button, where available, for context-sensitive
information about the parameters that you must specify.
Note: Although you can add an unlimited number of data sources or columns to
each model, you must perform any necessary joins between the various data files
before you import the data into your Cognos Transformer model. You must also
ensure that each data source contains sufficient information to provide the
necessary context for any drill-down paths specified in the model.
IBM Cognos Package or Report
You can import query items, and the associated filters and prompts, from IBM
Cognos packages and reports.
You do this by choosing the Package or Report data source type and browsing and
selecting from the available metadata.
Note: Transformer does not support IBM Cognos Finance reports or packages as a
data source. However, you can create PowerCubes directly in Cognos Finance.
After import, you can combine the IBM Cognos data with the data from other
sources as required. Individual query items can be used as source columns in the
Cognos Transformer model, and can be updated using the Modify Columns
feature. In relational packages and reports, measures appear as defined in
Framework Manager.
For more information about using packages and reports as a data source in Cognos
Transformer, see “Guidelines for Using IBM Cognos Packages and Reports as Data
Sources” on page 15 and “Creating a Model in Cognos Transformer” on page 347.
For information about modeling IBM Cognos relational and dimensionally
modeled relational (DMR) data sources, see the Framework Manager User Guide.
Dimensionally Modeled Relational Packages
When you access metadata from a dimensionally modeled relational (DMR)
package, you can import and leverage the dimensions, or import the query items
or metadata that make up those dimensions. You can also import the measure
metadata. Metadata from DMR packages can be directly accessed using:
vInsert Data Source option on the Edit menu
Using this option, you can select measures and query items. The dimensional
structure is not imported.
vInsert Dimension from Package option on the Dimension Map
Using this option, you can select dimensions, hierarchies or levels. The selected
dimensions are created in Cognos Transformer, together with queries containing
appropriate query items.
If you want to take advantage of Cognos Transformer's relative time functionality,
do not import the date dimensions from dimensional packages. Instead, use the
Insert Data Source option to import the appropriate date field to create your time
dimension.
14IBM Cognos Transformer Version 10.1.1: User Guide
OLAP Packages
Cognos Transformer allows you to leverage metadata from published OLAP
packages. As a result, Cognos Transformer PowerCubes can be used as high speed
data access cache methods for distributing smaller or focused areas of your
business information.
Consider the size of the resulting cube when you use another OLAP package as a
PowerCube data source. OLAP sources, such as Essbase, can include significant
amount of data that is not appropriate for PowerCubes. However, taking a specific
segment of data from these sources can be very useful, particularly if you intend to
mix that data with other data sources for further reporting or analysis.
When you use OLAP sources to populate your Cognos Transformer models
v Import the dimensions that you require.
SAP variable prompts are supported and should be used where necessary to
limit the data to a specific segment of your data source. For more information,
see “Working with SAP BW Data Using a Package in Framework Manager” on
page 339.
v Create the time dimension in the same way that you create fact queries.
Cognos Transformer does not support importing time dimensions from any
OLAP source, including PowerCubes. To create the Cognos Transformer time
dimension with relative time categories, import your time information from
either an IBM Cognos relational package or report, or from a flat file exported
from IBM Cognos BI or the original OLAP vendor.
In Cognos Transformer, you add dimensions from OLAP packages directly from
the Dimension Map. This is a practical way to begin creating conformed
dimensions and, to some extent, reusing portions of the published metadata from
the source dimension.
Using the Insert Dimension from Package option on the Dimension Map, you
can select the dimensions, hierarchies, or levels that you want to import from any
OLAP package on to the Cognos Transformer Dimension Map.
SAP BW Packages
You can use Cognos Transformer to import both dimensional and fact data from an
SAP BW query source. To do so, the SAP BW query package must be in a specific
format. The Cognos Transformer PowerCubes you create with these specifically
constructed SAP query packages can be used as high speed data access cache
methods for distributing smaller or focused areas of your business information.
There are three stages to importing an SAP BW query to access both dimensions
and facts using IBM Cognos BI:
v“Creating a BW Query in SAP Business Explorer Query Designer” on page 340
v“Creating a Package in Framework Manager” on page 343
v“Creating a Model in Cognos Transformer” on page 347
Guidelines for Using IBM Cognos Packages and Reports as Data
Sources
This section contains guidelines, best practices, and tips to help you create Cognos
Transformer models using the IBM Cognos packages and reports as data sources.
Chapter 3. Data Sources for Your Model15
For more information on creating Cognos Transformer models, see “Creating a
Model” on page 24.
Use List Reports
Data source queries using reports perform most efficiently when the report is a list.
Graphs, dashboards, crosstabs, and complex reports cannot be used as data source
queries.
Importing Dimensional Packages
Use the Insert Dimension from Package command when importing dimensional
packages if you want the dimensional structure maintained. This option preserves
the dimension levels and uses the smallest set of query items.
Importing Time Dimensions from Packages
When you create a query in Cognos Transformer based on a Framework Manager
package that contains hierarchical time-related categories, Cognos Transformer
interprets the time-related categories as a regular dimension and not as a time
dimension. As a result, the time dimension in your PowerCube will not contain
any relative time categories.
To avoid this problem, ensure that you import all of the data needed to define
your time dimension, and use Cognos Transformer to create the date levels and
categories.
Prompts in Report Data Sources
You can use a report with prompts as a data source in Cognos Transformer. You
must provide values for any mandatory prompts “Edit Existing Prompts in IBM
Cognos Reports and Packages” on page 29 when adding a query based on the
report data source to the model. Cognos 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.
If you want to add a second query using the same report as a data source to your
Cognos Transformer model, you will not be prompted to provide values for
mandatory prompts. The values in the cache will be used. Although you can
refresh the source when adding the second query to force Cognos Transformer to
reprompt you for values, data will still be retrieved based on the first query.
To create two queries in your Cognos Transformer model that are based on the
same report data source, where you want to provide different values for
mandatory prompts, you must duplicate the report data source. Use one report
data source to add the first query to the model and use the duplicate report data
source to add the second query to the model.
Extra queries may appear when you import a report that contains prompt pages.
These queries can be identified by the presence of query items named Use Value
and Display Value. Avoid importing query items from these queries.
For more information about prompt support, see “Edit Existing Prompts in IBM
Cognos Reports and Packages” on page 29, and “Using IBM Cognos Reports to
Create a Data Source” on page 193.
16IBM Cognos Transformer Version 10.1.1: User Guide
Loading...
+ 381 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.