Select language:

Object documentation InfoSet  


Description of a specific kind of InfoProvider: InfoSet describes data sources that are defined as a rule as joins of DataStore objects, standard InfoCubes  and/or InfoObjects (characteristics with master data). If one of the InfoObjects contained in the join is a time-dependent characteristic, the join is a time-dependent or temporal join.

An InfoSet is a semantic layer over the data sources.

Unlike the classic InfoSet, an InfoSet is a BI-specific view of data.

For more information, see the following documentation: InfoProviders, Classic InfoSets.


With activated InfoSets you can define queries in the BI suite.

InfoSets allow you to analyze the data in several InfoProviders by using combinations of master data-bearing characteristics, InfoCubes and DataStore objects. The system collects information from the tables of the relevant InfoProviders. When an InfoSet is made up of several characteristics you can map transitive attributes and analyze this master data.


You create an InfoSet using the characteristics Business Partner (0BPARTNER) – Vendor (0VENDOR) – Business Name (0DBBUSNAME) and can thereby analyze the master data.

You can use an InfoSet with a temporal join to map periods of time (see Temporal Joins). With all other types of BI object, the data is determined for the key date of the query, but with InfoSets with a temporal join, you can specify a particular point in time at which you want the data to be evaluated. The key date of the query is not taken into consideration in the InfoSet.


You can include any DataStore object, InfoCube or InfoObject of type Characteristic with Master Data in a join. A join can contain objects of the same object type, or objects of different object types. You can include individual objects in a join as many times as you want. Join conditions (equal join condition) connect the objects in a join to one another . A join condition specifies the combination of individual object records included in the results set.


InfoSet Maintenance in the Data Warehousing Workbench

You create and edit InfoSets in the InfoSet Builder. See Creating InfoSets and Editing InfoSets.

Queries Based on InfoSets

The BEx Query Designer supports a tabular (flat) display of queries. Use the Table Display pushbutton to activate this function.

In the BEx Query Designer, each InfoProvider in the join of type DataStore or characteristic bearing master data displays two separate dimensions (key and attribute). With InfoCubes, the dimensions of the InfoCube are mapped. These dimensions contain the fields and attributes for the selected InfoSet.


If the InfoProvider is an InfoObject of type Characteristic, all of the characteristics listed in attribute definition and all of the display attributes are assigned to the characteristics (and the compound characteristics, if applicable) in the Key dimension.

  The display attributes are only listed in the Key dimension.

  The independent characteristics are listed in both the Key and the Attribute dimensions.

If the InfoProvider is a DataStore object or an InfoCube, no field objects with the “exclusive attribute” property are listed in the directory tree of the InfoProvider.

If the join is a temporal join, there is also a separate Valid Time Interval dimension in the BEx Query Designer. See Temporal Joins.

InfoSets offer you the most recent reporting for characteristics that bear master data; in reporting and analysis, the newest records are displayed, even if they are not activated yet. See Most Recent Reporting for InfoObjects.

For more information about the technical details and examples of queries that use InfoSets, see Interpreting Queries Using InfoSets .

For more information about defining queries, see Query Design: BEx Query Designer

Transport Connection

An InfoSet is connected to the BI transport system as a TLOGO object. For more information, see Transporting BI Objects.

Definition and Delivery of Content

BI Content is defined and delivered in BI in the usual way. InfoSets are delivered in the D version and have to be activated by the customer (see Installing BI Content in the Active Version).