Show TOC

Checking SettingsLocate this document in the navigation structure

Use

Due to the complex relationships between objects, it is important to check the settings for the collected objects. This helps to avoid problems when transporting the objects or activating the BI Content.

Procedure

Transport

Check the Transport column in the Collected Objects screen area. The following objects are flagged automatically:

  • Objects that have not been displayed (objects that still have the $TMP package)

  • Objects that must be transported due to your selection in Groupings

    Caution

    Requests containing collected objects that are locked must be released before the current request is transported. In the log display, the system uses warnings to show for which objects there are still requests that must be released. These requests are also displayed in the Transport Request column.

You can add other objects manually.

Activating BI Content

In the Collected Objects screen area, check the columns Install, Match (X) or Copy and Active Version Available:

Transfer

The following BI Content objects are highlighted in this column by default:

  • Objects that are being transferred for the first time. There is not an active version of these objects in the system.

  • BI Content objects that have been redelivered in a new version. These objects can be identified by the BI Content time stamp in the corresponding object tables.

When setting this flag, check whether the checkbox refers to a folder or to an individual object: If the checkbox refers to a folder, the flag is set for all the objects belonging to this folder. If the checkbox refers to an individual object, the flag is only set for one single object and the flags for the other objects in the folder are not changed. The same applies if you remove the flag.

In the context menu, the following options are available for the installation:

  1. Install All Below

    The object in the selected hierarchy level and all objects in the lower levels of the hierarchy are selected as to Install.

  2. Do Not Install All Below

    The Install flags are removed for the object in the selected hierarchy level and all objects in the lower levels of the hierarchy.

Match (X) or Copy

If the SAP delivery version and the active version can be matched, a checkbox is displayed in this column.

With the most important object types, the active version and the SAP delivery version can be matched. When an object is being matched, specific object properties are compared between the active version (customer version) and the BI Content version (delivery version).

Caution

If you do not compare the versions, the delivery version is used and the active customer version is overwritten when you activate the BI Content. In other words, the delivery version is copied over the active version.

The table RSTLOGOPROP tells you which object types support matching. This table lists the transportable object types and describes their properties. The MERGEFL field indicates whether matching is supported for a particular object type.

The Match flag is set by default for objects that support this function. This prevents the customer version being overwritten unintentionally. Note that if the Install checkbox is not selected, the object is neither copied nor matched. In this case, the Match flag has no effect. The Match checkbox is evaluated as follows:

  • The active version of an object is matched to the delivery version, if you have configured the following settings for the object:

    • The Match flag is selected and

    • the Install checkbox is selected.

  • The active version of an object is overwritten by the delivery version, if you have configured the following settings for the object:

    • The Match flag is not selected and

    • only the Install checkbox is selected.

We recommend that you perform a match if you changed the customer version of an object.

Note

If an error occurs when you first try to activate the BI Content, deselect the Match flag when you next try to install the BI Content. By doing this, you can avoid inconsistencies in the modified version.

Note

Note regarding InfoSources: the InfoSource TRCS supports matching, but the 3.x InfoSource ISTD does not.

Note regarding transformations: when transformations are being matched, all the available transformations rules are retained and only new rules are added (for example, fields that are populated by a new routine). In this case, existing routines are not replaced. This can lead to errors after the BI Content is activated. Therefore, we recommend that you install transformations from the BI Content without matching and then modify the routines afterwards.

In the context menu, two options are available:

  1. Merge All Below

    The object in the selected hierarchy level and all objects in the lower levels of the hierarchy are selected as to Match.

  2. Copy All Below

    The Match checkboxes are deselected for the object in the selected hierarchy level and for all objects in the lower levels of the hierarchy. If the Install checkbox is also selected, these objects are copied from the delivery version to the active version.

Automatic and manual matching

It is necessary to identify whether the properties, which are compared between the active version and delivery version, can be matched automatically or whether this has to be done manually. If you are sure that the object will be used in the same way after you install BI Content, you can perform an automatic match for those properties. When performing matches manually you have to decide whether the characteristics of a property from the active version are to be retained, or whether the characteristics are to be copied from the delivery version.

Example

Example of an automatic match:

Additional customer-specific attributes have been added to the customer version of an InfoObject. In the BI Content version, two additional attributes that do not contain the customer-specific attributes have been delivered by SAP. To be able to use the additional attributes, the delivery version has to be reinstalled from BI Content. At the same time, the customer-specific attributes are to be retained. In this case, you have to set the indicator (X) in the checkbox. After installing the BI Content, the additional attributes are available and the customer-specific enhancements have been retained automatically. However, if you did not select the match indicator, the customer-specific enhancements in the customer version are lost.

Example of a manual match:

The customer version and BI Content version of an InfoObject have different texts. In this case the two versions have to be matched manually. When the BI Content is installed, a detail screen appears in which you specify whether you want to apply the text from the active version or from the BI Content version.

Usually when versions are matched, changes or additions to list-based settings (such as the list of attributes, list of fields, and list of processes involved) in BI Content are added to the customer version. Alternative settings (such as descriptions and checkboxes) are either retained from the customer version during automatic matching, or need to be manually matched. The most important properties for matching selected object types are listed below:

  • InfoObjects

    In relation to InfoObjects, it is important to differentiate between:

    • Characteristics

    • Time characteristics

    • Key figures and

    • Units

    Properties Matched Automatically:

    Properties Matched Manually:

    • Texts

      If there are no texts for characteristics in the active version yet, they will be taken over.

    • Attribute only (indicator)

    • Short and long text (description)

    • Time dependency of attributes

    • Transfer routine

    Properties Matched Automatically:

    Properties Matched Manually:

    • Compounding

      New InfoObjects are included in compounding

    • Attributes / navigation attributes

      New attributes are included.

      If an attribute is added by the customer, the settings for this attribute are transferred (for example, F4 sequence).

    • Application components

      If the entry for the active version is initial, the delivery version is used.

    • BEx display

    • Characteristic constants

    • Default member

    • Authorizations (indicator and field)

    • Selection (CHASEL)

    • InfoObject is document attribute

    • Data type

    • Length

    • Output length

    • Conversion routine

    • Lower case allowed (indicator)

    • Contains master data (indicator)

    • Master data is authorization relevant (indicator)

    • Export DataSource (indicator)

    • F4 query design

    • F4 query runtime

    • Check DataStore object

    • Contains text tables (indicator)

    • Texts are language-dependent (indicator)

    • Short, medium and long texts exist (each with indicator)

    • Default currency

    • GIS attribute

    • Hierarchies exist (indicator)

    Properties Matched Automatically:

    Properties Matched Manually:

    -

    • Type of key figure

    • Fixed unit

    • Fixed currency

    • Aggregation

    • Exception aggregation

    Properties Matched Automatically:

    Properties Matched Manually:

    -

    • See the table above ( Valid for Characteristics), if these properties are also relevant for the units.

  • InfoProvider

    When referring to InfoProviders it is important to differentiate between:

    • MultiProvider

    • InfoCubes

    • DataStore objects and

    • InfoObjects (see following table: Valid for All InfoObjects Named Above)

    Properties Matched Automatically:

    Properties Matched Manually:

    • New InfoObjects

      Any InfoObjects in the delivery version that do not exist in the active version are installed.

    • Manual matching is not necessary.

    Properties Matched Automatically:

    Properties Matched Manually:

    • New InfoProviders

      If InfoProviders in the delivery version do not yet exist in the active version, they are transferred.

    • Manual matching is not necessary.

    Properties Matched Automatically:

    Properties Matched Manually:

    • New dimensions

      If dimensions in the delivery version do not yet exist in the active version, they are transferred.

    • Manual matching is not necessary.

  • Process Chain

    With the process chain object type, those objects that exist in the delivery version but that do not yet exist in the customer version (such as additional objects in the process chain) are added automatically when the match is performed. Manual matching is not possible.

    Caution

    However, note that you may be able to activate or successfully execute the merged version of the process chain; this is because additional collection processes may be required under some circumstances to merge various process chain strings, or additional processes may have been added in the customer version. If this is the case, you need to manually adjust the generated process chain and activate it in process chain maintenance.

  • InfoObject Catalog

    With the InfoObject catalog object type, InfoObjects that are assigned to a catalog in the delivery version are transferred to the active version automatically. Manual matching is not necessary.

  • Transfer Rule

    With the transfer rule object type, those objects that exist in the delivery version but are not yet contained in the active version (for example, additional attributes) are added automatically when the match is performed. Manual matching is not possible.

Active Version Available

In this column, the following display options are available:

  • Green flag: The object is available in an active version. You decide whether you want to retain this version or reinstall the latest version of the object.

  • Date symbol: The object is already available in an active version. However, the active version belongs to an older BI Content release. We recommend that you install the latest version.

  • Gray flag: The object is available in the customer version. However, the object status is inactive. This indicates that the metadata for the object can be generated. The inactive object status indicates that the processed object is inconsistent and cannot currently be used for processing data. Install the object again from the delivery version (D version). If this is not enough to change the object status from inactive to active, the object has to be postprocessed. In the activation log, you can find notes on postprocessing.

    Example

    Postprocessing: An InfoObject can have the status 'inactive' if changes have been made to the structure at field level. Postprocessing the object involves converting the relevant tables in accordance with the activation log.

  • No flag: The object is not available in the active version.