Infoset:

Definition

Name for a particular type of InfoProvider: An InfoSet describes data sources that are
usually defined as joins for ODS objects or InfoObjects (characteristics with master data).
A time-dependent join or temporal join is a join that contains an InfoObject that is a time-
dependent characteristic.

An InfoSet is a semantic layer over the data sources and is not itself a data target.

Unlike the classic InfoSet, and InfoSet is a BW-specific view of data.

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

Use

In the BEx Query Designer you compile reports (queries) about activated InfoSets.

InfoSets allow you to report on several InfoProviders by using combinations of master

data-bearing characteristics and ODS objects. The information is collected from the
tables of the relevant InfoProviders. When an InfoSet is made up of several
characteristics, you are able to map transitive attributes and report on this master data.

You create an InfoSet using the characteristics Business Partner (0BPARTNER)

Vendor (0VENDOR) Business Name (0DBBUSNAME), and can then use the
master data for reporting.

You can create time runs with an InfoSet by means of a temporal join (for this, see
Temporal Joins). 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.

Structure

Every ODS object and every InfoObject that is a characteristic with master data can be
included in a join. A join can contain objects of the same object type, or objects of
different object types. The individual objects can appear in a join any number of times.
Join conditions connect the objects in a join to one another (equal join-condition). A join
condition determines the combination of records from the individual objects that are
included in the resulting set.

Classic InfoSets

Definition
A classic InfoSet provides a view of a dataset that you report on. You use the InfoSet query for
this purpose. The classic InfoSet determines which tables, or fields within a table, an InfoSet
query references.
Use
As of Release BW 2.0B, InfoSets are used in the Business Information Warehouse for
InfoObjects (master data), DataStore objects, and joins for these objects. These InfoSets are not
BI Repository objects but SAP Web Application Server objects. The InfoSet query can be used to
carry out tabular (flat) reporting on these InfoSets.
As of Release BW 3.0, these InfoSets are called classic InfoSets.

You can specify left outer joing in an InfoSets,select the object and choose the corresponding
function from the context menu. Note that outer joing are not permited on InfoCubes as this would
be an obvious performance issue. One more constraint, is that you are generally not allowed to
include more than two InfoCubes in an InfoSet. If you include more than two InfoCubes in an
InfoSet, the system produces a warning. This may be due to database related, or architecture
related constraints. You cannot add an object that you have already connected by using the left
outer join operator to another object.
1. Customer master table:

2. ODS data with key fields and data fields

Infoset : ods + infoset (based on Custid)

Design :
Restricted data:

Another Example: