Info Set
Info Set
InfoSets are InfoProviders that 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 using joins. When an InfoSet is made up
of several characteristics you can map transitive attributes and analyze this master data.
EXAMPLE
You create an InfoSet using the characteristics Business Partner (0BPARTNER) – Vendor (0VENDOR) –
Business Name (0DBBUSNAME) and can thereby analyze the master data.
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 connect the objects in a join to one
another (equal join-condition). A join condition determines the combination of individual object records
that are included in the results set.
You can use an InfoSet with a temporal join to map periods of time. With all other types of BW object, the
data is determined for the query key date, but with a temporal join in an InfoSet, 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.
Unlike the classic InfoSet, an InfoSet is a BW-specific view of data.
More information: Classic InfoSet
Prerequisites
Make sure that the objects for which you want to define the InfoSet are active. Create any InfoObjects
that you require that do not already exist and activate them.
Instead of creating a new InfoSet, you can transfer one of the InfoSets that are delivered with SAP BI
Content.
More information: Installing BI Content
Procedure
1. You are in the InfoProvider tree of the Modeling function area in the Data Warehousing Workbench.
In the context menu of the InfoArea in which you want to create an InfoSet, choose the Create
InfoSet... function. The Create InfoSet dialog box appears.
2. Enter descriptions for the new InfoSet.
3. In the Start with InfoProvider section, you determine which InfoProvider you want to use to start
defining the InfoSet.
4. Choose (Continue).
RECOMMENDATION
The first time you call the InfoSet Builder you can choose between two display modes:
network (DataFlowControl) or tree (TreeControl). While the network display is clearer,
the tree display can be read by the ScreenReader and is more suitable for visually-
impaired users. You can change this setting at any time using the menu path
Settings Display
The Change InfoSet screen appears.
5. Choose a layout for the InfoProvider tree:
The default value is Related InfoProviders. Changed settings are personalized and stored if you
leave InfoSet maintenance with F3. They are available in your next call.
For more information on the screen layout, particularly the layout of the InfoProvider tree,
see Screen Layout: Changing InfoSets.
6. You use the (where-used list) to determine which BW objects use the InfoSet that you have
selected. This shows you the effects of changing the InfoSet. This helps you to decide whether you
want to make these changes at this particular time.
7. You define or change the InfoSet by adding one or more InfoProviders to the join.
In join control, there are several ways to add an InfoProvider:
From the InfoProvider tree:
Transfer the required InfoProvider by double-clicking the entry in the InfoProvider tree or by
using drag and drop.
To insert a certain InfoProvider irrespective of the current display of the InfoProvider tree,
choose (Add InfoProvider).
RECOMMENDATION
If you know the technical name of the InfoProvider that you want to add, this
method is quicker than switching the layout of the InfoProvider tree.
The InfoProviders are displayed in the join control.
More information: Join Control
8. Define the join conditions.
More information: Defining Join Conditions
9. You can get general information such as object version, date created and date changed by
choosing Goto Global Settings . You can also make various settings here. More
information:
Most Recent Reporting for InfoObjects
Left Outer Join
Local Aggregation
10. Use (Check) to check that the InfoSet is defined correctly.
11. Save and activate the InfoSet.
Result
The InfoSet is available in the BEx Query Designer.