With SAP BusinessObjects BI 4.0 SAP introduced a new access method – direct access, which allows you to connect to a BEx query directly without creating an universe.
We recommend to use this BI Consumer Services connectivity to access your SAP NetWeaver Business Warehouse data.
2012 © 2012 SAP AG. All rights reserved.
161
Unit 4: SAP BusinessObjects Web Intelligence TBI30
Figure 65: Connect directly to BEx Query
Accessing BEx queries is similar to accessing an universe except they are not part of the BI platform:
• The starting point is an OLAP connection to enable access to the SAP BW system from the BI platform.
• OLAP connections are shared across the product suite (SAP Crystal Reports, Analysis, Web Intelligence)
• Passing from the BI platform to one or more SAP BW systems is seamless, the user browses from the BI platform up to the BEx query transparently.
• SSO is needed or BW credential must be set in the OLAP connection.
The OLAP connection let you define access to:
• SAP NetWeaver BW system
• InfoCube / MultiProvider
• BEx Query
162
© 2012 SAP AG. All rights reserved. 2012TBI30 Lesson: Web Intelligence and SAP NetWeaver Business Warehouse Data Sources
Figure 66: Select a BW BEx Query
In the Web Intelligence Query Panel you are presented the metadata provided by SAP NetWeaver Business Warehouse.
Describing Query Elements in SAP NetWeaver Business Warehouse
Query elements include characteristics, key figures, calculated key figures (formulas), restricted key figures, and reusable structures. Queries may have filters on characteristic values or filters on key figure values (conditions) assigned to select a certain slice of information from the InfoProvider. They may be parameterized by query variables.
All characteristics, navigational attributes, and key figures available through an InfoProvider are available for use in the Query Designer. Upon selection of an InfoProvider, the designer will see a list of metadata defining the following elements:
• Structures
These are collections of selections and formulas that provide layout criteria for a row or column that may be used by queries for a particular InfoProvider.
Structures may contain a combination of key figures, characteristics, and formulas. A reusable structure is a particular, commonly used collection of key figures or characteristics stored in the Metadata Repository for reuse in multiple queries (for example, a plan/actual variance or a contribution margin schema).
• Filters
2012 © 2012 SAP AG. All rights reserved.
163
Unit 4: SAP BusinessObjects Web Intelligence TBI30
Predefined filter criteria for the whole query that may be reused in all queries for a particular InfoProvider. A filter may contain any combination of characteristics and their filter values. A filter specifies the size of the subcube, as well as the initial navigation state displayed at query startup.
• Key Figures
A type of InfoObject used to record quantitative facts or measures. All of the key figures for a particular InfoProvider are available for queries. A calculated key figure is a formula consisting of basic, restricted, or other calculated key figures available in the InfoProvider stored in the Metadata Repository for reuse in multiple queries (for example, an average discount rate). A restricted key figure has an associated filter on certain characteristic values stored in the Metadata Repository for reuse in multiple queries (for example, year to date (YTD) sales of the previous year). A query consists of metadata elements arranged in rows, columns, and free characteristics.
All key figures are presented with the Unit and Formatted Value in the Web Intelligence Query Panel
• Dimensions
Dimensions refer to the grouping of characteristic InfoObjects in InfoCubes.
Before using BEx Queries in Web Intelligence
Note: Only BEx queries with the flag Allow External Access to the Query are eligible for reporting (only these queries are visible for selection within Web Intelligence).
Before setting the BEx query MDX flag Allow External Access to the Query, the administrator must ensure that the BEx query complies with reporting constraints concerning the query definition. These are described in the following table:
BEx Query Feature Web Intelligence Limitation
Linked nodes Linked nodes are not displayed.
Lower level nodes Lower level nodes are always shown after the main node.
Decimal number The BEx query decimal number
definition is not consumed in Web Intelligence. Use the formatted value instead if you need to keep the exact decimal setting in your report. You can also apply the decimal setting in the table and chart of your report.
164
© 2012 SAP AG. All rights reserved. 2012TBI30 Lesson: Web Intelligence and SAP NetWeaver Business Warehouse Data Sources
Variable orders Variables are displayed with respect to the variable dependency (less dependent first) rather than the order defined in the BEx query.
Number of objects allowed in a query Do not use more than 50 objects in a BEx query, otherwise an error occurs.
Variables dependent on compound characteristics and the parent object
When there are dependencies between variables in compound characteristics and their parent, the dependencies are not guaranteed.
Row/Column display as hierarchy It is not possible to show an overall hierarchy out of an axis hierarchy. The characteristics, hierarchies, and key figures that make up the hierarchy are retained.
Variables on default values default values are fully supported Filters as default values Not supported, these are removed
from the BEx query. The filter will be ignored, or, if a variable is used, the variable prompt will display, but the user response is ignored. Move any restriction based on a variable into the filter zone in order for it to be taken into account for reporting.
Expand to level By default, hierarchies are not expanded to a given level. To reproduce this behavior, expand the table and chart in the report, then save the document.
Query exceptions These are not taken into account in Web Intelligence. Apply conditional formatting in Web Intelligence instead.
Complex selection When a variable is defined to support the complex selection, there is no equivalent. This is limited to range selection.
Zero suppression Rows of zero values are not removed from the result table.
Query default layout Default positions of characteristics in Rows / Columns are not reproduced.
Position of lower level nodes These are always below the upper levels.
2012 © 2012 SAP AG. All rights reserved.
165
Unit 4: SAP BusinessObjects Web Intelligence TBI30
Local calculations (Rank, Minimum...) These are removed from the Bex query. Avoid the use of these, prefer the equivalent calculation function in the report.
Formula with calculation It is recommended to avoid Formula with calculation depending on the layout (“Percentage share of result” ) that are not supported. You can use equivalent calculation function in the Web Intelligence report.
Hierarchical measure structures Hierarchical measure structures are displayed as a flat list of measure.
Conditions Conditions are not supported.
Creating a Web Intelligence Document on a Multi Structure Query A SAP NetWeaver Business Warehouse query can contain up to two structures.
By creating such a query the user defines a report with a grid type of layout.
When creating a Web Intelligence query on top of an SAP NetWeaver Business Warehouse query with multiple structures, the structure with the characteristic is turned into a hierarchy, and the member selector can be used to find objects in the Query Panel.
Using Universes on SAP NetWeaver Business Warehouse InfoProviders in Web Intelligence
In the previous BusinessObjects Enterprise XI 3.x releases you created universes when connecting to your SAP NetWeaver Business Warehouse system.
Universe Design Tool that has been used for creating universes on top of SAP BW InfoProviders or queries in SAP BusinessObjects XI 3.x is still shipped with SAP BusinessObjects BI 4.0. That is, to enable a smooth transition and to protect your past investment. That means XI 3.x universes will work as is in Web Intelligence 4.0.
However, we recommend using SAP BusinessObjects 4.0 in combination with the new BICS direct connectivity.
166
© 2012 SAP AG. All rights reserved. 2012TBI30 Lesson: Web Intelligence and SAP NetWeaver Business Warehouse Data Sources
How SAP NetWeaver Business Warehouse Objects are Mapped and Used in the Universe
Figure 67: Mapping SAP NetWeaver Business Warehouse and SAP BusinessObjects XI 3.1 Universe
All InfoObjects in the BEx Query set as rows, columns, free characteristics, and filters are exposed to the universe. This includes characteristics, hierarchies, key figures, structures, and variables
Hierarchies are mapped, allowing Web Intelligence users to drill down according to BW hierarchies.
For InfoCubes, all the dimensions, key figures, and hierarchies are mapped. The following table shows the universe objects created for each BW object.
Dimensions and Characteristics SAP NetWeaver Business
Warehouse object
Universe objects created
Dimension Group Class
Characteristic Subclass with dimension and detail objects
Characteristic with hierarchy
If data source is a BEx Query:
Subclass containing dimension and detail objects for each hierarchy level in the currently defined hierarchy.
2012 © 2012 SAP AG. All rights reserved.
167
Unit 4: SAP BusinessObjects Web Intelligence TBI30
SAP NetWeaver Business Warehouse object
Universe objects created
If data source is an InfoCube:
Subclasses containing dimension and detail objects for each hierarchy level for all hierarchies defined for the characteristic.
Attributes
SAP NetWeaver Business Warehouse object
Universe objects created
Navigational attribute Subclass with dimension and detail objects (identical to characteristic) Display Attribute Detail object for the dimension
Structures
SAP NetWeaver Business Warehouse object
Universe objects created
Structure based on Characteristics (BEx Queries only)
Class with single dimension object for the structure
Key Figure Measure object in the class for the
Key Figure structure with dimension objects for units/currency
Calculated Key Figure (BEx Queries only)
Measure and dimension objects (same as Key Figure)
Restricted Key Figure (BEx Queries only)
Measure and dimension objects (same as Key Figure)
168
© 2012 SAP AG. All rights reserved. 2012TBI30 Lesson: Web Intelligence and SAP NetWeaver Business Warehouse Data Sources
Variables
SAP NetWeaver Business Warehouse object
Universe objects created
Variables (BEx Queries only) Filter mandatory in query In the class for the dimension to which the variable applies, two dimension objects supporting the list of values, one for caption, one for description.
Key date variable (BEx Queries only) Universe parameters defining key date variable in the universe
Characteristics in the Filters section of the BEx Query are not mapped. However, the filtering applies to the universe. If the filter has a fixed value, the filter is applied transparently when running the Web Intelligence query. If the
characteristic has a variable defined, the variable is mapped with these limitations:
• The variable always behaves like a mandatory variable
• Hierarchy and hierarchy node variables are not supported
To avoid these limitations, we recommend moving the characteristic from the Filter section to the free section of the BEx Query.
Leveraging the Semantic Layer
As part of SAP BusinessObjects 4.0 you can leverage the direct BICS connectivity (recommended) or leverage the semantic layer. By leveraging the semantic layer you can create an universe with a relational view on top of SAP NetWeaver Business Warehouse in the Information Design Tool. The relational view on top of SAP NetWeaver Business Warehouse is helpful when you need to combine data from multiple sources and one of them being SAP NetWeaver Business Warehouse.