This is the last article of our series about new features of SAP BusinessObjects 4.2! The following new features and enhancements are available in this release of the Information Design Tool:
Sets and Set Filters
The BI Sets support is the main enhancement in SAP BI 4.2 for the information design tool.
In the new version developers can create sets which are used as pre-defined complex query filters in Web Intelligence. A set is a structure that contains multiple lists of values for key enabled dimensions in the business layer and based on a universe (UNX). The sets can contain the definition of calendars, used for temporal sets, whose content evolves in time. Developers can publish themselves sets to the CMS repository and they are available as set filters when the associated universe is used as a data source in the query panel. Sets are stored in the data warehouse along with production data, enabling fast filtering.
BI sets are useful to query data using sets logic and operators rather than SQL.
Developers can now convert a single or a group of multiple .UNV universes to .UNX universes format in a single step. Linked .UNV universes can now also be converted to .UNX universes conserving links to all core universes. Developers can also choose to include all core universes in a single universe if preferred.
Now you can use the Big Numbers feature at the .UNX Universe level and avoid enablement per report. The Big Numbers are a new High Precision property to the existing Numeric Data Type, based on an IEEE decimal floating point format standard, which enables developers to define numeric objects that are expected to be consumed with a higher precision, from 15 digits to 40 digits.
The Information design tool can convert linked universes created with the Universe Design Tool. The conversion dialog box has been completely modified to convert several universes at once and propose new conversion options.
Now developers can link a universe to one or more core universes in the repository. When changes are made in the core universe, they are automatically propagated to the shared components in its linked universes. Using linked universes allow developers to take advantage of components in predefined and tested universes as a starting point to quickly build new universes.
The process for creating a linked universe has changed. A developer must start with a pre-existing universe and create a linked universe from it. Once created, the developer can add tables to the new universe which reads from the original universe. Changes to the original universe are automatically reflected in the new linked universe. Both the data foundation and business layer from the original universe are available in the linked one.
The new SQL parameter NO_NULL_YIELDS_IN_SUBQUERY has been added to the SQL Generation Parameters list. When set to YES, SQL scripts are generated ensuring fields with non NULL values are included for filters based on a subquery. The default value is NO.
Setting Summary tab preferences for data foundation views
For data foundations with multiple views, you can now choose to open a specific view in the editor instead of the default master view. This can help to save time when developers want to work on a subset of the data foundation, and do not need to display the entire content of the Master View. A new Summary tab is available that lists views with a color code that gives an indication of the loading time onto the screen. Based on this information, developers can select a view that will display more quickly rather than the master view which displays all of the available views.
Creating a business layer directly on a BEx Query
Developers can create a business layer directly on a BEx Query using BICS access and publish the business layer as a universe available to Web Intelligence. Creating a universe based on a BEx query has a major advantage over using direct access to a BEx query as developers can organize and customize the query dimensions, measures, and hierarchies in the business layer. Although developers can edit certain components of the business layer, the data foundation is built automatically on the query and is read only.
This article provided an overview of the features and enhancements that have been added to the SAP BusinessObjects since the previous release. It directs you to the available product documentation to get you started using the new features!