Skip to end of metadata
Go to start of metadata

Introduction

  • An InfoSet is a data source defined as a join between ODS objects, Characteristics or Cubes (new with BW70)
  • An InfoSet is not itself a data target, it does not store data
  • A join condition determines the combination of records from the individual objects that are included in the resulting set. Usually, when defining InfoSets, the objects are linked via inner join operators. However, you can also use left outer joins. Inner join and left outer join are only different in the situation where one of the involved tables does not contain any suitable record which meets the join conditions.
  • A time-dependent join or temporal join is a join that contains an InfoObject that has time-dependent attributes.
  • Within InfoSets several InfoProvider can be joined. Within this object one and the same infoobject/attribute can occur several times. Since an infoobject/attribute has to be unique within the InfoProvider it became unavoidable to establish aliases for the tables and fields of an infoset. If you turn on the display of technical names (button) in the transaction RSISET you get for every infoobject an field alias displayed: e.g. the infoset is called ISET1 and for the infoobject 0country the alias F1 is displayed - then internally the OLAP engine assignes the following technical name to this infoobject: ISET1___F1

InfoProvider that can be joined are:

  • InfoObjects having MasterData (timedependend and timeindependent)
  • DataStores
  • BasisCubes (since 7.0), (no NCUM cubes)

Interpretation of Query Results

The join condition determines the combination of records from the individual objects that are included in the resulting set. Depending on the definition of the Join and the data in the objects, it may happen that records from tables are included multiple times to get a record of the resulting set. This can lead to unwanted effects and makes it often difficult to understand the values displayed in a query. The following simple examples (and the list of SAP consulting notes listed below) should help to better understand the nature of JOINs.

Reports and Function Modules

RSQ_ISET_MASS_OPERATIONS  is a Report to check and activate infosets

RSQ_ISET_READ_RUNTIME_FIELDS is a Function Module that can be used to check the fields of the InfoSet  

Very Simple Examples to..

SAP Online Documentation

Creating Infosets

Topics

SAP Consulting Notes

Please click on the number of the note you are interested in.

Helpful Consulting Notes
  • 1064698    BW InfoSet: Include filter value in on-condition
  • 1581709    BW InfoSet with InfoCube and LEFT OUTER join
  • 1435772    InfoSet using left outer join and EXCLUDING conditions
  • 1500161    BW query on InfoSet with LEFT OUTER join terminates
  • 577953      Left Outer Join
  • 592785      Interpredation of Infoset Results
  • 583249      Temporal Joins
  • 2118286  CPR/HCPR: High Query Memory Consumption 
  • 673575      InfoSet: Long running program - SAPSQL_STMNT_TOO_LARGE
  • 1238583    Preliminary clarification: Information regarding BI Infosets
  • 1118492    BW Infoset does not support non-cumulative cubes!
  • 1532120    Local grouping before the join: Time-dependent InfoSets
  • 1279048    Local grouping before join - Time-independent InfoSets
  • 1712518    ABAP DUMP MESSAGE_TYPE_X CL_RSQ_ISET_SERVICE
  • 1694462    Dump GETWA_NOT_ASSIGNED / SAPLRSQ_ISET_RUNTIME occurs when executing infoset query
  • 1638003    Short Dump MESSAGE_TYPE_X EXTEND_FIELD_BUFFER
  • 1816330    InfoSet Queries Display Unexpected Results