InfoSet (Changed) 

Technical Data

Function is	Changed
In Release	Software Component ●      Component: SAP NetWeaver ●      Release 7.0
Assignment to Application Component	BW-WHM Warehouse Management
Country Setting	Valid for all countries

Use

As of release SAP NetWeaver 7.0, the following new features are available with InfoSets:

Using InfoCubes in InfoSets

You can now include InfoCubes in an InfoSet and use them in a join. InfoCubes are handled logically in InfoSets like DataStore objects. This is also true for time dependencies. In an InfoCube, data that is valid for different dates can be read.

Restrictions:

For performance reasons you cannot define an InfoCube as the right operand of a left outer join. SAP does not generally support more than two InfoCubes in an InfoSet.

Pseudo Time Dependency of DataStore Objects and InfoCubes in InfoSets

In BI only master data can be defined as a time-dependent data source.  Two additional fields/attributes are added to the characteristic.

DataStore objects and InfoCubes that are being used as InfoProviders in the InfoSet cannot be defined as time dependent.

As of SAP NetWeaver 7.0, you can specify a date or use a time characteristic with DataStore objects and InfoCubes to describe the validity of a record.   These InfoProviders are then interpreted as time-dependent data sources.

Accessibility Mode for Working with InfoSets

The first time you call the InfoSet Builder you can choose between two display modes: network (DataFlow Control) or tree (TreeControl). While the network display is more transparent, the tree display can be read by the ScreenReader and is suitable for visually-impaired users. You can change this setting at any time in Settings  ®  Display. Changes take effect the next time you call the InfoSet Builder.

InfoSet Connection to TREX Search

You can use the TREX search to find InfoSets if you want to change an existing InfoSet in transaction RSISET.

Enhanced Where-Used List for Working with InfoSets

When deleting InfoSets, the system up to now has only performed limited checks to see whether the InfoSet is still being used.

Now you can only delete InfoSets when the fields of the InfoSet are no longer being used in the currency translation types.

Enhancement of Global Properties

The global properties in InfoSet maintenance have been enhanced by one setting Left Outer: Include Filter Value in On-Condition.

This indicator is used to control how a condition on a field of a left-outer table is converted in the SQL statement.

This affects the query results:

●      If the indicator is set, the condition/restriction is included in the on-condition in the SQL statement. In this case the condition is evaluated before the join.

●      If the indicator is not set, the condition/restriction is included in the where-condition. In this case the condition is only evaluated after the join.

The indicator is not set by default.

Key Date Derivation from Time Characteristics

Key dates can be derived from the time characteristics 0CALWEEK, 0CALMONTH, 0CALQUARTER, 0CALYEAR, 0FISCPER, 0FISCYEAR:

It was previously possible to specify the first, last or a fixed offset for key date derivation. As of SAP NetWeaver 7.0, you can also use a key date derivation type to define the key date.