IBM Cognos Disclosure Management Version 10.2.6: Migrating...

IBM Cognos Disclosure ManagementVersion 10.2.6

Migrating from IBM Cognos FSR 6 toIBM Cognos Disclosure Management10.2.6

IBM

NoteBefore using this information and the product it supports, read the information in “Notices” on page 39.

Product Information

This document applies to Cognos Disclosure Management Version 10.2.6 and may also apply to subsequent releases.

Licensed Materials - Property of IBM

© Copyright IBM Corporation 2010, 2016.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Introduction to IBM Cognos Disclosure Management Migration Guide . . . . . . . . . v

Chapter 1. Overview of the migration tool . . . . . . . . . . . . . . . . . . . . . 1Migration scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Migration limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Migrating multiple databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Functionality of the migration tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Overview of migration steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 2. Migration planning . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 3. Prerequisites for upgrading IBM Cognos FSR 6 to IBM Cognos DisclosureManagement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Upgrading the IBM Cognos FSR 6 database . . . . . . . . . . . . . . . . . . . . . . . . 17

Upgrading desktop publishing tags . . . . . . . . . . . . . . . . . . . . . . . . . . 17Upgrading report objects to the latest Microsoft Office format . . . . . . . . . . . . . . . . . 17Generating a new unique database identifier . . . . . . . . . . . . . . . . . . . . . . . 17

Installing IBM Cognos Disclosure Management . . . . . . . . . . . . . . . . . . . . . . . 19User accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Setting up a user account to connect to the IBM Cognos FSR 6 database . . . . . . . . . . . . . . 19Setting up a user account to connect to the IBM Cognos Disclosure Management databases . . . . . . . 19

Uploading taxonomies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 4. Installing the migration tool . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 5. Running the migration tool . . . . . . . . . . . . . . . . . . . . . . 23

Chapter 6. Resolving report objects . . . . . . . . . . . . . . . . . . . . . . . 29Resolving desktop publishing tags in report objects . . . . . . . . . . . . . . . . . . . . . . 30Resolving XBRL tags in report objects . . . . . . . . . . . . . . . . . . . . . . . . . . 31Resolving XBRL tuples in report objects . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 7. Manual updates . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Post migration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

© Copyright IBM Corp. 2010, 2016 iii

iv IBM Cognos Disclosure Management Version 10.2.6: Migrating from IBM Cognos FSR 6 to IBM Cognos Disclosure

Management 10.2.6

Introduction to IBM Cognos Disclosure ManagementMigration Guide

The IBM Cognos Disclosure Management Migration Guide describes how to usethe migration tool to migrate data from IBM® Cognos® FSR Version 6 to CognosDisclosure Management Version 10.2.6.

Cognos Disclosure Management is a unified financial governance solution thatfocuses on improving financial processes and controls, particularly in the finalstages before disclosure. It helps the finance department improve the timelinessand quality of financial management processes and reporting. Cognos DisclosureManagement also facilitates audits, extends enterprise resource planning (ERP)transactional controls, and improves financial risk management.

Audience

The IBM Cognos Disclosure Management Migration Guide is intended for userswho need to migrate data from IBM Cognos FSR Version 6 to Cognos DisclosureManagement Version 10.2.6.

Finding information

To find information on the web, including all translated documentation, access IBMKnowledge Center (http://www.ibm.com/support/knowledgecenter).

Publication date

This document was published on June 13, 2016.

Accessibility features

Accessibility features help users who have a physical disability, such as restrictedmobility or limited vision, to use information technology products. IBM CognosHTML documentation has accessibility features. PDF documents are supplementaland, as such, include no added accessibility features.

Forward-looking statements

This documentation describes the current functionality of the product. Referencesto items that are not currently available may be included. No implication of anyfuture availability should be inferred. Any such references are not a commitment,promise, or legal obligation to deliver any material, code, or functionality. Thedevelopment, release, and timing of features or functionality remain at the solediscretion of IBM.

Samples disclaimer

The Sample Outdoors Company, Great Outdoors Company, GO Sales, anyvariation of the Sample Outdoors or Great Outdoors names, and Planning Sampledepict fictitious business operations with sample data used to develop sampleapplications for IBM and IBM customers. These fictitious records include sampledata for sales transactions, product distribution, finance, and human resources.

© Copyright IBM Corp. 2010, 2016 v

http://www.ibm.com/support/knowledgecenter/

http://www.ibm.com/support/knowledgecenter/

Any resemblance to actual names, addresses, contact numbers, or transactionvalues is coincidental. Other sample files may contain fictional data manually ormachine generated, factual data compiled from academic or public sources, or dataused with permission of the copyright holder, for use as sample data to developsample applications. Product names referenced may be the trademarks of theirrespective owners. Unauthorized duplication is prohibited.

vi IBM Cognos Disclosure Management Version 10.2.6: Migrating from IBM Cognos FSR 6 to IBM Cognos Disclosure

Management 10.2.6

Chapter 1. Overview of the migration tool

The migration tool provides you with all of the required information tosuccessfully migrate your data from IBM Cognos FSR 6 to IBM

®

Cognos®

Disclosure Management 10.2.6.

Supported versions for this tool are described in the following table.

Table 1. Supported versions of Cognos FSR and Cognos Disclosure Management

Supported versions of theDatabase, Client, and Server Version of Cognos FSR 6

Versions of CognosDisclosure Management

Database version 6.7.0.37

6.7.1.1

6.7.2.4

10.2.6

Client version 6.7.0

6.7.1

6.7.2

10.2.6

Server version 10.2.6

Important: The minimum supported version of Cognos FSR is 6.6.1 GA.

Migration scopeThe migration tool provides a basic migration of data to ensure you have a startingpoint after upgrading from IBM Cognos FSR 6 to IBM

®

Cognos®

DisclosureManagement.

The tool includes migration of the following items:

Users SQL and Windows users in your Cognos FSR database. Imported SQLusers will be set with the same initial default password. Applicablepermissions from Cognos FSR are mapped and set at application andreport levels for imported users. Some recommended permissions inCognos Disclosure Management will also be set by default that you canedit after the migration has run. If you are using an XBRL-enabled versionof Cognos FSR and have XBRL permissions, you will have all CognosDisclosure Management XBRL permissions in Cognos DisclosureManagement by default.

Report GroupsEntities you have in your Cognos FSR database.

ReportsWhen you select which reports to migrate, the entity or report group itbelongs to is also migrated, retaining the entity to report relationship asyou have in Cognos FSR. The following report properties are mapped andmigrated: Due Date, Submission Due Date, and Period and ReportOwner. The dates are converted from the local date stored in the CognosFSR database to Coordinated Universal Time (UTC).

© Copyright IBM Corp. 2010, 2016 1

Report Objects and HierarchyThe two-level hierarchy for your reports in Cognos FSR is replicated toCognos Disclosure Management (sections and objects) in the same sortorder.

Object WorkflowsWorkflows defined in your report objects including workflow states andproperties such as background color and image, transitions, and propertiessuch as due date, current state, and assigned user.

External Data SourcesSource connections and query details defined in your excel objects. Thisincludes external Excel files and OLAP queries on your database sheet andrelational queries, as defined in Query Builder, on your query sheets.

Shared Objects and ReferencesShared and reference objects are migrated to Cognos DisclosureManagement. A Migrate Dependent Objects option is provided that willdetect the dependencies and migrate the shared objects first to ensure thereference objects can be created. After importing the dependent objects, themigration tool engine will also detect and set the cascaded relationships ifthe selected report is a cascaded report.

Object PropertiesThe following properties are mapped and converted where needed whenmigrating to Cognos Disclosure Management: Object Due Date, BreakType and Break Number, Print Option, Font Type, Font Size, ParagraphKeep with Next, Table Indent from Left. Section TOC and Note variablesare pushed down to object level.

Object Reference VariablesThe following object reference variables are recognized in CognosDisclosure Management with the migration of your report objects. Someare recognized after the migration tool does the necessary conversions:

Table 2. Object reference variables

Variable Tag

AutomaticIdentification byCognos DisclosureManagement whenmigration toolimports object Comments

Range Start ##RS Yes

Range End ##RE Yes

Source (includingrange block)

##S Yes

Destination(including rangeblock)

##D Yes

Destination forGlobal Source Staticor Dynamic

##GD Yes

Global Source Static ##GSS Yes, once converted The migration toolwill convert to##GSD on import

Global SourceDynamic

##GSD Yes

2 IBM Cognos Disclosure Management Version 10.2.6: Migrating from IBM Cognos FSR 6 to IBM Cognos Disclosure

Management 10.2.6

Table 2. Object reference variables (continued)

Variable Tag

AutomaticIdentification byCognos DisclosureManagement whenmigration toolimports object Comments

Validation Rule ##R Yes

Note Left/Right ##NL Yes

Superscript Note Left ##SL Yes

Superscript NoteRight

##SR Yes

Workflow Rule ##WR Yes

Workflow Status ##WS Yes

Image Range Start ##IRS Yes The migration toolwill also update theWord object changingfrom Cognos FSR 6Bookmark syntax toCognos DisclosureManagementhyperlink syntax

Image Range End ##IRE Yes The migration toolwill also update theWord object changingfrom Cognos FSR 6Bookmark syntax toCognos DisclosureManagementhyperlink syntax

Image Fixed RangeStart

##IFRS Yes, once converted The migration toolwill convert to##IRS/##IRE tagsand the tool will alsoupdate the Wordobject changing fromCognos FSR 6Bookmark syntax toCognos DisclosureManagementhyperlink syntax

Image Fixed RangeEnd

##IFRE Yes, once converted The migration toolwill convert to##IRS/##IRE tagsand the tool will alsoupdate the Wordobject changing fromCognos FSR 6Bookmark syntax toCognos DisclosureManagementhyperlink syntax

Chapter 1. Overview 3

Custom GroupsCustom groups you have defined in your Cognos FSR database includingthe association of the customized groups to your report objects.

SnapshotsReport level snapshots you have saved in your Cognos FSR database.

Query VariablesQuery variables you have defined in your Cognos FSR database at reportand object levels.

Desktop Publishing TagsTagged content in your Excel and Word objects for output to AdobeInDesign.

If you are using an XBRL-enabled version of Cognos FSR:

XBRL ManagementUnits (excluding dynamic units related to query tagging), Time Periods(excluding Forever type time periods), and Scale Factors. Decimal accuracy(excluding precision accuracy), defined for your Cognos FSR scales will bemigrated at the tagging level. Taxonomies that you select to migrate will beimported.

XBRL Cache ManagerHTTP cached content for taxonomy files stored in your Cognos FSRdatabase.

XBRL Entity ConfigurationEntity schemes and identifiers you have defined at entity level in yourCognos FSR database. Report level overriding identifiers will also beimported.

XBRL Report ConfigurationThe XBRL configurations for your report will be migrated to CognosDisclosure Management at project level. You will be able to migrate yourXBRL report as one or more projects in Cognos Disclosure Management.

XBRL TagsFor your XBRL configured reports, XBRL tags in your Excel and Wordobjects in your Cognos FSR database will be migrated to CognosDisclosure Management at project level. Migration of XBRL tags will onlyinclude the following types of tagging:

Table 3. Migration of XBRL tags

Type of tag Part of migration Comments

Item tagging Yes Certain tags are skipped andlogged as not supported orare deemed invalid inCognos FSR. Orphan tags aremigrated as exceptions

Textblock tagging Yes Certain cases for text blockitems are skipped andlogged as not supported.Orphan tags are migrated asexceptions


Management 10.2.6

Table 3. Migration of XBRL tags (continued)

Type of tag Part of migration Comments

Dimension tagging Yes For explicit, simple type orcomplex type simple contentdimensions only. Complextype complex content anddynamic typed dimensionsare not supported

Negated tagging Yes

Enumerated value tagging Yes

Nil tagging Yes

Footnote tagging Yes

Query tagging Ignored Not supported

Tuple tagging Yes Certain tuples are skippedand logged as not supportedor are deemed invalid inCognos FSR. Empty tuples ortuples with less than theminimum amount of contentare migrated as exceptions

There are some exceptions to the above scope, where manual updates using theCognos Disclosure Management client will be required after import:v Page Orientationv TOC and Note Variable Name Changesv Object reference variable names and comments maximum lengthsv Query variable names with unsupported characters or the length is too longv Verify and resolve valid errors for report objects using the clientv Verify and resolve valid errors for XBRL tagged report objects using the clientv Convert external data sources that are not supported such as Microsoft Access

connectionsv Convert relational data sources for OLE DB and ODBC connections. The

migration tool will migrate the connection strings as is. You may need to updatethem by: switching from a 32-bit to 64-bit driver since 32-bit providers are notsupported in Cognos Disclosure Management, changing from DSN to a DSN-lessconnection string, or switching to a relational provider instead (Microsoft SQLServer, Oracle or DB2®)

v Convert Essbase report script member specifications to MDX scriptsv Add your Oracle Hyperion Financial Management (HFM) data sources for your

migrated report objects with Oracle HFM formulasv Convert external links in your Excel objects and update the formulas with the

external referencesv Convert pivot tables in your Excel objects with external data sources

The migration tool converts the following items, either due to how it functions inCognos Disclosure Management, or the feature is not yet available:v Any unsupported characters in the character set are removed from report object

names, reports, and report groups.v Global static source variables ##GSS are converted to ##GSD in your report

objects.


v Image fixed range variables ##IFRS/##IFRE are converted to ##IRS/##IRE inyour report objects.

v Bookmarks in Word objects referencing Excel charts or image range variables areconverted to hyperlinks.

v Section level TOC and Note variables that are set in your reports are pusheddown to object level to the first printable report Excel or Word object.

v TOC and Note variables are removed of any unsupported characters.v Dummy text is inserted into your empty page setup objects with paragraph

settings copied from the Normal style such as font type and font size. Theparagraph settings from the dummy text in the page setup object are applied tosubsequent objects, based on the enforcement settings, in Cognos DisclosureManagement report generation.

v If you have a header or footer in a report section, the object is moved to thebeginning of the report section. Cognos Disclosure Management applies headersor footers to subsequent objects in a section depending on the order of theobjects. By moving to the top of the report section, the header or footer will beapplied to objects within the section.

v If the page setup object has the Different Odd & Even Pages property set, themigration will detect and set the header or footer placement object propertyaccordingly on the header or footer objects.

v Objects with Break Type as Blank Row in Cognos FSR will be mapped to thenew property Blank Row with Page Setup Properties in Cognos DisclosureManagement where new line breaks in report generation will apply paragraphsettings from your page setup object such as font type and size. This will controlthe height of the line breaks.

v The enforcement setting Keep with Next Paragraph/Table for Excel objects andthe page setup object paragraph setting on the dummy paragraph of text isupdated based on the migration options. If the Enforce Keep Table with Nextoption is selected, the enforcement setting is set based on Cognos FSR behavior.Otherwise, the enforcement setting will be set to true by default.

v The enforcement setting Keep with Next Paragraph/Table is not enabled forWord objects by default based on Cognos FSR behavior. If the Word object inCognos FSR has the enforcement setting enabled, the tables in the migratedWord object are updated to keep the table rows from breaking across the pages.The table will only split at the beginning of a row as opposed to splitting in themiddle of the row's content.

v Report and object level query variables referenced in Essbase query memberspecifications. If the query variable value references a dimension memberencased in single quotes, it is replaced with brackets for MDX compatibility. Forexample: 'Y2007' is updated to [Y2007].

v Orphan workflow states where a state was deleted in Cognos FSR but is stillreferenced in an object workflow are migrated with the name suffixed with"(Deleted)".

v Duplicate workflows status names are migrated and appended with anincrement in the name.

v Macros will be removed from report objects saved as macro enabled documentformats (extensions .DOCM/.XLSM) and converted to .DOCX/.XLSX formats asthese macro extensions are not supported in Cognos Disclosure Management.

v Named ranges and bookmarks for your desktop publishing tags are renamed inyour report objects when migrating to Cognos Disclosure Management.


Management 10.2.6

v Desktop publishing tags in your Excel objects are associated to a default stylenamed Migration Default Style, since it is mandatory in Cognos DisclosureManagement for each tag to have an associated style.

v Desktop publishing tags in your Word objects with no style assigned, (None),are associated with the Microsoft Office style that is applied to the content, ifapplicable, or the default style Migration Default Style.

v Desktop publishing tag names are appended with an increment in the name ifmore than one tag has the same name. In Cognos FSR, you can have multipleExcel tags with the same name across objects in a report and multiple Word tagswith the same name within one object and across objects in the report.

v Desktop publishing tags in your Word objects with the same tag name and sameassociated style are reused. For instance, two Word tags will be migrated as onetag with two references.

v XBRL configured reports and tags are migrated to project level in CognosDisclosure Management and transformation sets are created with necessarytransformations as needed to handle such Cognos FSR settings as scale factors,nil values and enumerated values.

v XBRL units with custom measures are migrated to Cognos DisclosureManagement with no namespace, where it will resolve by default to the targetnamespace of your imported taxonomy.

v XBRL time periods are migrated to Cognos Disclosure Management as two timeperiods, one as Duration (start and end date) and the other as Instant (the enddate only).

v XBRL negation of the entire row or column functionality in Cognos FSR, whereyou can place a -1 in the ##RS row or ##RS column, is migrated to CognosDisclosure Management by converting to the negated property.

v Named ranges and bookmarks for your XBRL tags are renamed in your reportobjects when migrating to Cognos Disclosure Management.

v If you use report level query variables for time period, unit, scale, or explicitdimension members as dynamic context for your XBRL tags, the migration toolwill replace the query variables with their static values since query variables foraspects are not supported in Cognos Disclosure Management.

v XBRL tags assigned to a scale with infinite precision accuracy are converted toinfinite decimal accuracy.

Related tasks:“Resolving XBRL tags in report objects” on page 31The migration tool will import XBRL tags in your report objects based on theprojects you selected to be created in the migration wizard.

Migration limitationsThe migration tool will import your object workflows and external data sources(external Excel files, relational and OLAP queries) associated with your reportobjects. However, there are some limitations with the migration tool.

It is important to verify all of your migrated queries and referencing formulas inyour migrated Excel objects.

The migration process will:v Import your source connection details.v Import your source query details.


v Migrate your query variables at report and object levels. At the application level,they are set with the default value 0 just as query variables are at report level inCognos FSR.

Important: Your migrated query will execute at report level with correctvariable values substituted before execution. However, in Data QueryManagement, you will receive a query execution error if you want to see thedata preview. If you want to see the data preview for a migrated query, you canchange the default value 0 at the application level provided there is no conflictwith another report using the same variable. You can also create a new queryvariable to reference.

v Copy your Cognos FSR database sheet which will be named Database (LegacyCopy).

v Transform the database and query sheets from Cognos FSR to IBM®

Cognos®

Disclosure Management format and automatically update all formulasreferencing these sheets.

New features in Cognos Disclosure Management that are equivalent to the CognosFSR query option and are set accordingly during migration:v Suppress Rows with Null Values. If your OLAP query in Cognos FSR has

Suppress Missing selected, this query level option in Cognos DisclosureManagement will be set to true.

v Display Missing Data as '<Label>'. If, in your Cognos FSR client configurationfile, you have set the key DisplayMissingValuesAsZero to true, you can selectthe check box Display Missing Values as Zero in the migration tool. If thischeck box is not selected, the migration will, by default, set the missing datalabel to empty cell.

There are some limitations in the migration of workflows and external datasources:v Hierarchy security members. This option is ignored in the migration as there is

no equivalent option in Cognos Disclosure Management.v Essbase report scripts. Cognos Disclosure Management supports MDX for

Essbase queries. Any report scripts in your Essbase queries will require anupdate to MDX syntax. The report script will be migrated as is and logged as awarning. You will need to edit and resolve your query after migration.

v Member specification IChildren. In Cognos FSR, the parent-child orderreturned are children preceding their parents. In Cognos DisclosureManagement, the default parent-child order returned is parents before theirchildren. For the purposes of migration, a special flag is set to retain the sameorder result as Cognos FSR. If you would like to edit your query to change theorder after migration, you will need to delete and re-add the query and thenre-link your formulas.

v Refresh type for relational queries. In Cognos FSR, for relational queries, theRefresh Type option controls whether the relational query should refresh OnDemand, On Rollover or Always. In Cognos Disclosure Management, thisfeature is not available. A data refresh impacts all queries in the report object.

v Relational sources with unsupported server types. In Cognos FSR, you cancreate queries in Query Builder for the following server types: Microsoft SQLServer Connection, Oracle Connection, Microsoft Access Connection, OLE DBConnection and ODBC Connection. Cognos Disclosure Management does notsupport the latter two providers; 32-bit providers are not supported. For anunsupported server type, you will need to convert to a relational query orexternal Excel file query. For OLE DB Connection and ODBC Connection


Management 10.2.6

providers, the migration tool will migrate the connection strings as is, where youwill need to convert to a 64-bit provider, from a DSN to DSN-less connectionstring or to a relational query.

v Disconnected data sources. If your report object in Cognos FSR has a currentworkflow state that is disconnected from data sources, the object will be set inlocked state in Cognos Disclosure Management as the equivalent option whenmigrated. A locked state in Cognos Disclosure Management includes more thanqueries not being executed for that report object. The locked state once migratedmeans that the following content will not be refreshed: destination variables(##D, ##GD) in the object, the reference object will not be refreshed from theshared object, external Excel files, and OLAP and relational queries will not beexecuted.

Migrating multiple databasesThe migration tool supports migrating multiple Cognos FSR databases to one IBMCognos Disclosure Management database.

Unique database identifier

Each Cognos FSR database is uniquely identified by a database identifier,specifically its Microsoft SQL Server Service Broker GUID. The migration toolremembers what items were migrated from your source regardless of whichMicrosoft SQL Server instance on which your database resides. This means you canmove your Cognos FSR database to a new server or restore a copy of yourdatabase to use for migration and the tool will identify the database as the samesource.v If you have multiple FSR databases that are valid separate sources with different

reports, you must verify the identifier on each database prior to migrating thatdatabase. It is possible for databases to have the same identifier if you restored adatabase from a backup and then continued to make modifications and use therestored database as another FSR database. In this scenario, you will need togenerate a new unique identifier on the FSR database with the duplicateidentifier prior to migrating. See the chapter Prerequisites for upgrading IBMCognos FSR 6 to Cognos Disclosure Management for information about checkingand generating the new database identifier.

Migration behavior

Migration behavior is designed to remember what has been migrated and toreduce duplications where possible:v Once an item is migrated, it has been migrated. You will not be able to select it

for migration in the UI. You can continue to migrate new items from this source.v You can delete the migrated item in Cognos Disclosure Management if you need

to re-migrate that item from this source. You can then select it again from the UI.v If you upgrade from a previous version of Cognos Disclosure Management, you

can continue to migrate new items from this source.v The migration tool will try to reduce duplications by reusing an existing entity

that already has been migrated to Cognos Disclosure Management or generate aunique name as needed if the item to migrate will need to be added as aseparate entity. You can update further to reduce duplications in the CognosDisclosure Management client after migration of each source.


Table 4. Items to migrate where the migration tool will reduce duplications if possible..Important: If the migration tool cannot reduce duplications, it will create a unique name toensure the item can migrate.

Item tomigrate Naming convention Reuse? Comments

Workflow State FSR Status Name index Y

Custom Group FSR Custom Group Name[index] Y

User FSR Login Id Y The same user inmultiple Cognos FSRdatabases will getapplication permissionsset one-time with themigration of your firstCognos FSR database.Report permissions forthis user will get setbased on the individualCognos FSR source. Youcan manually updateapplication and reportpermissionspost-migration throughthe Cognos DisclosureManagement client.

Import Source Domain Y

Query Variable FSR Query Variable Name Y

Relational DataSource

FSR Connection Name_index Y

Relational DataQuery

FSR Query Name_index Y

External ExcelFile DataSource

<File Name>_<ObjectID>_count Y

External ExcelFile DataQuery

<File Name>_<SheetName>_<ObjectID>_count

Y

OLAP DataSource

<Server>_<Application>_<Cube>

_<ObjectID>_count

Y

OLAP DataQuery

<Server>_<Application>_<Cube>_

<ObjectID>_count

Y

DesktopPublishingStyle

Migration Default Style or MicrosoftOffice Style Name

Y


Management 10.2.6

Table 4. Items to migrate where the migration tool will reduce duplications ifpossible. (continued).Important: If the migration tool cannot reduce duplications, it will create a unique name toensure the item can migrate.

Item tomigrate Naming convention Reuse? Comments

Report Group FSR Report Group Name N Migration will alwaysmigrate as a separateentity. You can renamethe duplicate reportgroup name if you wantto keep the separategrouping or move outthe reports first beforedeleting the reportgroup.

Report FSR Report Name N Migration will alwaysmigrate as a separateentity.

Cache Entry URL Y

Time Period FSR Time Period Name and FSRTime Period Name - instant

Y

Unit my<FSR Unit Name> Y

Entity Scheme FSR Entity Scheme Name Y

Entity FSR Entity Identifier[index] Y

Taxonomy FSR Taxonomy Name[index] N Migration will alwaysmigrate as a separateentity.

Project FSR Report Name[index] or CustomProject Name[index]

N Migration will alwaysmigrate as a separateentity.

Transaction Set(scale factor)

my_<FSR Scale Name> Y

TransformationSet(dynamicallycreated asneeded)

my_Fact Value String to Number

my_Enumerated Value - <enumvalue>

my_fact Value String to Nil forEmpty Cell

my_fact Value String to Nil for ''<nilvalue>''

my_Date Format Value - <dateformat>

my_Fact Value String to Empty

Y

Functionality of the migration toolThe migration tool connects to your IBM Cognos FSR 6 database and imports andconverts data, where necessary, into your IBM

®

Cognos®

Disclosure Managementdatabase.


A user is created in Cognos Disclosure Management solely for the purposes ofmigration. This user will have all of the necessary permissions automatically setsuch that you can log into the Cognos Disclosure Management client after runningthe migration tool to verify, edit, and resolve your imported report objects. Aftermigration has been completed, you can disable this migration user.

Overview of migration stepsYou can follow simple configurations and procedures to ensure a successfulmigration of your data from IBM Cognos FSR 6 to IBM

®

Cognos®

DisclosureManagement 10.2.6

Procedure1. Upgrade your Cognos FSR 6 database to version 6.6.1 if you are currently

using an older version of Cognos FSR.2. Install Cognos Disclosure Management.3. Install the migration tool on the same server where your Cognos Disclosure

Management server is installed.4. Run the migration tool on the Cognos Disclosure Management server.5. Resolve raised notifications by the tool for objects that could not be

successfully imported into Cognos Disclosure Management.6. Update the following using the Cognos Disclosure Management client to

complete the basic migration:a. Page Orientation.b. For TOC and Note variables that the migration log indicate the variable

name was removed of unsupported characters, update the report objects inyour migrated report referencing these variables to the changed names.

c. For object reference variables and comments that the migration log indicatethat the length is too long, update the report object containing the variablename or comment to a shorter length. This will apply to variable namesand variable comments where allowed maximum lengths in CognosDisclosure Management is 100 and 500, respectively, whereas Cognos FSRallows longer lengths.

d. For query variables with names containing unsupported characters or thelength is too long, manually add the query variables.

7. Using Cognos Disclosure Management, manually configure and update tomigrate the following items that are not part of the migration scope:a. Essbase report scripts. Convert member specification to MDX script.b. Relational sources with unsupported server types. Convert to a relational

query. For instance, Microsoft SQL Server, Oracle or DB2, or an externalExcel file source.

c. Relational sources with OLE DB and ODBC connections to 32-bit provideror DSN connection string. Convert to a 64-bit provider and DSN-lessconnection string respectively or convert to a relational query.

d. Add Oracle HFM data sources and associate with your migration reportobject content with Oracle HFM formulas.

e. Orphan workflow users and states. Update workflow states and objectworkflows.

f. Expiration policy. A default cache expiration policy is set for all migratedOLAP and relational queries named Expiration Policy for Migration Query.You can edit this policy or create your own. For migrated external Excel filequeries, it is set by default to the expiration policy installed by Cognos


Management 10.2.6

Disclosure Management named Whenever External Excel File is Modified. Youcan change this to a different policy or create your own.

g. External links. Convert external links in your Excel object to an externalExcel file data source and query in Cognos Disclosure Management andassociate the query with your report. In your Excel object, insert the newquery and update all formulas referencing the external link to the queryresult sheet instead. You can locate the formulas with the externalreferences by searching the workbook's formulas for the left squarebracket, since external references use brackets to enclose the workbookname.

h. Pivot tables with external data sources. Convert pivot tables with externaldata sources in your Excel object by creating a data source and query inCognos Disclosure Management and associate the query with your report.In your Excel object, insert the new query and change your pivot datasource to point to the range on the query result sheet instead.

8. Update the following using the Cognos Disclosure Management client tocomplete the migration of tagged content for output to Adobe InDesign:a. For tags purposefully skipped by the migration tool, resolve and add

manually.b. For tags that did migrate but had a valid warning, resolve and update

manually.c. For tags associated with the default style, Migration Default Style, you

can rename the default style name or create your own.9. Update the following using the Cognos Disclosure Management client to

complete the XBRL migration:a. Run refresh of project items for your migrated XBRL reports and resolve

the valid errors such as orphan tags that you had existing from CognosFSR.

b. For XBRL tags purposefully skipped by the migration tool, resolve andadd manually.

c. For XBRL tags that did migrate, but had a valid warning, resolve andupdate manually.

d. For tagged items to empty cells, the tag will have been migrated withdefault string to nil transformation. If the preference is to generatetagged empty cells as zero or to omit them, then update the defaulttransformation set named my_Fact Value String to Nil for Empty Cell.

e. For XBRL tuples or tags attached to the tuple that are purposefullyskipped by the migration tool, resolve and add manually in the TupleExplorer.

f. For XBRL tuples or tags attached to the tuple that did migrate, but had avalid warning, resolve and update manually in the Tuple Explorer.

10. Clean up the migration:a. Disable the migration user.



Management 10.2.6

Chapter 2. Migration planning

The process of migrating data from your Cognos FSR database to IBM®

Cognos®

Disclosure Management involves a combined effort of utilizing the migration tool,manual updates, and a complete review and verification.

The import processing times for your reports, snapshots, taxonomies, and XBRLtags using the migration tool can vary based on various factors:v The Cognos FSR data source serverv The Cognos Disclosure Management server, where the migration tool is runv Having sufficient resourcesv The size of your report objects and snapshotsv The number of objects per reportv The number of tags per report objectv Network connection

You can set up a test environment mirroring production and run the migration toolto get an idea of processing times based on your Cognos FSR database as part ofyour migration plan. As a best practice, you should migrate your reports one at atime or in small batches of five provided the reports in the batch are not largereports. If a report is very large with over 1000 objects, migrate only the onereport. If a report is large and has numerous snapshots saved, for instance 50 ormore, migrate only the one report. This will allow you to verify and resolve as yougo with each migrated report as opposed to trying to migrate and troubleshoot alarge number of reports all at once.

If you have an XBRL-enabled version of Cognos FSR, you should migrate inmultiple runs by migrating all of your reports first, then your taxonomies, and last,migrate all of your XBRL tags.



Management 10.2.6

Chapter 3. Prerequisites for upgrading IBM Cognos FSR 6 toIBM Cognos Disclosure Management

Ensure that the following prerequisites have been met before you install and runthe migration tool.

Upgrading the IBM Cognos FSR 6 databaseYou must upgrade your current version of IBM Cognos FSR to Version 6.6.1 if youare currently using an earlier version.

About this task

You can use the Cognos FSR Database Upgrade Utility to update the Cognos FSRdatabase to Version 6.6.1. For more information, see the IBM Cognos FSR InstallationGuide 6.6.1.

Upgrading desktop publishing tagsIf you have tagged content in your reports for output to Adobe InDesign, youmust run the data conversion procedure for your reports to upgrade the tags priorto migration.

About this task

You can use the IBM Cognos FSR Database Upgrade Utility to update the CognosFSR database to Version 6.6.1. For more information, see the IBM Cognos FSRInstallation Guide 6.6.1.

Procedure

In IBM Cognos FSR, click Administration > Data Conversion > Upgrade DesktopPublishing tags.For more information, see the IBM Cognos FSR Administration Guide 6.6.1.

Upgrading report objects to the latest Microsoft Office formatYou can upgrade your report objects to the latest Microsoft Office format prior tomigration.

About this task

You can use the Cognos FSR Office Conversion Utility to upgrade your reportobjects to the latest Microsoft Office format. For more information, see UpgradeMicrosoft Office objects with IBM Cognos FSR Office Conversion Utility(http://www-01.ibm.com/support/docview.wss?uid=swg21592651).

Generating a new unique database identifierIf you will be migrating more than one Cognos FSR database to the same IBM

®

Cognos®

Disclosure Management, you must check that the identifier on eachdatabase is unique.


http://www-01.ibm.com/support/docview.wss?uid=swg21592651

http://www-01.ibm.com/support/docview.wss?uid=swg21592651

About this task

The migration tool uniquely identifies each database by its Microsoft SQL ServerService Broker GUID. It is possible for databases to have the same databaseidentifier if you restored a database from a backup and then continued to use therestored database as another Cognos FSR database. Check the Cognos FSRdatabases that you want to migrate to see if each database has a different identifier.

Procedure1. Check that each Cognos FSR database that you want to migrate has a unique

database identifier. To verify, you can run the following SQL statement:SELECT name, service_broker_guid

FROM sys.databases

ORDER BY service_broker_guid, name

Important: If your Cognos FSR databases are on multiple SQL instances, alsoensure to run this query on each SQL instance and compare the broker IDs.

Table 5. Comparison of broker IDs on multiple Cognos FSR databases.

Database Name

Database Identifier

SQL Server Service BrokerGUID Duplicate Identifier?

FSR_01 7A812427-5516-427C-AAC0-06A38A878643

N

FSR_02 1C7DB876-D952-4C2F-9B63-74E995E02E22

N

FSR_03 E2EE8375-4DC9-4B27-9625-A839E682470A

N

FSR_04 83E801FC-CD1A-4DC4-A29E-4E46E3DD2104

N

FSR_05 83E801FC-CD1A-4DC4-A29E-4E46E3DD2104

Y

2. Generate a new service broker identifier on the Cognos FSR database with theduplicate identifier using the SQL statement later in this section. If you are notusing SQL Service Broker for any applications, there is no impact to re-generatethe service broker identifier on your Cognos FSR database.

Important: Ensure all users are logged out of Cognos FSR when you run thisSQL script or it will automatically log out any users logged in. Exclusive lock isrequired on the Cognos FSR database to generate the new broker.Replace $(FSRDBNAME) with the name of your FSR database.

Important: Executing this script will kick off any users that are logged intoyour FSR databaseUSE master

GO

ALTER DATABASE [$(FSRDBNAME)] SET NEW_BROKER WITH ROLLBACK IMMEDIATE

GO


Management 10.2.6

Installing IBM Cognos Disclosure ManagementYou must install IBM

®

Cognos®

Disclosure Management before you can migrateyour data from IBM Cognos FSR 6. You must also upgrade Cognos DisclosureManagement to 10.2.6 if you have a previous version of the product installed.

About this task

To install Cognos Disclosure Management 10.2.6 see the IBM Cognos DisclosureManagement Installation Guide.

Important: When installing the Cognos Disclosure Management server, selectTypical installation when choosing Setup Type in the installation wizard. Themigration tool is installed along with the core Cognos Disclosure Managementapplication.

If you are installing IBM®

Cognos®

Disclosure Management XBRL along with theCognos Disclosure Management server, select Custom installation when choosingSetup Type in the installation wizard. The migration tool is selected for installationby default.

User accountsYou must set up user accounts to connect to both the IBM Cognos FSR 6 databaseand IBM

®

Cognos®

Disclosure Management.

Setting up a user account to connect to the IBM Cognos FSR6 database

You must set up a user account to connect to the IBM Cognos FSR 6 database.

About this task

A domain account or a SQL login that has access to your Cognos FSR 6 database isrequired with, at minimum, db_reader permissions. This account will be used bythe migration tool to connect to the Cognos FSR 6 database. No existing tables inyour Cognos FSR database will be modified.

Setting up a user account to connect to the IBM CognosDisclosure Management databases

You must set up a user account to connect to the IBM®

Cognos®

DisclosureManagement databases.

About this task

A domain account or a SQL login that has access to your Cognos DisclosureManagement databases is required with db_owner permissions. This account willbe used by the migration tool to connect to, and update, the Cognos DisclosureManagement databases.

Important: There are two databases, typically named CognosDM and CognosDMCache.If XBRL is also installed, there is a third database that is typically namedCognosDMXBRL.

Chapter 3. Prerequisites for upgrading IBM Cognos FSR 6 to IBM Cognos Disclosure Management 19

Uploading taxonomiesIf you are using an XBRL-enabled version of Cognos FSR, you must upload yourtaxonomy files locally to the IBM

®

Cognos®

Disclosure Management server.

About this task

The migration tool is run on the Cognos Disclosure Management server and theimport of taxonomies requires the local files. You will need to copy your taxonomyfiles from your current file location to a folder locally on the Cognos DisclosureManagement server. If you have your taxonomies cached, you can export themfrom Cognos FSR.

Procedure1. In the Cognos FSR client, navigate to XBRL > Configure XBRL > Manage >

Taxonomies.2. Select your taxonomy and click Save Cache. The taxonomy files will be saved

to your local disk from where you are running the Cognos FSR client.3. Copy the exported taxonomy files from your local disk to the Cognos

Disclosure Management server disk.

Results

Your taxonomies are now saved on the Cognos Disclosure Management serverdisk. When you run the migration tool, you will be able to import your taxonomyfiles into the Cognos Disclosure Management database.


Management 10.2.6

Chapter 4. Installing the migration tool

You must install the migration tool on the same server where your IBM®

Cognos®

Disclosure Management server resides.

About this task

The migration tool is automatically installed with Typical installation when youinstall Cognos Disclosure Management server.

Procedure1. Go to the location where you installed the Cognos Disclosure Management

website. The typical location is the c:\inetpub\wwwroot\CognosDM-Server\Toolsdirectory.

2. Navigate to the Tools folder. If you do not see a compressed file namedMigration Tool, then you must run the Cognos Disclosure Management serverinstaller again.

3. On the Program Maintenance window, select Modify and then click Next.4. Click Migration Tool > This feature will be installed on local hard drive and

then click Next. Follow the rest of the prompts in the wizard.5. Navigate to the Migration Tool compressed file and extract its contents to the

current location or select a different location.

Results

The migration tool is now installed and ready to use.



Management 10.2.6

Chapter 5. Running the migration tool

After you install the migration tool, you can run the tool by following the stepsbelow.

Before you begin

Ensure that all users are logged off IBM Cognos FSR 6 prior to running themigration tool. Only one user should be running the migration tool at a time. Youmust run the migration tool as an administrator.

Procedure1. Log in to the IBM

®

Cognos®

Disclosure Management client as the defaultsecurity administrator.

2. Navigate to Administration > Security > Users, then click Add.3. Create an application user. This user will be used solely for migration

purposes.4. Log out of the Cognos Disclosure Management client.5. Navigate to the location where the migration tool application is installed

<InstallationFolder>\MigrationTool\.6. Double-click Ibm.CognosDM.Migration.UI.exe to run the application.7. When the migration wizard opens, you will see a list of nine steps that you

must complete. FSR Settings. Enter the server name in the Server Name fieldand the Cognos FSR database name in the Database field. Select UseIntegrated Security if you are connecting to your Cognos FSR database usingWindows authentication. If you are not using Windows authentication, enteryour SQL login and password to connect to your Cognos FSR database.Ensure that this user account has permissions to the Cognos FSR database inSQL Server. Click on the Connect button to verify a successful connection.Once connected, the unique database identifier will be displayed which ishow the migration tool will remember your source Cognos FSR database.Click Next to move to Step 2 in the wizard.

8. CDM Settings. Click Browse and navigate to the location where the CognosDisclosure Management server web services are installed. Choose the masterkey file MasterKey.txt. The typical location for this file isC:\inetpub\wwwroot\CognosDM-Server\MasterKey.txt. Select a databaseprovider from the Provider drop-down list based on whether your CognosDisclosure Management database is deployed on Microsoft SQL Server or IBMDB2. Enter the server name in the Server Name field and the CognosDisclosure Management database name in the Database field. If your databaseprovider is SQL Server, select Use Integrated Security if you are connecting toyourCognos Disclosure Management database using Windows authentication.If you are not using Windows authentication, enter your SQL login andpassword to connect to your Cognos Disclosure Management database. If yourdatabase provider is DB2, enter your DB2 login and password to connect toyour Cognos Disclosure Management database. Ensure your user account haspermissions to the Cognos Disclosure Management databases.

Important: If your Cognos FSR database is XBRL-enabled and you chose toinstall the XBRL feature when you installed Cognos Disclosure Management,


then select Enable XBRL Migration and enter the connection details for theIBM

®

Cognos®

Disclosure Management XBRL database.Click Next to move to Step 3 in the wizard.

9. CDM Authentication. Enter the username and password of the CognosDisclosure Management application user you created for migration purposes.Click Log in to verify a successful log in. This application user will be theuser for the duration of the migration process. Click Next to move to Step 4 inthe wizard.

10. Migration Options.a. Report Object Options. If you select the Migrate Dependent Objects

check box, the migration tool will determine the shared objectdependencies for reference objects in your selected reports. If a referenceobject in your selected report is dependent on a shared object in a differentreport, the migration tool will migrate that shared object first. This optionalso handles dependencies for global source and destination variableswhere the report with the source variable is migrated first.You can select Add Default Page Setup Object to add a page setup objectwith default page setup settings similar to Cognos FSR such as narrowmargins and page layout. The default page setup object will be added tothe beginning of the first section in your migrated report if your report hasno page setup object, no printable page setup object, or if the firstprintable object in your report does not have a preceding printable pagesetup object. By selecting this option, generating the report in CognosDisclosure Management will receive the same default page setup settingsapplied for the printable objects in your report that do not have apreceding page setup object in Cognos FSR.

b. Word Object Conversion Options. This section provides options to updatethe content or formatting in your Word objects as they are migrated tohelp produce generated reports in Cognos Disclosure Management similarto your generated reports in Cognos FSR, based on the report generationdifferences between the two products. You can enable the check boxRemove Section Breaks to remove all section breaks you have insertedmanually in your Word object content and reduce the number of pagesthat are generated. This applies only to printable Normal Word objects.You can select Remove Empty Paragraphs at End of Document to removeempty paragraphs at the end of your Word object content. This willremove up to two empty paragraphs in a printable Normal Word objectand up to one empty paragraph in a printable Header or Footer Wordobject. This will reduce the number of empty paragraph breaks betweenobjects that are generated.

c. Excel Object Conversion Options. This section provides options to updatethe content or formatting in your Excel objects as they are migrated to helpproduce generated reports in Cognos Disclosure Management similar toyour generated reports in Cognos FSR based on the report generationdifferences between the two products. You can enable the check boxFormat Cells within the Printable Range to Wrap Text to format all cellsin your printable Excel range (##RS/##RE) by setting the Wrap Textproperty to true. This controls the row height setting to be set to At Leastinstead of Exactly when your Excel range is generated to a Word table.This can help reduce the row height difference and ensure the cell contentdoes not get cut off in the generated report.You can select Enforce Keep Table With Next to have the migration toolset the object enforcement setting Keep with Next Paragraph/Table inCognos Disclosure Management to correspond to the behavior in Cognos


Management 10.2.6

FSR when a table does and does not break across the page. When youselect this option, the option Add Default Page Setup Object is alsoautomatically selected as the two options work together for theenforcement setting to apply as expected in report generation. If the optionis not selected, by default, the migration tool will set the objectenforcement setting Keep with Next Paragraph/Table to true for all theExcel objects in the report.

d. Query Options. This section provides the option to change the DisplayMissing Data as '<Label>' from the default empty cell to 0 for OLAP dataqueries. If you have the DisplayMissingValuesAsZero configuration key setto true in your Cognos FSR client, select the Display Missing Values asZero check box in the migration tool.

e. Date Conversion Options. This section provides the option to change thetime zone setting to use in the conversion of your Cognos FSR local datesto Coordinated Universal Time (UTC). The default conversion will use thesame time zone setting of your Cognos FSR database server. To change thedefault to another time zone setting, select the Use Specific Time Zonecheck box and select the time zone from the drop-down list.

Important: Cognos FSR does not store the time zone with the date in thedatabase. As a result, conversion of Cognos FSR local dates to UTC whenmigrating to Cognos Disclosure Management cannot be completelyaccurate.v If you are in the same time zone as your Cognos FSR database server,

you do not need to select the Use Specific Time Zone check box. Theonly accuracy issue that cannot be accounted for is Daylight SavingsTime (DST) for historical dates.

v If you and other users are in a different time zone than the databaseserver, select the Use Specific Time Zone check box and select the timezone setting that applies to the majority of users. This will mean all thedates that are migrated from Cognos FSR to Cognos DisclosureManagement will be converted to UTC using your selected time zone.

Manual updates can be made to your migrated date properties ifnecessary.

f. Security Migration Options. This section provides the option to importyour Cognos FSR Windows users into Cognos Disclosure Management.Select Migrate Windows Users and click Add Domain. Enter the Domain,User Name and Password and then click Test Connection. This is thedomain user that will be used to connect to Active Directory and importyour Cognos FSR Windows users for the specified domain into CognosDisclosure Management. If you have windows users from multipledomains in your Cognos FSR database, click Add Domain again to enterthe next one. Click Next to move to Step 5 in the wizard.

11. Select Reports. The reports navigation tree will display all of your reports,including the object hierarchy under each report. Select an individual report ormultiple reports to migrate under a report group. You can also choose to selectall reports under a report group by selecting the entire report group. Whenfirst migrating a report, you can only select at report level. You can only selectat object level to try again on a subsequent run of the migration tool if thatobject was not able to migrate. For best performance, migrate one report at atime or batch migration of your reports by migrating up to five reportsinstead of selecting all of your reports. On subsequent runs of the migrationtool, you will see your previously selected reports, and all objects in thatreport in the reports navigation tree, as disabled. If an object under that report

Chapter 5. Running the migration tool 25

is not disabled and the check box is not selected, it means the migration toolwas unable to import it into Cognos Disclosure Management. Click Next tomove to Step 6 in the wizard.

12. Select Taxonomies.

Important: This step will only be enabled if your Cognos FSR database isXBRL-enabled and you have enabled XBRL migration in the CDM Settingsstep. Otherwise, this step will be skipped in the migration wizard.The taxonomies navigation tree will display a list of the taxonomy names inyour Cognos FSR database. You can select more than one taxonomy; in themigration engine, taxonomies will be imported one at a time.a. Import taxonomy from local files. Select the taxonomy and click Add

Taxonomy > Add Files For Taxonomy. Navigate to the folder where yousaved your taxonomy files locally on the Cognos Disclosure Managementserver as part of the migration prerequisites. Select your taxonomy filesand set which file will be the entry point. The default detection of theentry point is the schema file. Click Next to move to Step 7 in the wizard.

b. Import taxonomy from URL. You can choose this method if yourtaxonomy is in the Cognos FSR Cache Manager such as a taxonomy witha folder structure or one that is available for download from the Internet.Select the taxonomy and click Add Taxonomy > Add URL For Taxonomy.Type the URL for the entry point. As part of migration, the Cognos FSRCache Manager is migrated first, before the import of taxonomies. Thetaxonomy will be downloaded from the Internet as part of the importprocess if not found in the migrated Cache Manager. Click Next to moveto Step 7 in the wizard.

13. Select Projects.

Important: This step will only be enabled if your Cognos FSR database isXBRL-enabled and you have enabled XBRL migration in the CDM Settingsstep. Otherwise, this step will be skipped in the migration wizard.a. The reports navigation tree will display a list of the XBRL configured

reports in your Cognos FSR database. If the report has already beenmigrated or if you have already selected it for migration, it will be enabledin the navigation tree. You can add one or more projects for your selectedXBRL report by configuring it with different taxonomies that may beassociated with your report. You can choose to either add projectsindividually or add all projects with defaults:v Select the report and click Add Project. By default, the Taxonomy tab

will be selected with the current associated taxonomy for this report.v Click Add All Projects to automatically have the migration tool add all

projects in your current session with defaults, provided that: the reporthas already been migrated or is selected for migration, the associatedtaxonomy has already been migrated or is selected for migration, and aproject with same report and taxonomy has not already been migratedor added.

b. After you add a project, the lower panel shows the object hierarchy for thecurrent project. Only the objects with XBRL tags in this report will bedisplayed. The project and the objects will all be selected by default formigration. An object will show as migrated if migration of the tags for theobject completed successfully. If no tags or only some of the tags weresuccessfully migrated for an object, you can select the object and re-run themigration tool.


Management 10.2.6

14. Run Migration. Click Start Migration. The Progress Log will display theprogress of the migration. You can toggle the Successful, Warnings and Errorsbuttons on or off in the viewer. When the migration process has completed,the Next button will become enabled. Click the Next button.

15. Finish. A migration summary will display the results of the migration. Youcan click the Open Log File button to open the log file in the Log Viewerwhich will parse the log file into columns from which you can Filter, Sort,and Group By for easier search and readability when analyzing andtroubleshooting the migration. You can click the Migrate Other Reportsbutton to do another migration run for another report, taxonomy or projectwithout having to exit the migration tool.

Chapter 5. Running the migration tool 27


Management 10.2.6

Chapter 6. Resolving report objects

The migration tool will import all objects for each report you have selected. If thereis an issue with an object, the tool will report it on the Progress Log viewer, logfile and will continue importing the next object.

About this task

For each report that you have selected, the migration tool will import objectcontent, properties, dependent objects, workflow, data sources, data queries, queryvariables, and associate queries with reports and objects.

During report object migration, the following cases are intentionally skipped andlogged in the migration log:v Relational source with unsupported server types: Microsoft Access Connection.

These queries are ignored. You will first need to convert to a supported type.v Essbase member specification in report syntax. The OLAP query is still migrated

but you will need to edit the query and convert to a MDX script.v Orphan workflow state. Workflow state is migrated with a "(Deleted)" suffix and

object workflow is still migrated.v Orphan user assigned to workflow state. Object workflow is still migrated but

with no user assigned.v Orphan query variables referenced in data queries. The query is still migrated

with the query variable where the query variable is set with a default value. Youwill need to edit the report query variable value to resolve the query executionerror.

v OLAP query that is defined without at least one dimension in the row axis andone on the column axis. The query is still migrated but you will need to edit thequery to resolve query validation and execution errors.

v External links and pivot tables with external data sources. Excel object content isstill migrated with the external references. You will need to create a data sourceand query and convert the external references if applicable to point to the queryresult sheet for the data to refresh.

The report object will be enabled in the Select Reports tab for that report in thewizard for you to try migrating again if errors were encountered. If you receiveone of these warnings and no other errors, the report object will be marked asmigrated and manual resolution will be required. However, if there is a need toremigrate an object to keep section breaks, for instance, you can remigrate it bydeleting the migrated object in IBM

®

Cognos®

Disclosure Management first.

Procedure1. Errors encountered will be displayed on the Progress Log viewer and detailed

messages are logged to the log file Migration.YYYY-MM-DD_HH.MM.SS.log in thelog folder <InstallationFolder>\MigrationTool\LogFiles.

2. Double-click the Ibm.CognosDM.Migration.UI.exe file and click the Open LogFile button. When the log viewer opens, click Load File and navigate to<InstallationFolder>\MigrationTool\LogFiles and select the correct migrationlog file. You can filter on start time if you ran more than one migration in asession. You can also Filter, Sort or Group By using the columns to findspecific warnings or errors.


3. Depending on the type of error found, you can:a. Update the object in the IBM Cognos FSR client and then select the object

and import it again. You will now be able to select the object in the reportsnavigation tree under that report.

b. Do nothing, and bypass the object by leaving the check box clear in themigration tool. You can add the object manually using Cognos DisclosureManagement, if you wish.

c. If a reference object was not added in your imported report, ensure thatMigrate Dependent Objects is selected and select those reference objects inthe reports navigation tree again. The shared objects that the referenceobjects are referencing will automatically be selected for you in the treeview. Then import those objects again.

d. If an object is marked as migrated in the Select Reports tree view but youencounter an issue with the migrated object in Cognos DisclosureManagement, you can delete the migrated object within the CognosDisclosure Management client. Then you can resolve the issue in CognosFSR and change the migration options selection in the user interface. Forinstance, you can choose not to remove section breaks and you can selectthe report object and try migrating it again.

To review an up-to-date list of migration errors and how to resolve them, seeResolving migration errors (http://www.ibm.com/support/docview.wss?uid=swg21652667).

Resolving desktop publishing tags in report objectsThe migration tool will import desktop publishing tags into your report objects.Any tags that are not migrated will have to be resolved.

About this task

For each report that you have selected, your desktop publishing tags will beimported as part of migrating your report objects.

Important: If you have upgraded from an older version of IBM Cognos FSR, youmust run the data conversion procedure to upgrade your desktop publishing tagsthrough the Cognos FSR client prior to migration.

The Tags Explorer and report generation output to Adobe InDesign in IBM®

Cognos®

Disclosure Management has been enhanced and will not produce theexact same output as Cognos FSR. For further information on how this featureworks, see the IBM Cognos Disclosure Management User Guide. In the migration oftags, the migration tool will convert and transform tags to so they are consistentwith the functionality in Cognos Disclosure Management.

Two instances of this include:v Word tags with the same name and same associated style will be reusedv Generated output will have XML tags representing your object hierarchy: report

name, object name, section name and tag name

During report object migration, the following case is intentionally skipped andlogged in the migration log:

Excel tag references As object in sheet but no chart or picture was found on thetagged sheet


Management 10.2.6

http://www.ibm.com/support/docview.wss?uid=swg21652667

Applicable tags also include:v Word tags that are orphansv Word tags which reference mixed content such as table and text

The report object will be enabled in the Select Reports tab for that report in thewizard for you to try migrating again if errors were encountered. If you receivevalid warnings and no other errors, the report object will be marked as migratedand manual resolution will be required.


messages are logged to the migration log file YYYY-MM-DD_HH.MM.SS.log in thelog folder InstallationFolder>\MigrationTool\LogFiles.


3. Depending on the type of error found, you can:a. Update the tag in the Cognos FSR client and then select the object and

import it again. You will now be able to select the object in the SelectReports tab in the user interface by selecting the report object in the treeview.

b. Do nothing, and bypass the object by leaving the check box clear in themigration tool. You can add the tags for that object manually using CognosDisclosure Management.

c. If your tag did migrate but had a valid warning, update the tag manuallyusing Cognos Disclosure Management.

d. If an orphan tag was migrated, then delete the tag using Cognos DisclosureManagement and add the tag if you want the orphan tag to be treated as avalid tag.

e. If a tag references mixed content, you will receive a report generation errorin Cognos Disclosure Management. Update the tag manually using CognosDisclosure Management to resolve the report generation error.

f. If your tags did not migrate and you receive a message that the report'sdesktop publishing tags were not upgraded, verify the data conversionprocedure was run for your report. If this is the case, run the dataconversion procedure in Cognos FSR and delete the already migrated reportin Cognos Disclosure Management. You can then re-run migration for thisreport and the desktop publishing tags should migrate.

Related concepts:Chapter 7, “Manual updates,” on page 35Some manual changes are necessary to complete the migration from IBM CognosFSR 6 to IBM

®

Cognos®


Resolving XBRL tags in report objectsThe migration tool will import XBRL tags in your report objects based on theprojects you selected to be created in the migration wizard.

Chapter 6. Resolving report objects 31

About this task

For each report that you have selected, the migration tool will import XBRL objecttags based on the associated report and taxonomy for that project. This means themigration engine will only migrate all applicable tags in that report object. If allapplicable tags cannot be migrated for that object, tags are rolled back for thatobject. Non-applicable tags are those that are not supported in IBM

®

Cognos®

Disclosure Management or those that are deemed invalid for Cognos FSR.Non-applicable tags are intentionally skipped in a report object and are logged inthe migration log for the following cases:v Assigned to a query tagged headerv Assigned to a Cognos FSR time period that is out of scope for the report. This

means that the tag's time period is not assigned for the report in Cognos FSRXBRL > Configure XBRL > Usable Filters

v Assigned to a Cognos FSR time period that is a Forever typev Assigned to a Cognos FSR scale with precision accuracyv Assigned to a Cognos FSR scale with a multiply by setting greater than 12

zeroesv Assigned to an element that cannot be found in the taxonomyv Assigned to a dimension that cannot be found in the taxonomyv Assigned to an explicit dimension member that cannot be found in the

taxonomyv Assigned to an unsupported typed dimension valuev Assigned to a text block item, but the cell value does not contain ##RS or ##XS,

where the latter is not within a printable range ##RS/##REv Assigned to a context with dynamic aspect where the query variable could not

be replaced with a static aspect.

Applicable tags that are migrated but an XBRL setting from Cognos FSR is ignoredincludes the following case:

Double or triple negation set for a tagged cell in your Cognos FSR report object.The tag will be migrated to Cognos Disclosure Management with negation.Multiple negation settings or the net effect of a stacked negation (double or triplenegation) where they can cancel one another out is ignored.

Applicable tags also include orphan tags which are migrated and logged in themigration log to indicate that an orphan tag was found.

Applicable tags are migrated per report object in batches. As a result, it is possiblefor partial tag migration to occur. If a batch fails due to an XBRL tag validation,these tags will be rolled back. The report object will be enabled in the SelectProjects tab for that project in the wizard for you to try to migrate your tags again.If a tag fails content validation, an error message will be logged and the tag willstill be migrated. You can then refresh the project to see these content validationmessages and resolve them using Cognos Disclosure Management.

To resolve XBRL tagged objects that the migration tool was not able to import,perform the following steps:


Management 10.2.6




3. Depending on the type of error found, perform the following actions:a. Update the tag in the Cognos FSR client and then select the object and

import it again. You will then be able to select the object by selecting theproject and navigating to the object in the object hierarchy tree displayedunder that project.

b. Do nothing, and bypass the object by leaving the check box clear in themigration tool. You can add the tags for that object manually using CognosDisclosure Management.

c. If your tag did migrate but had a valid warning where an XBRL settingfrom Cognos FSR was ignored, update the tag manually using CognosDisclosure Management.

d. If an orphan tag was migrated, then delete the tag using Cognos DisclosureManagement and add the tag if you want the orphan tag to be treated as avalid tag.

Related concepts:“Migration scope” on page 1The migration tool provides a basic migration of data to ensure you have a startingpoint after upgrading from IBM Cognos FSR 6 to IBM

®

Cognos®

DisclosureManagement.Chapter 7, “Manual updates,” on page 35Some manual changes are necessary to complete the migration from IBM CognosFSR 6 to IBM

®

Cognos®


Resolving XBRL tuples in report objectsThe migration tool will import XBRL tuples in your report objects.

About this task

The migration sequence is migration of the tuples and then migration of the tagsassigned to elements that are part of each tuple, attaching the tags to the tuples.

Important: The Cognos FSR Tuple Explorer displays in tagged order andgenerates an instance document for the tuple using the part order specified in theschema regardless of group type (Sequence, Choice, or All). After migration, thedisplay in the IBM

®

Cognos®

Disclosure Management Tuple Explorer will displaybased on the part order specified in the schema as opposed to the tagged orderdisplay in Cognos FSR. After migration, the instance document will match theorder displayed in Cognos Disclosure Management.

For each report that you have selected, the migration tool will import XBRL tuplesand then the tags assigned to elements that are part of these tuples based on theassociated report and taxonomy for that project. This means the migration engine

Chapter 6. Resolving report objects 33

will only migrate all applicable tuples in that report object. If all applicable tuplescannot be migrated for that object, they are rolled back for that object and the tagsattached to these tuples are not migrated.

Non-applicable tuples are those that are not supported in Cognos DisclosureManagement or those that are deemed invalid for Cognos FSR. Non-applicabletuples are intentionally skipped in a report object and are logged in the migrationlog for the following case:v A tuple group defined in the schema with occurrence indicators, minimum or

maximum. For instance, a tuple with the group type Sequence with a minimumoccurrence of 2. A tuple in Cognos FSR is valid provided the group occursexactly once and the group contains only item parts and tuple parts.

Applicable tuples also include empty tuples and tuples with less than theminimum amount of content. The tuples are still migrated and Cognos DisclosureManagement will identify any invalid content in the Tuple Explorer, which youcan then resolve.

To resolve XBRL tuples and tags attached to these tuples that the migration toolwas not able to import, perform the following steps:



2. Double-click the Ibm.CognosDM.Migration.UI.exe file and click Open Log File.When the log viewer opens, click Load File and navigate toInstallationFolder>\MigrationTool\LogFiles and select the correct migrationlog file. You can filter on start time if you ran more than one migration in asession. You can also Filter, Sort, or Group By using the columns to findspecific warnings or errors.

3. Depending on the type of error found, you can either:a. Update the tag attached to the tuple in the Cognos FSR client for that object

and then select the object and import it again. You will now be able toselect the object in the Select Projects page in the user interface by selectingReport, the project and then finding the object in the panel that displays theobject hierarchy.

b. Do nothing, and bypass the object by leaving it deselected in the migrationtool. You can add the tuples and tags attached to these tuples for that objectmanually using the Tuple Explorer in Cognos Disclosure Management.

c. If your tag attached to a tuple did migrate but had a valid warning wherean XBRL setting from Cognos FSR was ignored, update the tag manuallyusing the Tuple Explorer in Cognos Disclosure Management.

d. If the tuple had validation messages such as invalid content, resolve itmanually using the Tuple Explorer in Cognos Disclosure Management.

Related concepts:Chapter 7, “Manual updates,” on page 35Some manual changes are necessary to complete the migration from IBM CognosFSR 6 to IBM

®

Cognos®



Management 10.2.6

Chapter 7. Manual updates

Some manual changes are necessary to complete the migration from IBM CognosFSR 6 to IBM

®

Cognos®

Disclosure Management 10.2.6.Related tasks:“Resolving desktop publishing tags in report objects” on page 30The migration tool will import desktop publishing tags into your report objects.Any tags that are not migrated will have to be resolved.“Resolving XBRL tags in report objects” on page 31The migration tool will import XBRL tags in your report objects based on theprojects you selected to be created in the migration wizard.“Resolving XBRL tuples in report objects” on page 33The migration tool will import XBRL tuples in your report objects.

Post migration tasksTo complete the migration from IBM Cognos FSR 6 to IBM

®

Cognos®

DisclosureManagement 10.2.6, you must complete some manual steps.

Procedure1. Log in to Cognos Disclosure Management with the application user you used

to run the migration tool.2. Update the following items:

a. Page Orientation: If you have sections in your Cognos FSR 6 reports withOrientation = Landscape and it does not have a Page Setup Word object inthat report section, insert a Page Setup Word object. All imported Excel andWord objects will have, by default, the enforcement setting PageOrientation enabled.

b. Update report objects referencing TOC or Note variables to the changednames where the migration log indicated the variable name was removed ofunsupported characters.

c. Update report objects containing reference variables and comments to ashorter length where the migration log indicated the length is too long. Thiswill apply to variable names and variable comments where allowedmaximum lengths in Cognos Disclosure Management are 50 and 500respectively, whereas Cognos FSR allows longer lengths.

d. Add query variables where the migration log indicated the query variablename was too long or had unsupported characters.

3. With the assistance of the IBM Professional Services Department, configure andset up the following to complete the migration and to generate reports withyour dynamic content:a. User Permissions. Imported Cognos FSR users are imported with applicable

permissions at application and report level where Cognos FSR permissionshave been mapped to near or equivalent mappings in Cognos DisclosureManagement. You can edit application and report level permissions for theimported users as needed. You can also create groups and assign users withthe same permissions to those groups.


Important: Reset the password for imported SQL users from Cognos FSR.They will have been imported and set with the same initial defaultpassword: Passw0rd.

b. Essbase report scripts. Convert member specification to MDX script.c. Relational sources with unsupported server types. Convert to a relational

query. For instance, Microsoft SQL Server, Oracle or DB2 or an externalExcel file source.

d. Relational sources with OLE DB and ODBC connections to 32-bit provideror DSN connection string. Convert to a 64-bit provider and DSN-lessconnection string respectively or convert to a relational query.

e. Add Oracle HFM data sources and associate with migrated report objectcontent with Oracle HFM formulas.

f. Orphan workflow users and states. Update workflow states and objectworkflows.

g. Expiration policy. A default cache expiration policy is set for all migratedOLAP and relational queries named Expiration Policy for Migration Query.You can edit this policy or create your own. For migrated external excel filequeries, it is set by default to the expiration policy installed by CognosDisclosure Management named Whenever External Excel File is Modified. Youcan change this to a different policy or create your own.

h. External links. Convert external links in your Excel object to an externalExcel file data source and query in Cognos Disclosure Management andassociate the query with your report. In your Excel object, insert the newquery and update all formulas referencing the external link to the queryresult sheet instead. You can locate the formulas with the external referencesby searching the workbook's formulas for the left square bracket, sinceexternal references use brackets to enclose the workbook name.

i. Pivot tables with external data sources. Convert pivot tables with externaldata sources in your Excel object by creating a data source and query inCognos Disclosure Management and associate the query with your report. Inyour Excel object, insert the new query and change your pivot data source topoint to the range on the query result sheet instead.

4. Update the following using the Cognos Disclosure Management client tocomplete the migration of tagged content for output to Adobe InDesign:a. For tags purposefully skipped by the migration tool, resolve and add

manually.b. For tags that did migrate but had a valid warning, resolve and update

manually.c. For tags associated to the default style Migration Default Style, you can

rename the default style or create your own.5. Update the following items for your XBRL migrated reports to complete the tag

migration and to validate generations of your instance documents:a. Run refresh of project items for your migrated XBRL reports and resolve the

validation errors such as orphan tags that were carried over from CognosFSR.

b. For XBRL tags intentionally skipped by the migration tool, resolve and addthem manually.

c. For XBRL tags that did migrate but had a warning, resolve and updatemanually.

d. For tagged items to empty cells, the tag will have been migrated withdefault string to nil transformation. If you prefer to generate tagged


Management 10.2.6

empty cells as zero or omit them, update the default transformation setnamed my_Fact Value String to Nil for Empty Cell.

e. For XBRL tuples or tags attached to the tuple that are purposefully skippedby the migration tool, resolve and add manually to the Tuple Explorer.

f. For XBRL tuples or tags attached to the tuple that did migrate, but had avalid warning, resolve and update manually in the Tuple Explorer.

Chapter 7. Manual updates 37


Management 10.2.6

Notices

This information was developed for products and services offered worldwide.

This material may be available from IBM in other languages. However, you may berequired to own a copy of the product or product version in that language in orderto access it.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service. This document maydescribe products, services, or features that are not included in the Program orlicense entitlement that you have purchased.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law: INTERNATIONALBUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFNON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULARPURPOSE. Some states do not allow disclaimer of express or implied warranties incertain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.


Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Software GroupAttention: Licensing3755 Riverside Dr.Ottawa, ONK1V 1B7Canada

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.


Management 10.2.6

This Software Offering does not use cookies. However, depending upon theconfigurations deployed, this Software Offering may use other technologies tocollect personally identifiable information. These technologies collect each user'sv namev user namev passwordv profile namev personally identifiable information other than name, user name, password,

profile name and position

for purposes ofv session managementv authenticationv enhanced user usabilityv single sign-on configurationv usage tracking or functional purposes other than session management,

authentication, enhanced user usability and single sign-on configuration

These technologies cannot be disabled.

If the configurations deployed for this Software Offering provide you as customerthe ability to collect personally identifiable information from end users via cookiesand other technologies, you should seek your own legal advice about any lawsapplicable to such data collection, including any requirements for notice andconsent.

For more information about the use of various technologies, including cookies, forthese purposes, see IBM's Privacy Policy at http://www.ibm.com/privacy andIBM's Online Privacy Statement at http://www.ibm.com/privacy/details in thesection entitled "Cookies, Web Beacons and Other Technologies" and the "IBMSoftware Products and Software-as-a-Service Privacy Statement" athttp://www.ibm.com/software/info/product-privacy.

Trademarks

IBM, the IBM logo and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at “ Copyright andtrademark information ” at www.ibm.com/legal/copytrade.shtml.

The following terms are trademarks or registered trademarks of other companies:v Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered

trademarks or trademarks of Adobe Systems Incorporated in the United States,and/or other countries.

v Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

Notices 41

http://www.ibm.com/privacy

http://www.ibm.com/privacy/details

http://www.ibm.com/software/info/product-privacy

http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml


Management 10.2.6

Index

AAdobe InDesign 17authentication

specifying for IBM Cognos Disclosure Management 23

Cclient

versions for migration 1Cognos FSR Database Upgrade Utility 17CognosDM database 19CognosDMCache database 19CognosDMXBRL database 19comments

updating 35custom groups

migration scope 1

Ddatabase for IBM Cognos FSR 6

setting up user account for 19upgrading 17versions for migration 1

database identifiersgenerating unique 18overview 9

databases for IBM Cognos Disclosure Managementsetting up user account for 19versions for migration 1

desktop publishing tagsresolving in report objects 30upgrading 17

duplicatesreducing during migration 9

Ffunctionality 12

Hhierarchy

migration scope 1

IIBM Cognos Disclosure Management

installing 19migrating to 1setting up user account for migration 19

IBM Cognos FSR 6migrating from 1setting up user account for migration 19upgrading database to Version 6.6.1 17

identifiersSee database identifiers

MMicrosoft Office 17migration

limitations 7main steps 12manual steps after use of migration tool 35multiple databases 9overview 1planning for 15

migration toolinstalling 21overview 1resolving report objects that were not imported 29running 23supported versions of databases, servers, and clients 1

Nnote variables

updating 35

Oobject properties

migration scope 1objects 1

Ppage orientation

updating 35Page Setup Word object

using to update page orientation 35prerequisites

IBM Cognos Disclosure Managementprerequisites 17

migration toolprerequisites for upgrading 17

upgrading IBM Cognos FSR 6 17

Qquery variables

migration scope 1updating 35

Rreference variables

updating 35references

migration scope 1report groups

migration scope 1report objects

migrating to IBM Cognos Disclosure Management 23migration scope 1resolving desktop publishing tags in 30


report objects (continued)resolving report objects that were not imported 29resolving XBRL tags in 32resolving XBRL tuples in 33updating 35upgrading 17

reportsmigrating to IBM Cognos Disclosure Management 23migration scope 1planning for migration of 15

Sservers

specifying for IBM Cognos Disclosure Management 23versions for migration 1

shared objectsmigration scope 1

snapshotsmigration scope 1

Ttable of contents variables

updating 35taxonomies

migrating to IBM Cognos Disclosure Management 23uploading 20

Uuser accounts

overview 19

user accounts (continued)setting up to connect IBM Cognos Disclosure Management

databases 19setting up to connect to IBM Cognos FSR 6 database 19

usersmigrating to IBM Cognos Disclosure Management 23migration scope 1temporary for migration 12updating permissions 35

Vvariables

migration scope 1

Wworkflow

temporary template for migration 12updating 35

XXBRL

CognosDMXBRL database 19migration scope 1planning for migration of 15resolving tags in report objects 32resolving XBRL tuples in report objects 33uploading taxonomies for 20


Management 10.2.6

IBM Cognos Disclosure Management Version 10.2.6: Migrating...

Documents

Transcript of IBM Cognos Disclosure Management Version 10.2.6: Migrating...