Defining Grouping Mode 

Use

There are several options for defining how the objects of BI Content should be collected before they are copied to the active version and transported.

By default, only those objects are collected that are absolutely necessary to activate and transport an object. If you also want to take additional dependencies between the objects into consideration when you collect objects, you can make a selection using a grouping mode.

More information: Object Dependencies and Consistency

Procedure

In the right screen area, select the objects of the BI Content to be collected by choosing  Grouping.

The different ways in which you can group the objects are described in the next sections.

Required Objects Only

Only those objects that are really required for the action (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 collected, as are the application components to which the InfoObjects are assigned.

■       With InfoCubes, at least the InfoObjects contained in the InfoCube and the InfoArea are collected. The attributes and application components are also collected recursively for the InfoObjects found in this way.

In Data Flow Before

The objects that pass data to a collected object are collected.

For an InfoCube, for example, all the objects that are in the data flow before the InfoCube, and are therefore necessary for providing data to the InfoCube, are collected. This includes transformation rules and InfoSources, for example.

To activate these objects, all the corresponding objects required for these objects have to be collected in addition. To activate an InfoSource, you may also require InfoObjects that are not contained in the InfoCube and therefore have not yet been collected. However, the objects that are in the data flow before these additional objects are not collected.

The figure below illustrates this:

If you are collecting data In Data Flow Before, note the following about DataSources:

The BI system collects the DataSources for those objects that are at most one level before the selected object. This is sufficient to provide transaction and master data.

If the selected object is for example an InfoCube, as in the above figure, the following DataSources are collected:

●        DataSources from which the corresponding InfoSource supplies transaction data to the InfoCube

●        DataSources that contain the original master data of the InfoObjects contained in the InfoCube (characteristics of the InfoProvider as well as their display and navigation attributes). No DataSources are collected for the attributes of these InfoObjects.

The following is valid for activating DataSources with the option In Data Flow Before if the D versions of the DataSources exist in the BI system: When you collect the objects, the system checks whether you have the authorization to activate DataSources in the source system remotely from the BI system. When you trigger the transfer of BI Content to the active version in the BI system, the results of the authorization check refer to the cache. The system either gives a warning or performs the activation and then replicates the active DataSources. The prerequisite for the source system and BI system is SAP NetWeaver 7.0 (Plug-In Basis 2005.1) for the BI Service API. If this prerequisite is not fulfilled, you have to activate the DataSources in the source system and then replicate them to the BI system.

More information: Copying BI Content DataSources to the Active Version.

In Data Flow Afterwards

The objects that get their data from a collected object are collected.

For an InfoCube, for example, all the objects that are in the data flow after the InfoCube, and are therefore reporting objects that display the data stored in the InfoCube, are collected. This includes queries and Web templates, for example. To activate these objects, all the corresponding objects required for these objects have to be collected in addition. To activate a role, you may also require additional workbooks that refer to other InfoCubes. However, the objects that are in the data flow after the additional objects are not collected. The additional workbooks cannot be used for reporting unless they were installed from BI Content by some other means.

The figure below illustrates this:

Data Flow Before and Afterwards

All objects that provide or pass on data are collected.

For example, if you are using an InfoCube, the objects required to activate the InfoCube are collected together with other objects that are required to activate those objects as well. This includes objects positioned both before and after the InfoCube in the data flow.

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

If you set the In Data Flow Before and Afterwards or In Data Flow Afterwards indicators, the system does not collect all objects. This is due to performance reasons.

Use the In Data Flow Before and Afterwards option only if you want to collect and copy a small number of objects.

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 the added objects are collected. Otherwise it may not be possible to activate these objects.

For example, an InfoCube can be used by transformation rules and queries.

Backup of System Copy (only in function area Transport Connection)

There is the additional option Save For System Copy for the grouping in the Transport Connection function area.

We recommend you make this setting when a source system needs to be copied and renamed.

You can avoid having to re-create objects for both SAP systems and BI systems in the following way:

                            a.      Collect the source-system-dependent objects in the BI system. 

                            b.      Save these to a request.

                            c.      Export the request.

                            d.      Delete the objects and rename the source system. Maintain the mapping table RSLOGSYSMAP so that the old system name Original Source System is changed to the new system as Target Source System.

More information: Defining the Target Source System

                            e.      Import the request in which you saved the source-system-dependent objects.