Page551 PDF Cognos

IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business
Warehouse
Product(s): IBM Cognos 10; Area of Interest: Infrastructure
Daniel Wagemann Cognos Proven Practices Advisor IBM Rich Borucki Solution Specialist IBM Pierre Valiquette Software Engineer IBM This document is intended to provide a single point of reference for techniques and product behaviours when dealing with SAP NetWeaver Business Warehouse (SAP BW) as a data source in IBM Cognos 10. View more content in this series Contributors This effort would not have been possible without contributions from Patricia Defosse, Linda Whitney, and Agnes Chau. Skill Level: Advanced Date: 07 Jan 2011
Introduction
Purpose This document is intended to provide a single point of reference for techniques and product behaviours when dealing with SAP NetWeaver Business Warehouse (SAP BW) as a data source in IBM Cognos 10. Applicability Generally speaking, the practices and methods noted within the IBM Cookbook for IBM Cognos 8.4 for use with SAP NetWeaver Business Warehouse are applicable to
Copyright IBM Corporation 2011 IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse Trademarks Page 1 of 25
developerWorks
ibm.com/developerWorks/
your IBM Cognos 10 on SAP BW environment. Hence the guidelines mentioned in this document can be considered an addendum, or delta practices, and are specific to IBM Cognos 10 with SAP BW. The techniques and product behaviours outlined in this document apply to: 1. IBM Cognos 10 version 10.1 2. SAP BW Query Designer version 7.0 Exclusions and Exceptions The techniques and product behaviours outlined in this document may not be applicable to previous or future releases.
SAP BW Objects and Queries

IBM Cognos 10 leverages the SAP BW investment within your organization by providing access to the SAP BW metadata and business content. The guidelines and practices for the design and use of SAP BW objects and queries can be found within the document entitled IBM Cookbook for IBM Cognos 8.4 for use with SAP NetWeaver Business Warehouse located at http://www.ibm.com/developerworks/ data/library/cognos/page468.html, and are generally applicable when accessing SAP BW with IBM Cognos 10. In addition to the guidelines noted within the SAP BW objects and queries section of the above referenced cookbook, IBM Cognos 10 provides support for time-dependent hierarchy structures. The following describes time-dependent hierarchy structures, and how they are depicted in IBM Cognos 10. Time-Dependent Hierarchy Structures Some SAP BW users require the ability to create reports depicting hierarchy structures that are valid for a specific time period; therefore they need to create the hierarchy structure as a time-dependent. For example, assign retailers to different geographies at different times within the context of a hierarchy.
IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse
Page 2 of 25
developerWorks
Figure 1: This image shows time-dependent structures Algeria and Morocco
As the example above illustrates, this SAP hierarchy represents retailers in different geographic locations. This illustration shows how the retailer located in the country of Algeria from the time period 01-01-2000 to 31-12-2004 has ceased operations at the end of 2004, and was replaced by new dealer located in Morocco, which started to log transactions in 01-01-2005. Notice in Figure 2, for the characteristic ZD_CCUST (Retailer) in SAP BW, under the Hierarchy tab, the option Time-Dependent Hierarchy Structure has been selected.
Page 3 of 25
developerWorks
Figure 2: Time-Dependent Hierarchy Structure is defined within the SAP BW InfoObject
Since ZD_CCUST (Retailer) contains a time-dependent hierarchy structure, we can see in Figure 3 that for the hierarchy named Retailer TimeDep1, different validity dates are assigned for countries Algeria and Morocco.
Page 4 of 25
developerWorks
Figure 3: Time-dependent structures defined with different validity dates
IBM Cognos 10 allows users to visualize and interact with the SAP BW timedependent hierarchy structures. Notice in the image Figure 4, how the timedependent hierarchy structures are depicted in the IBM Cognos 10 Framework Manager model, and can be leveraged as alternate hierarchies within IBM Cognos 10 BI.
Page 5 of 25
developerWorks
Figure 4: Alternate hierarchies are arranged by validity dates
General Principles when Accessing Time-Dependent Hierarchy Structures Since the time-dependent hierarchy structures are depicted in the IBM Cognos 10 Framework Manager as alternate hierarchies, import only the definitions of the hierarchies you need. This will help to optimize the IBM Framework Manager import process when accessing metadata from SAP BW.
IBM Cognos 10 Framework Manager

IBM Cognos 10 Framework Manager provides the metadata model development environment in IBM Cognos 10, and is the starting point for IBM Cognos 10 and SAP BW integration. The guidelines and practices to leverage SAP BW metadata within IBM Cognos Framework Manager can be found within the document entitled IBM Cookbook for IBM Cognos 8.4 for use with SAP NetWeaver Business Warehouse located at http://www.ibm.com/developerworks/data/library/cognos/page468.html, and are generally applicable when accessing SAP BW metadata with IBM Cognos 10 Framework Manager. In addition to the guidelines noted within the metadata modelling section of the above referenced cookbook, IBM Cognos 10 Framework Manager provides the ability to define a package to use Dynamic Query Mode (DQM).
Page 6 of 25
developerWorks
Dynamic Query Mode

The IBM Cognos 10 architecture provides the ability to utilize two query modes: Compatible Query Mode Dynamic Query Mode Compatible Query Mode triggers the traditional query methods as utilized in IBM Cognos 8.4, and users of this mode can expect similar or slightly improved response times in IBM Cognos 10. This mode is the default processing method for a package unless DQM is specifically defined for the package in IBM Cognos 10 Framework Manager. Dynamic Query Mode is enabled at the package level using IBM Cognos 10 Framework Manager or Self-Service Package Wizard and is leveraged by IBM Cognos 10 solutions such as Reports Studio, Business Insight Advanced, and Query Studio. DQM is an enhanced, Java-based query mode which offers the following key capabilities: Query optimizations to address query complexity, data volumes, and timeliness expectations with improved query execution techniques. Significant improvement for complex OLAP queries through intelligent combination of local and remote processing and better MDX generation. Security-aware caching. New data Interfaces leveraging 64 bit processing. Ease of maintenance with query visualization. Both the Compatible and Dynamic query modes in IBM Cognos 10 utilize patented MDX technology to send optimized Multi-dimensional Expressions (MDX) specifically for SAP BW, through the SAP BW OLAP BAPI interface to access SAP BW data, and is SAP Certified Integration with SAP NetWeaver. To better understand the benefits of the Dynamic Query Mode and the steps necessary to implement the DQM, refer to the Dynamic Query Guide provided in the IBM Cognos 10 installation documentation or the IBM Cognos 10 Dynamic Query Cookbook located at: http://www.ibm.com/developerworks/data/library/cognos/ infrastructure/cognos_specific/page529.html. The IBM Cognos 10 Dynamic Query Cookbook will contain additional information for the following topics: IBM Cognos 10 architecture. Definitions and variances between Compatibility and Dynamic Query Modes. Requirements for connectivity to all supported OLAP data sources. Process to define a package to use DQM with IBM Cognos Framework Manager.
Page 7 of 25
developerWorks
IBM Cognos 10 configuration settings for all supported data sources. Administration features specific to DQM. IBM Cognos 10 caching. Debugging and troubleshooting the DQM.
SAP BW Specific Configuration Files within IBM Cognos 10

When accessing SAP BW using Dynamic Query Mode, many of the principles which applied to IBM Cognos 8.4.1 are still in effect. It should be noted however that the configuration entries are located in different configuration files. Some new entries have been added and some entries are no longer required for DQM. The two main configuration files for Dynamic Query Mode are xqeodp.config.xml, located under the configuration directory, and bw.properties, located under configuration\xqe directory. By default, xqeodp.config.xml will be suffixed by example. Simply remove the -example and the file will take effect upon startup of the query service. XQEODP.CONFIG.XML This file contains the main configuration file which most will be familiar with and their explanation can be found within the IBM Cookbook for IBM Cognos 8.4 for use with SAP NetWeaver Business Warehouse located at http://www.ibm.com/ developerworks/data/library/cognos/page468.html. The configurations which should be of concern include: useFastGetMembers useMDXToRetrieveMembersFor useMDXToRetrieveMembersLimit displayProperty detectSAPVariableUniqueness
These configuration entries resided in both sapbw_config.xml and qfs_config.xml in earlier versions of the product, and their usage has not altered since then. All other entries should be left unaltered unless specifically instructed by IBM Cognos Customer Support or Development. Tracing The XQEODP.CONFIG.XML file also contains the mechanism to trace some of the communications between the Query Service and SAP BW such as MDX statements and BAPI (Business Application Programming Interface) function calls used to retrieve metadata and data from the underlying systems. In order to perform this level of tracing, locate this section of the configuration file:
Page 8 of 25
developerWorks
<component name="SBWODP"> <eventGroup name="Configuration"/> <eventGroup name="Connection"/> <eventGroup name="Function"/> <eventGroup name="Metadata"/> <eventGroup name="DataQuery"/> <eventGroup name="Timing"/> <eventGroup name="Exception"/> </component>
Add level=info to an entry and restart the query service, and this will start recording the requested entries to the log file which is located under the logs\xqe directory. Each time the query service starts, a new file is created. The log files are prefixed with xqelog-<timestamp>.xml. For example, in order to trace some of the outgoing MDX statements, you would set the following entry:
<component name="SBWODP"> <eventGroup name="Configuration"/> <eventGroup name="Connection"/> <eventGroup name="Function"/> <eventGroup name="Metadata"/> <eventGroup name="DataQuery" level=info/> <eventGroup name="Timing"/> <eventGroup name="Exception"/> </component>
The most frequently used entries are DataQuery and Function. Those two entries will show most of the pertinent calls made to SAP BW which should be of concern. BW.PROPERTIES This file contains some of the entries dictating the default behavior of the query engine specifically for SAP BW. First and foremost, it must be stated that entries in this file should not be altered unless specifically instructed by Customer Support or Development. They are meant for very specific scenarios and their applications are server wide. With that said, two entries can be altered. The first entry is lolap.tupleStorageThreshold. This sets the maximum potential size of a tuple which we will store in the cache. The potential is calculated by multiplying the members received from each dimension requested from SAP BW. Should the potential size of the result exceed this limit, then IBM Cognos will not be caching the data results. Please note this only affects data cache (tuple storage) and not metadata cache. By default, this value is set to 150,000. This limit will easily be reached, therefore, we can increase the potential limit to 150,000,000. This does not mean that all tuples up to 150,000,000 will be stored in the cache as other heuristics are also considered by the engine. These other heuristics will avoid storing results which would be slower to write/read from the cache then reading directly from SAP BW (i.e. very large dense reports). The second entry which some may be interested in leveraging is use.valid.from=true. This will dictate whether the From date or the To date will be utilized when setting the KEYDATE for time-dependant hierarchies. Each timeIBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse Page 9 of 25
developerWorks
dependant hierarchy contains a validity period which is stored in the model /package. When authoring a report against such hierarchies, prior to executing a report, IBM Cognos will set the key date based on these stored periods. By default (true), the From date will be used. Changing the value to false will have the following effect: 1. If no values exist for To -> the current date is used as key date. 2. Values exist only for To -> To date is used as key date. 3. Values exist for both From and To -> To date is used as key date. The validity period of time-dependant hierarchies can be found in the IBM Cognos Framework Manager model. In the left hand pane, select the concerned hierarchy and note the two properties: Valid_From and Valid_To. Advanced Environment Settings In IBM Cognos 10, all optional SAP prompts of a SAP BW InfoQuery are prompted by default, and all will be revealed in an IBM Cognos prompt page unless they are explicitly called and hidden from an IBM Cognos report. However, you do have the ability to change this default behavior with an advanced server property that will hide the optional variables without having to explicitly call the optional SAP variables in an IBM Cognos report. The property called RSVP.PROMPT.FORCEDATASOURCEPARAMETERPROMPT must be set to FALSE to hide the optional SAP variables. Step by Step for changing the Advanced Environment Settings To change the default parameter value, and set the parameter to FALSE, perform the following steps. 1. Go to IBM Cognos Administration -> Configuration -> Dispatchers and Services. Figure 5: IBM Cognos Administration for Dispatchers and Services
Page 10 of 25
developerWorks
2. Click on the dispatcher URL. 3. For the ReportService, choose the Properties link. Figure 6: View the properties of the ReportService
4. Select the Settings tab. Figure 7: View Settings
5. For the row labeled Environment, Advanced Settings, choose Edit. Figure 8: Edit the advanced settings
6. Click the checkbox option to Override the settings acquired from the parent entry. A parameter input screen will then appear. 7. Set the following parameter to FALSE to hide optional SAP variables. RSVP.PROMPT.FORCEDATASOURCEPARAMETERPROMPT (default is TRUE) Figure 9: Setting this parameter to FALSE will hide optional SAP variables
8. Click OK, and OK again.

IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business Warehouse Page 11 of 25
developerWorks 9. Stop and restart the ReportService.
IBM Cognos 10 Report Studio

In addition to the guidelines noted within the IBM Cookbook for IBM Cognos 8.4 for use with SAP NetWeaver Business Warehouse for professional report-writing with SAP BW. The following statements should be considered when using IBM Cognos 10 Report Studio over a SAP BW data source. 1. Access SAP BW data with DQM-enabled packages whenever possible. Performance of analysis capabilities can be improved substantially with DQM when accessing SAP BW data. 2. Use SAP BW queries with variables and filters to restrict the data set from BW to help limit the size of data passed from SAP BW. 3. Refer to the IBM Cognos 10 Dynamic Query Cookbook to better understand the benefits of the Dynamic Query Mode. 4. Active Reports, a new capability introduced in IBM Cognos 10, can be built to access data from SAP BW.
IBM Cognos 10 Business Insight Advanced

Business Insight Advanced is a Web-based tool used to author reports and analyze data. The user interface is designed for business users to get insight into their business. For more information on how to use Business Insight Advanced, consult the IBM Cognos Business Insight Advanced User Guide provided in the IBM Cognos 10 installation directory. The following statements provide general statements which can be applied within the Business Insight Advanced (BIA) environment when working with SAP BW data. 1. Access SAP BW data with DQM-enabled packages whenever possible. Performance of analysis capabilities can be improved substantially with DQM when accessing SAP BW data. 2. .Use SAP BW queries with variables and filters to restrict the data set from BW to help limit the size of data passed from SAP BW. 3. Leverage SAP BW InfoQuery optional variables as opposed to filtering within Business Insight Advanced where appropriate. This approach will leverage the processing power of the SAP BW server, and push filtering of the data to the SAP BW data source. 4. The format of the SAP BW variables will be determined by the definition of the variable within the SAP BW query, or changes made to the variable definition in IBM Cognos Framework Manager or the Self-Service Package Wizard. 5. No formatting of the variable display format is done within Business Insight Advanced. 6. To re-prompt for SAP variables in Business Insight Advanced, click the refresh icon at the bottom of the page.
developerWorks
Figure 10: Refresh in Business Insight Advanced
7. To simplify reporting for end users, build a IBM Cognos Framework Manager package fit for purpose with only one data source. For example, deliver a package that delivers only what the users need from a data source, rather than allowing them to see all available content. And consider hiding or omitting elements, such as several alternate hierarchies, which they do not need. This approach will help to alleviate user-confusion and mitigate the probability that users will attempt to view unnecessarily high volumes of data which may provide slower performance. 8. Bring dimension levels into the report as opposed to display attributes to improve the initial response from SAP BW when the data is not cached with DQM. However, if the same display attribute is requested later, performance should be greatly improved as the data will reside in the DQM cache for users who have the same SAP BW security profiles. 9. When building a report and you do not want data to refresh as each column is brought in, create the reports in Page Design mode found in the View menu. (View -> Page Design).
Self-Service Package Wizard

The IBM Cognos 10 Self-Service Package Wizard (SSPW) allows users to create connections directly from IBM Cognos Connection to pre-modeled SAP BW data sources without using IBM Cognos 10 Framework Manager. Often, business users do not have data modeling skills nor are they required to model their SAP BW information. However, they still need to rely on IT resources to import, model, and package a data source; making the process a longer experience. The Self-Service Package Wizard helps business users by providing direct access to their information in SAP BW by enabling them to create their own IBM Cognos packages based on the SAP BW source. Consider these general statements when working with the Self-Service Package Wizard in IBM Cognos 10. 1. There is a limit to the number of objects a user can select. By default, the user can select a maximum of two SAP BW cubes and five SAP BW InfoQueries. But consider starting small, and request that users only choose one or two objects at a time per package. This will help to limit and control the number of objects which are imported at one time, assist with an optimized import of the SAP BW metadata, and help to limit the size of the IBM Cognos Content Store. 2. Consider updating the default settings to limit how many SAP BW queries or cubes a user can import for metadata. These parameters may be updated
developerWorks
3.
4. 5. 6.
7.
8.
9.
within Cognos Administration and the steps to change are noted below in this section. Import metadata from SAP BW queries rather than selecting the cube. This will provide users the ability to leverage SAP BW objects not otherwise available from the cube, such as calculated and restricted key figures, query structures, filters, and variables. This practice is aligned with the proven practices as stated for IBM Cognos Framework Manager and SAP BW. When publishing a new package, select the option Use Dynamic Query Mode. SSPW users should strongly consider saving their packages to their My Folders directory or other dedicated directories to avoid package clutter in the Public Folders directory. With SSPW, you have the option to select at the cube or SAP BW query level, and definitions of any objects under those levels will be imported. For those SAP BW queries that call several alternate hierarchies or dimensions that are not necessary for reporting, consider importing SAP BW metadata using IBM Cognos Framework Manager where you have the option to select only the hierarchies that you need. This method can help expedite the import process. Consider use by IT and business users within test environments to enable users to build their own models and assist with requirements gathering. This practice could help to accelerate requirements gathering, development, and regression testing processes for required SAP BW reports and analysis as business users could be more involved. Any package created using the SSPW cannot be changed with IBM Cognos Framework Manager after the package is published. To change an existing package with SSPW, a user will need to re-import the SAP BW InfoQuery and then over-write the existing package. Another option is to recreate and overwrite the package using IBM Cognos Framework Manager. In the event it is required that updates to the package will be necessary on a iterative basis, consider using IBM Cognos Framework Manager where there is more control to include or omit objects that are necessary for the package and reports. In the event a package has been created with SSPW where the SAP BW InfoQuery is changed after the package was created, there could be ramifications to existing reports that were built on the package. It may be necessary to re-import the SAP BW InfoQuery with SSPW or IBM Cognos Framework Manager to get the latest definitions, and then over-write the existing package. Also note that in this case, existing reports should be analyzed to see if changes are necessary.
Using the Self-Service Package Wizard The following section provides a step by step overview of using the Self-Service Package Wizard to create a package. 1. To enable this feature, the Cognos Administrator must update the SAP BW connection properties to allow personal packages. This step is done in IBM Cognos Administration -> Configuration -> Data Source Connections.
developerWorks
Figure 11: Data source connection properties in IBM Cognos Administration
Figure 12: 'Allow personal packages' is checked
2. Click on the Self Service Package Wizard blue folder icon.
Page 15 of 25
developerWorks Figure 13: The SSPW Wizard icon
3. A window opens showing all SAP BW data sources available. Select the SAP BW data source containing the data required, and click OK. Figure 14: The SAP BW connection appears within the wizard
4. Specify the name and location of the new package. It is recommended that users save their packages to My Folders to avoid user confusion and clutter in the Public Folders.
Page 16 of 25
developerWorks
Figure 15: The user has chosen to save the package to My Folders
5. Find and select the appropriate SAP BW InfoQuery required, and leave the default option to Enable SAP BW Dual Structures support. Click Next. It is recommended to choose a query rather than the cube. This provides users the ability to leverage SAP BW objects not otherwise available from the cube, such as calculated and restricted key figures, query structures, filters, and variables.
Page 17 of 25
developerWorks
Figure 16: The user has selected the SAP BW InfoQueries for the package
6. Choose to import any languages that are supported within your SAP BW environment. Confirm the design language, and click Next.
Page 18 of 25
developerWorks
Figure 17: English is imported from SAP BW
7. Choose the option for Use Dynamic Query Mode to leverage DQM and its query caching capabilities for improved response times and performance. Optionally choose the Object display name of your choice. Note the display name chosen should be supported and available within your SAP BW data source. And to have objects in the model organized the same way that they are organized in SAP Business Explorer Query Designer, select the Enhance model for SAP BW organization of objects option. You will then have a folder for each dimension. Note this selection is purely optional for visual purposes only, and is a matter of personal preference. You may choose this option to accommodate those users who are familiar with the SAP Business Explorer tools. Click Finish.
Page 19 of 25
developerWorks
Figure 18: The user has chosen to 'Use Dynamic Query Mode' for better performance
8. If the SAP BW InfoQuery contains variables, you can choose to edit its properties by selecting to launch the SAP BW Edit Variables page. Do this by choosing the option to Edit the SAP BW variables for the package after closing this dialog , and then click Close.
Page 20 of 25
developerWorks
Figure 19: Edit SAP BW variables for the package
9. If required, you can change the behavior of the variables via the Prompt Type property by using the dropdown menu.
Page 21 of 25
developerWorks
Figure 20: Change the SAP BW variable properties as necessary
A new package is ready to be used within IBM Cognos 10 so users may access data from SAP BW. Figure 21: The new package appears in 'My Folders' as defined
Update Default Settings to Control Import Limits IBM Cognos Administrators may want to reduce the number of SAP BW queries or cubes a user can select to import SAP BW metadata beyond the default settings. By default, a user can select a maximum of two SAP BW cubes and five SAP BW InfoQueries. These governors can be set within the Dispatchers and Services tasks within IBM Cognos Administration. The following section outlines the steps necessary to reduce the limits, which will help to control the number of objects that are imported at one time for a package, and promote an optimized import of the SAP BW metadata.
developerWorks
1. Go to IBM Cognos Administration -> Configuration -> Dispatchers and Services. Figure 22: IBM Cognos Administration for Dispatchers and Services
2. Click on the dispatcher URL. 3. For the MetadataService, choose the More link. 4. Select Set Properties, and then the Settings tab. Figure 23: View Settings
5. For the row labeled Environment, Advanced Settings, choose Edit. Figure 24: Edit the advanced settings
6. Click the checkbox option to Override the settings acquired from the parent entry. A parameter input screen will appear. 7. Add the following parameters to specify the value for maximum number of SAP BW cubes or SAP BW InfoQueries. com.ibm.cognos.metadatauiservice.sap.maxcubes (default value is 2) com.ibm.cognos.metadatauiservice.sap.maxInfoQueries (default value is 5)
Page 23 of 25
developerWorks
Figure 25: Insert parameters to define the limit for SAP BW InfoQueries and cubes
8. Click the OK twice. 9. Stop and restart the service MetadataService.
Page 24 of 25
developerWorks
About the authors

Daniel Wagemann Daniel Wagemann is an IBM Cognos Proven Practice Advisor for Business Analytics in Canada. In his 11 years working with the IBM Cognos product Suite, he has established a vast understanding of all areas of an IBM Cognos deployment. His areas of expertise include course development, technical writing, consulting and customer support. His work can be found within almost all areas of the Proven Practices Site.
Rich Borucki Rich Borucki is a Cognos Solution Specialist with SAP subject matter expertise in which he has a detailed understanding of the technical integration of IBM Cognos with SAP applications. One of his roles for the past two years is to drive customer successes and help Cognos customers by developing materials such as this cookbook as support for their IBM Cognos implementations with SAP applications. In his combined 10 years at IBM, he has also served as a SAP BW developer and managing consultant delivering SAP BW implementations to IBM customers.
Pierre Valiquette Pierre Valiquette is a Software Engineer within the IBM Cognos SAP BW development team. His primary role consists of bridging the gap between the SAP BW development team, IBM Cognos Support organization, and the customer base. Pierre has been involved for 13 years in the Ottawa Lab in various capacities from Customer Support to Development. His main focus throughout has always been a customer facing one. Copyright IBM Corporation 2011 (www.ibm.com/legal/copytrade.shtml) Trademarks (www.ibm.com/developerworks/ibm/trademarks/)
Page 25 of 25

Page551 PDF Cognos

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Page551 PDF Cognos

Enviado por

Direitos autorais:

Formatos disponíveis

IBM Cognos Proven Practices: IBM Cookbook for IBM Cognos 10 for use with SAP NetWeaver Business

SAP BW Objects and Queries

Figure 1: This image shows time-dependent structures Algeria and Morocco

Figure 2: Time-Dependent Hierarchy Structure is defined within the SAP BW InfoObject

Figure 3: Time-dependent structures defined with different validity dates

Figure 4: Alternate hierarchies are arranged by validity dates

IBM Cognos 10 Framework Manager

Dynamic Query Mode

SAP BW Specific Configuration Files within IBM Cognos 10

4. Select the Settings tab. Figure 7: View Settings

8. Click OK, and OK again.

developerWorks 9. Stop and restart the ReportService.

IBM Cognos 10 Report Studio

IBM Cognos 10 Business Insight Advanced

Figure 10: Refresh in Business Insight Advanced

Self-Service Package Wizard

Figure 11: Data source connection properties in IBM Cognos Administration

Figure 12: 'Allow personal packages' is checked

2. Click on the Self Service Package Wizard blue folder icon.

developerWorks Figure 13: The SSPW Wizard icon

Figure 17: English is imported from SAP BW

Figure 19: Edit SAP BW variables for the package

Figure 20: Change the SAP BW variable properties as necessary

8. Click the OK twice. 9. Stop and restart the service MetadataService.

About the authors

Você também pode gostar