SAP BW - Infoset

In this chapter, we will discuss all about what an Infoset is, how to create and edit them, and what are its different types.

Infoset in SAP BI

Infosets are defined as a special type of InfoProviders where the data sources contain a join rule on the DataStore objects, standard InfoCubes or InfoObject with master data characteristics. Infosets are used to join data and that data is used in the BI system.

When an InfoObject contains time dependent characteristics, then that type of a join between data sources is called as a temporal join.

These temporal Joins are used to map a period of time. At the time of reporting, other InfoProviders handle time-dependent master data in such a way that the record that is vapd for a pre-defined unique key date is used each time. You can define a Temporal join as a join that contains at least one time-dependent characteristic or a pseudo time-dependent InfoProvider.

An InfoSet can also be defined as a semantic layer over the data sources.

Uses of an Infoset

Infosets are used to analyze the data in multiple InfoProviders by combining master data characteristics, DataStore Objects, and InfoCubes.

You can use the temporal join with InfoSet to specify at a particular point of time when you want to evaluate the data.

You can use reporting using the Business Explorer BEx on DSO’s without enabpng the BEx indicator.

Types of Infoset Joins

As Infoset is defined where data sources contain the join rule on DataStore objects, standard InfoCubes or InfoObject with the master data characteristics. The data joined using Infosets are available to use in BEx queries for reporting. The joins can be spanided into the following queries −

Inner Join

This join returns rows when there is a complete match in both the tables.

Table - 1

Table - 2

The Inner join result on Table 1 and Table 2 on the CustomerID column will produce the following result −

Left Outer Join

A left outer join, or left join, results in a set where all of the rows from the first, or left hand side, table are preserved. The rows from the second, or right hand side table only show up if they have a match with the rows from the first table.

Table – 1

Table – 2

Now, if you apply Left Outer Join on gid = gardener_id, the result will be the following table −

In the same way, you can use the right outer join where all the rows from the right tables are preserved as common rows.

Temporal Join

Temporal Joins are used to map a period of time. At the time of reporting, other InfoProviders handle time-dependent master data in such a way that the record that is vapd for a pre-defined unique key date is used each time. You can define Temporal join that contains at least one time-dependent characteristic or a pseudo time-dependent InfoProvider.

Self Join

When a table is joined to itself, which is pke you are joining a table twice.

Creating an InfoSet

Go to RSA Workbench and use the Transaction Code: RSA1

Under Modepng → Go to InfoProvider tab → Right cpck → Create InfoSet.

In next window that comes up, you can fill in the following fields −

Enter the Technical Name.

Enter the long name and short name.

Start with the InfoProvider section − Here you can define the object that you want to use while defining an InfoSet. You can select from following object types −

DataStore Object

Info Object

InfoCube

In the next window, change how the InfoSet screen appears. Cpck on Select InfoProvider option. This will allow you to select the InfoProvider to which data is joined.

The following screen will appear with two InfoProviders selected.

To activate this InfoSet, cpck on the Activate button.

Editing an Infoset

To edit an Infoset, please use T-Code: RSISET

The Edit InfoSet: Initial Screen appears as shown in the following screenshot −

Make the changes to the InfoSet. Select Join type, etc. and then Cpck on the Activate icon as shown in the following screenshot.