Show TOC

Recommendations for Modeling InfoSetsLocate this document in the navigation structure

Use

  • To avoid problems caused by duplicated key figure values (see SAP Note 592785), we recommend that you only stage the key figures of one DataStore object or InfoCube of the InfoSet for the query. To do this, set the flag in the first column in InfoSet maintenance.

  • We recommend using just one InfoSet object (DataStore object, InfoCube, or master data table) with ambiguous characteristic values. As long as the InfoCube contains the visible key figures, this means that all the key characteristics of the DataStore object are used in the join condition for the InfoCube when joining a DataStore object with an InfoCube. Equally, when joining a master data table with compounding to an InfoCube, all of the key characteristics of the master data table are joined with the characteristics of the InfoCube.

  • SAP does not generally support more than two InfoCubes in an InfoSet.

  • As a general rule, do not use a large number of InfoProviders in a single InfoSet. Define more than one InfoSet instead.

  • Keep the number of joins in an InfoSet to a minimum, especially if loading a large quantity of data.

  • Only use left outer joins in InfoSets when absolutely necessary. Performance is better with inner joins than with left outer joins.

  • Do not perform calculations before aggregation. This can produce incorrect query results.

  • For time-dependent InfoSets, do not use the Valid from (0DATEFROM) and Valid to (0DATETO) fields in the query definition. Use the Valid Time Interval (VALIDTIMEINTERVAL), dimension instead. This is only visbile in Query Designer and is used for the time selection.