Collection Object Grouping  

Use

Via  Grouping, you can choose which Business Content objects are to be collected.By default, only those objects that are absolutely necessary for an object’s activation are collected. By making the appropriate selection, you can also collect objects that are required for the activation of other objects that were collected at the same time. 

Functions

You can group objects in the following ways:

Required Objects Only

Only those objects that are really necessary for the action, that is, copying or transporting the selected objects, are taken into account (minimal selection).

The following applies for InfoObjects and InfoCubes, for example:

§         With InfoObjects, the corresponding attributes are also collected, as are the application components to which the InfoObject is assigned.

§         With InfoCubes, the InfoObjects contained in the InfoCube as well as the InfoArea are collected.

In Data Flow Before

Those objects are collected that submit data to a collected object.

If your start point is an InfoCube, all those objects that are in the data flow before the InfoCube, and are therefore necessary for providing data to the InfoCube, are collected. This includes, for example, update rules and InfoSources.  So that these objects can be activated, all the corresponding objects required for these objects have to be collected in addition. For activating an InfoSource, InfoObjects may also be necessary which are not contained in the InfoCube and have therefore not yet been collected. However, for these additional objects, the objects that come before them in the data flow are not collected.

The following graphic shows this example in more detail:

In Data Flow Afterwards

Objects are collected that receive data from a collected object.

For example, if your start point is an InfoCube, all those objects that are in the data flow after the InfoCube, and are therefore reporting objects that serve to display the data stored in the InfoCube, are collected. This includes, for example, queries and Web templates. So that these objects can be activated, all the corresponding objects required for these objects have to be collected in addition. For activating a role, additional workbooks that are based on other InfoCubes may also be necessary. However, for these additional objects, the objects that come after them in the data flow are not collected. These additional workbooks cannot be used for reporting unless they are transferred from the Business Content by some other means.

The following graphic shows this example in more detail:

In Data Flow Before and Afterwards

All objects are collected that either deliver or submit data.

For example, when using an InfoCube, the objects necessary for activating the InfoCube are collected together with other objects that are required for activating those objects collected as well. This includes objects positioned both before and after the InfoCube in the data flow. 

With the InfoCube, all incoming data streams and the evaluation string are activated. Both are then completed with data streams, enabling a complete evaluation in the workbooks.

The restriction that the system does not collect all objects if you have set In Data Flow Before and Afterwards or In Data Flow Afterwards, is applied for performance reasons. 

Optional Objects

In the context menu, you can select the Add Optional Objects option. The where-used list is called and all objects that use the selected object are added. In addition, all objects required for these objects are collected. Otherwise it may not be possible to activate these objects.

For example, an InfoCube may be used by update rules and queries.