Add Data Security
You can restrict the data represented by query subjects in a project by creating a security filter. The security filter controls the data that is shown to your users when they set up their reports.
For example, your Sales team consists of a Sales Director, and four Sales Managers. You create a security filter that includes a group for the Sales Director and a group for Sales Managers, and apply the filter to the Salary query subject. When the package is available for your users, and a report is generated for the Sales Managers and the Sales Director, only the Sales Director can see
the salary information for the Sales Managers.
If a user has multiple roles, the security filters belonging to these roles are joined together with ORs.
If a role is based on another role, the security filters are joined together with ANDs.
You can base the security filter on an existing security filter. If you choose this option, the security filter inherits the filter and all the filter properties.
When you create a security filter, you can also use existing project filters, or create new filters usingthe expression editor. For more information, see "Create a Filter" (p. 156).
Steps
1. Click the query subject you want, and from the Actions menu, click Specify Data Security.
2. To add new users, groups, or roles, do the following:
● Click Add Groups.
● In the Select Users and Groups window, add users, groups, or roles. For information about
how to do this, see the Content Manager User Guide.
● In the Select Users and Groups window, click OK.
3. If you want to base the group on an existing group, click a group in the Based On column.
Tip: If you do not see the group you want in the list, you must add the group to the security
filter.
4. If you want to add a filter to a group, in the Filter column, click either Create/Edit Embedded Filter or Insert from Model.
ADD OBJECT SECURITY
Steps to Add Object-Based Security
1. Click the object you want to secure, and from the Actions menu, click Specify Object Security.
Tip: You can select more than one object at a time.
2. Select the users, groups, or roles you want to change. Or, click Add to add new users, groups,
or roles.
For more information, see the Content Manager User Guide.
3. Specify security rights for each user, group, or role by doing one of the following:
● To deny access to a user, group, or role, select the Deny check box next to the name for
the user, group, or role. Deny takes precedence over Allow.
● To grant access to a user, group, or role, select the Allow check box.
Tip: To allow everyone to see all objects unless specifically denied access, select the Allow check
box for the Everyone role.
4. Click OK.
A list of new and updated object-based packages appears.
ADD PACKAGE SECURITY
Steps
1. Click the package you want to edit, and from the Actions menu, click Package, Edit Package
Settings.
2. Click the Permissions tab.
3. In Cognos Connection, create, add, or remove groups or roles as required. For information
about how to do this, see the Cognos Connection User Guide.
4. After you finish modifying the security for the package, click OK to return to Framework
Manager.
Tuesday, March 2, 2010
MDX Overview
Multidimensional Expression (MDX) is the industry standard language used to
query multidimensional data sources and generate reports in BW. It is typically
used by third-party reporting tools. Those of you who are interested in a
non-SAP reporting solution to augment Business Explore (BEx) need to understand
the impact of MDX. Each tool uses it differently, and MDX affects your BW resources.
query multidimensional data sources and generate reports in BW. It is typically
used by third-party reporting tools. Those of you who are interested in a
non-SAP reporting solution to augment Business Explore (BEx) need to understand
the impact of MDX. Each tool uses it differently, and MDX affects your BW resources.
SAP Cognos Architecture Comparision
SAP BW is a very large scale datawarehousing tool based on ROLAP
technology.It has its own reporting Tool - BEX and its own star
schemas and ROLAP based cubes.
Cognos Powerplay is an OLAP based system , that sits on top of a
Star schema.
the SAP BW system has more overall functionality than the Cognos
system in terms of database schemas and extraction
transformation and loading.
One of the fundamental differences between SAP BW and Cognos is
in the ROLAP and OLAP technologies they base their cubes on.
The SAP BW Rolap is a relational database based on Oracle or DB2
or Microsoft Sql server.
the Cognos OLAP cubes are based on compressed large binary
objects.
This difference leads to the SAP BW system having the advantage
that the extract and data load time to the ROLAP level is as
fast as any good database load/insert can be and in theory this
is the only load time that you will incurr.
For the equivalent Cognos based system you may (if you are
running a data warehouse level)need to load your daily/weekly
data into a star schema and then subsequently load this data
into a Powerplay cube .
The load of the data intto the Powerplay transformer engine and
the subsequent creation of the Powerplay cube binary object -
can take a long period of time.This depends on the number of
rows you are loading and the parallel nature of the queries and
the complexity of the cube design.
So, for very large multi terrabyte systems, you may encounter
difficulties in fitting all the Powerplay cube creations into
your batch window.
However, SAP Bw has a similar problem i that it normall relies on
a level above the ROLAP, called Aggregations - and these are
similar in result to the Powerplay cubes aggregations - except
the BW ones are held in DB2 or Oracle and the powerplay ones are
Blobs.
Powerplay has better graphing and time series functionality - the
graphs are embedded in the Powerplay functinality - whereas in
SAP bW the graphs tend to be stuck on top of the spreadsheet
output.
I would say in summary, that the Cognos Powerplay system is
easier to use and deploy than SAP BW, but SAP BW is possibly
better for the complete end to end data warehouse solution - but
doesnt look quite as nice as Cognos to the end users.
technology.It has its own reporting Tool - BEX and its own star
schemas and ROLAP based cubes.
Cognos Powerplay is an OLAP based system , that sits on top of a
Star schema.
the SAP BW system has more overall functionality than the Cognos
system in terms of database schemas and extraction
transformation and loading.
One of the fundamental differences between SAP BW and Cognos is
in the ROLAP and OLAP technologies they base their cubes on.
The SAP BW Rolap is a relational database based on Oracle or DB2
or Microsoft Sql server.
the Cognos OLAP cubes are based on compressed large binary
objects.
This difference leads to the SAP BW system having the advantage
that the extract and data load time to the ROLAP level is as
fast as any good database load/insert can be and in theory this
is the only load time that you will incurr.
For the equivalent Cognos based system you may (if you are
running a data warehouse level)need to load your daily/weekly
data into a star schema and then subsequently load this data
into a Powerplay cube .
The load of the data intto the Powerplay transformer engine and
the subsequent creation of the Powerplay cube binary object -
can take a long period of time.This depends on the number of
rows you are loading and the parallel nature of the queries and
the complexity of the cube design.
So, for very large multi terrabyte systems, you may encounter
difficulties in fitting all the Powerplay cube creations into
your batch window.
However, SAP Bw has a similar problem i that it normall relies on
a level above the ROLAP, called Aggregations - and these are
similar in result to the Powerplay cubes aggregations - except
the BW ones are held in DB2 or Oracle and the powerplay ones are
Blobs.
Powerplay has better graphing and time series functionality - the
graphs are embedded in the Powerplay functinality - whereas in
SAP bW the graphs tend to be stuck on top of the spreadsheet
output.
I would say in summary, that the Cognos Powerplay system is
easier to use and deploy than SAP BW, but SAP BW is possibly
better for the complete end to end data warehouse solution - but
doesnt look quite as nice as Cognos to the end users.
Master Detail Relationship
Master detail relationships link information between two data containers (such as list crosstab or chart) within a report: a master data container and a detail data container.
Using a master detail relationship you can use a single report to display information that would normally take two reports.
Master detail relationship can be created for any data container within Report Studio.
1. Create or open a report to use that has one data
container (i.e. a crosstab report)
2. From the Toolbox tab drag a container object next to the container in the work area (i.e. a chart- drag items from the insertable objects pane)
3. Select the second container and drag it into the first container where you want to place it.
4. Click the embedded object to select it.
5. From the Data Menu click Master Detail Relationships to create the master detail links.
6. Click New Link and select the data items from each query that you want to link to the master detail relationship.
Using a master detail relationship you can use a single report to display information that would normally take two reports.
Master detail relationship can be created for any data container within Report Studio.
1. Create or open a report to use that has one data
container (i.e. a crosstab report)
2. From the Toolbox tab drag a container object next to the container in the work area (i.e. a chart- drag items from the insertable objects pane)
3. Select the second container and drag it into the first container where you want to place it.
4. Click the embedded object to select it.
5. From the Data Menu click Master Detail Relationships to create the master detail links.
6. Click New Link and select the data items from each query that you want to link to the master detail relationship.
Cognos BI Applications
IBM Cognos 8 Business Intelligence applications:
# Query Studio - a tool to create basic ad-hoc reports and a lighter version of Report Studio. It allows users to create one 1-page report at a time. Application used by Query Authors and Report Authors.
# Report Studio - used to create and manage more advanced reports, which are very often standarized and executed periodically and distributed to people in various departments in an organization. Reports can engage dashboards with gauges, charts, maps and other graphical elements with a full drill-through capabilities. Reports designs created in Query Studio can be read and edited in Report Studio (and not the opposite way). Report Studio is used by Report Authors.
# Analysis Studio - an application to analyze cubes and explore business data in a multidimensional manner. Large volumes of data can be analyzed through ranking, complex filtering, slicing, dicing and creating custom subsets. Mainly used by business analysts.
# Metrics Studio - used for scorecarding, helps manage performance by monitoring and analyzing metrics at all levels of an organization. The idea behind it is to put performance indicators next to the organization's key performance measures (red, orange, green status notation) and link them to reports containing related information.
# Event Studio - a process (an agent) which runs in the background and monitors the data and reacts when ocurrs something which may be cause a problem in the future in the business. For instance, if quantity of product X on stock is less than a given value, event manager can send an email to the responsible person which will contain a warning with problem description and a cognos report attached.
Event studio takes action by generating emails, running reports, updating news channel in a corporate portal or communicating with other software.
Aside from tracking actual products, it can also be used in monitoring services. For example if the number of subscribers in, say, a mobile broadband service exceeds the set capacity, event manager can email the necessary people so the problem could be looked into.
# Cognos Connection - it is a Web portal for Cognos 8 and a component which interracts with the Content Store. It is a frontend to publish, find, manage, organize, and view organization’s business intelligence data.
# PowerPlay Transformer and PowerPlay (Cognos 8 Business Intelligence Mobile Analysis ) - The Cognos 8 BI Mobile Analysis package is a new name for Cognos 7 PowerPlay applications. In fact, apart from the integration with Cognos 8 packages, there are no major changes since PowerPlay version 7.
Among others, the package includes the following applications known from Cognos 7 BI:
- Cognos PowerPlay Series 7 Version 4
- PowerPlay Connect
- PowerPlay for Excel
- Configuration Manager
- Cognos Scheduler
# Content Store is a database where the metadata for all the Cognos 8 component is stored and managed centrally.
Content store can be accessed directly with the Framework Manager.
# Framework Manager is a Cognos 8 modeling tool for creating and managing business-related metadata for use in all Cognos 8 BI applications. It lets modelers model relational data dimensionally, apply hierarchies to allow drill behavior, apply member functions and query any of the supported data sources (relational database with SQL or OLAP with MDX).
The main users of Framework manager are data warehouse developers and data modelers. Report authors base on the metadata information set up using Framework Manager when creating new reports.
# IBM Cognos TM1 (formerly Applix TM1) is a business intelligence solution which provides high-performance analytics, reporting, dashboarding and budgeting capabilities, fully integrated with Microsoft Excel. Thanks to its in-memory engine, TM1 is flexible, scalable and provides a high-performance read/write capability which makes it a great tool for budgeting, planning and controlling.
# Cognos Analysis for Microsoft Excel (CAFE) provides capabilities around exploration and slice and dice within Excel. It provides such capabilities as the Analysis Studio with its interactivity, but allows users to stay within Excel which very often is a key business requirement.
# Query Studio - a tool to create basic ad-hoc reports and a lighter version of Report Studio. It allows users to create one 1-page report at a time. Application used by Query Authors and Report Authors.
# Report Studio - used to create and manage more advanced reports, which are very often standarized and executed periodically and distributed to people in various departments in an organization. Reports can engage dashboards with gauges, charts, maps and other graphical elements with a full drill-through capabilities. Reports designs created in Query Studio can be read and edited in Report Studio (and not the opposite way). Report Studio is used by Report Authors.
# Analysis Studio - an application to analyze cubes and explore business data in a multidimensional manner. Large volumes of data can be analyzed through ranking, complex filtering, slicing, dicing and creating custom subsets. Mainly used by business analysts.
# Metrics Studio - used for scorecarding, helps manage performance by monitoring and analyzing metrics at all levels of an organization. The idea behind it is to put performance indicators next to the organization's key performance measures (red, orange, green status notation) and link them to reports containing related information.
# Event Studio - a process (an agent) which runs in the background and monitors the data and reacts when ocurrs something which may be cause a problem in the future in the business. For instance, if quantity of product X on stock is less than a given value, event manager can send an email to the responsible person which will contain a warning with problem description and a cognos report attached.
Event studio takes action by generating emails, running reports, updating news channel in a corporate portal or communicating with other software.
Aside from tracking actual products, it can also be used in monitoring services. For example if the number of subscribers in, say, a mobile broadband service exceeds the set capacity, event manager can email the necessary people so the problem could be looked into.
# Cognos Connection - it is a Web portal for Cognos 8 and a component which interracts with the Content Store. It is a frontend to publish, find, manage, organize, and view organization’s business intelligence data.
# PowerPlay Transformer and PowerPlay (Cognos 8 Business Intelligence Mobile Analysis ) - The Cognos 8 BI Mobile Analysis package is a new name for Cognos 7 PowerPlay applications. In fact, apart from the integration with Cognos 8 packages, there are no major changes since PowerPlay version 7.
Among others, the package includes the following applications known from Cognos 7 BI:
- Cognos PowerPlay Series 7 Version 4
- PowerPlay Connect
- PowerPlay for Excel
- Configuration Manager
- Cognos Scheduler
# Content Store is a database where the metadata for all the Cognos 8 component is stored and managed centrally.
Content store can be accessed directly with the Framework Manager.
# Framework Manager is a Cognos 8 modeling tool for creating and managing business-related metadata for use in all Cognos 8 BI applications. It lets modelers model relational data dimensionally, apply hierarchies to allow drill behavior, apply member functions and query any of the supported data sources (relational database with SQL or OLAP with MDX).
The main users of Framework manager are data warehouse developers and data modelers. Report authors base on the metadata information set up using Framework Manager when creating new reports.
# IBM Cognos TM1 (formerly Applix TM1) is a business intelligence solution which provides high-performance analytics, reporting, dashboarding and budgeting capabilities, fully integrated with Microsoft Excel. Thanks to its in-memory engine, TM1 is flexible, scalable and provides a high-performance read/write capability which makes it a great tool for budgeting, planning and controlling.
# Cognos Analysis for Microsoft Excel (CAFE) provides capabilities around exploration and slice and dice within Excel. It provides such capabilities as the Analysis Studio with its interactivity, but allows users to stay within Excel which very often is a key business requirement.
Performance Tuning of Cognos Reports
These are some general guidelines we use at my work:
1. For your queries, try to set the Processing property to Database Only. It runs faster than Limited Local.
2. Try to use fixed column widths where possible. We have found that dynamic sizing sometimes runs queries twice--once to find the largest data content, then again to dynamically size the columns based on the largest data content.
3. Try to move as many calculations as possible into the model so your query doesn't have to do them for every row of data pulled.
4. Try to use as many filters as possible up front to minimize the data you must pull in and process.
5. Simple CASE statements run faster than Search CASE statements.
6. Place calculations strategically. Rather than include a calculation in a CASE statement in multiple places, do it once in a separate field and then refer to it in multiple places. This minimizes processing time.
7. Create logical and useful index fields and logical table structures to make searching and pulling the data as efficient as possible.
8. When sorting a field, sort it either at the tabular model level OR the query level but NOT both.
9. Where possible, use database functions for calculations instead of their equivalent Cognos functions. See #1.
10. When using direct facts in the report do not create shortcuts, use
directly in facts under Qurey.
11. Cognos configuration by default font is Times new roman
the best practices are saying change the font to Arial - it will use less memory.
Hope that helps get you started thinking in the right direction.
1. For your queries, try to set the Processing property to Database Only. It runs faster than Limited Local.
2. Try to use fixed column widths where possible. We have found that dynamic sizing sometimes runs queries twice--once to find the largest data content, then again to dynamically size the columns based on the largest data content.
3. Try to move as many calculations as possible into the model so your query doesn't have to do them for every row of data pulled.
4. Try to use as many filters as possible up front to minimize the data you must pull in and process.
5. Simple CASE statements run faster than Search CASE statements.
6. Place calculations strategically. Rather than include a calculation in a CASE statement in multiple places, do it once in a separate field and then refer to it in multiple places. This minimizes processing time.
7. Create logical and useful index fields and logical table structures to make searching and pulling the data as efficient as possible.
8. When sorting a field, sort it either at the tabular model level OR the query level but NOT both.
9. Where possible, use database functions for calculations instead of their equivalent Cognos functions. See #1.
10. When using direct facts in the report do not create shortcuts, use
directly in facts under Qurey.
11. Cognos configuration by default font is Times new roman
the best practices are saying change the font to Arial - it will use less memory.
Hope that helps get you started thinking in the right direction.
LO extraction in SAP
1. Go to transaction code RSA3 and see if any data is available related to your DataSource. If data is there in RSA3 then go to transaction code LBWG (Delete Setup data) and delete the data by entering the application name.
2. Go to transaction SBIW --> Settings for Application Specific Datasource --> Logistics --> Managing extract structures --> Initialization --> Filling the Setup table --> Application specific setup of statistical data --> perform setup (relevant application)
3. In OLI*** (for example OLI7BW for Statistical setup for old documents : Orders) give the name of the run and execute. Now all the available records from R/3 will be loaded to setup tables.
4. Go to transaction RSA3 and check the data.
5. Go to transaction LBWE and make sure the update mode for the corresponding DataSource is serialized V3 update.
6. Go to BW system and create infopackage and under the update tab select the initialize delta process. And schedule the package. Now all the data available in the setup tables are now loaded into the data target.
7. Now for the delta records go to LBWE in R/3 and change the update mode for the corresponding DataSource to Direct/Queue delta. By doing this record will bypass SM13 and directly go to RSA7. Go to transaction code RSA7 there you can see green light # Once the new records are added immediately you can see the record in RSA7.
8. Go to BW system and create a new infopackage for delta loads. Double click on new infopackage. Under update tab you can see the delta update radio button.
9. Now you can go to your data target and see the delta record.
2. Go to transaction SBIW --> Settings for Application Specific Datasource --> Logistics --> Managing extract structures --> Initialization --> Filling the Setup table --> Application specific setup of statistical data --> perform setup (relevant application)
3. In OLI*** (for example OLI7BW for Statistical setup for old documents : Orders) give the name of the run and execute. Now all the available records from R/3 will be loaded to setup tables.
4. Go to transaction RSA3 and check the data.
5. Go to transaction LBWE and make sure the update mode for the corresponding DataSource is serialized V3 update.
6. Go to BW system and create infopackage and under the update tab select the initialize delta process. And schedule the package. Now all the data available in the setup tables are now loaded into the data target.
7. Now for the delta records go to LBWE in R/3 and change the update mode for the corresponding DataSource to Direct/Queue delta. By doing this record will bypass SM13 and directly go to RSA7. Go to transaction code RSA7 there you can see green light # Once the new records are added immediately you can see the record in RSA7.
8. Go to BW system and create a new infopackage for delta loads. Double click on new infopackage. Under update tab you can see the delta update radio button.
9. Now you can go to your data target and see the delta record.
Subscribe to:
Comments (Atom)