Checking Settings 

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 selected automatically:

●      Those that have not been displayed, that is, objects that still have package $TMP.

●      Those that must be transported according to your selection in  Groupings.

 

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

You can add other objects manually.

Activate Content

Check the following columns in the Collected Objects area of the screen:

Install

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

●      Objects that are being installed for the first time. There is no active version of these objects in the system.

●      Objects that are being delivered again by BI Content in a newer version. These objects can be identified by the BI Content time stamp in the corresponding object tables.

When you set this flag, check whether the checkbox is intended for a folder or an individual object: If the checkbox is for a folder, the flag is set for all objects that belong to this folder. If the checkbox is for a specific object, the flag is set for this specific object only and the flags for the other objects in the folder are not changed. The same applies when you deselect this flag.

The context menu has two installation options:

...

...

       1.      Install All Below

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

       2.      Do Not Install Any Below

The Install flags are deselected 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 compared, a checkbox is displayed in this column.

The active version and SAP delivery version can be compared for the most important object types. The RSTLOGOPROP table 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.

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.

Note that the InfoSource TRCS supports matching, but the 3.x InfoSource ISTD does not.

When matching is performed, the customer version and the BI Content version of particular properties of the object are compared. It is also necessary to identify whether these properties can be matched automatically or whether this has to be done manually. If you are sure that an object will be used in the same way after you install BI Content, you can automatically match the properties of this object. When performing matches manually, you have to decide whether you want to retain the characteristics of a property from the active version, or whether you want to apply the characteristics from the delivery version.

 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 the BI Content. The customer-specific attributes should be retained however. To do this, you have to set the flag (X) for matching in the checkbox. When the BI Content is installed, the additional attributes are available and the customer-specific enhancements are retained automatically. If you did not select the match flag however, the customer-specific enhancements in the customer version are lost.

 Example of a manual match:

The customer version and content version of an InfoObject have different texts. You therefore need to match the two versions 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 content version.

The Match flag is set by default to prevent you from inadvertently overwriting the customer version. If the content of the SAP delivery version is to be matched against the active version, you have to set the Install flag separately.

The active version is overwritten by the delivery version if:

●      The Match flag is not set, and

●      Only the Install flag is set.

In other words, the delivery version is copied to the active version.

If the Install flag is not set, the object is neither copied nor matched. In this case, the Match flag has no effect.

We recommend performing a match if you have changed the customer version of an object.

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. This helps to avoid inconsistencies in the modified version.

The context menu has two options for matching:

...

...

       1.      Merge All Below

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

       2.      Copy All Below

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

The most important properties that are taken into account when versions are matched for a selected object type are listed below. Generally, 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.

InfoObjects

When talking about InfoObjects, it is important to differentiate between:

●      Characteristics

●      Time characteristics

●      Key figures and

●      Units

Valid for All InfoObjects Named Above

Properties Matched Automatically:	Properties Matched Manually:
●      Texts If there are no texts for characteristics in the active version yet, these are taken over.	●      Exclusive attribute (flag) ●      Short and long text (description) ●      Time dependency of attributes ●      Transfer routine

Valid for Characteristics

Properties Matched Automatically:

Properties Matched Manually:

●      Compounding New InfoObjects are added to compounding. ●      Attributes/navigation attributes New attributes are added. If an attribute has been added by the customer, the settings for this attribute are applied (F4 sequence, for example). ●      Application component If the entry for the active version is initial, the delivery version is used.

●      BEx display ●      Characteristic constant ●      Default member ●      Authorizations (flag and field) ●      Selection (CHASEL) ●      InfoObject is document attribute ●      Data type ●      Length ●      Output length ●      Conversion routine ●      Lowercase allowed (flag) ●      Contains master data (flag) ●      Master data is authorization relevant (flag) ●      Export DataSource (flag) ●      F4 query design ●      F4 query runtime ●      Check DataStore object ●      Contains text tables (flag) ●      Texts are language-dependent (flag) ●      Short, medium and long texts exist (each with flag) ●      Default currency ●      GIS attribute ●      Hierarchies exist (flag)

Valid for Key Figures

Properties Matched Automatically:	Properties Matched Manually:
-	●      Type of key figure ●      Fixed unit ●      Fixed currency ●      Aggregation ●      Exception aggregation

Additional Validities for Units

Properties Matched Automatically:	Properties Matched Manually:
-	●      See the table above (Valid for Characteristics) if these properties are also relevant for the units.

InfoProvider

When talking about InfoProviders, it is important to distinguish between:

●      MultiProviders

●      InfoCubes

●      DataStore objects and

●      InfoObjects (see Valid for All InfoObjects Named Above table)

Valid for All InfoProviders Named Above:

Properties Matched Automatically:	Properties Matched Manually:
●      New InfoObjects If InfoObjects in the delivery version do not yet exist in the active version, they are copied.	●      Manual matching is not necessary.

Additional Validities for MultiProviders

Properties Matched Automatically:	Properties Matched Manually:
●      New InfoProviders If InfoProviders in the delivery version do not yet exist in the active version, they are copied.	●      Manual matching is not necessary.

Additional Validities for InfoCubes

Properties Matched Automatically:	Properties Matched Manually:
●      New dimensions If dimensions in the delivery version do not yet exist in the active version, they are copied.	●      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.

Note however that you might be able to activate or execute the merged version of the process chain. This is because additional collection processes might be required in order to merge various process chain strings, or additional processes might 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 copied 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 that do not yet exist in the active version (such as additional attributes) are added automatically when the match is performed. Manual matching is not possible.

Active Version Available

The following display options are offered in this column:

●      The object is available in the active version. You decide whether to retain this version or to reinstall the latest version of the object.

●      Date icon: The object is already available in the active version. The active version is from an older BI Content release however. We recommend installing the latest version.

●      Gray icon : The object is available in the customer version. The object status is inactive though. 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 does not change the object status from "inactive" to "active", the object has to be post-processed. You can find information about postprocessing in the activation log.

Postprocessing: An InfoObject might have status inactive if changes have been made to the structure at field level. Postprocessing the object involves converting the relevant tables as specified in the activation log.

●      No flag: There is no active version of this object.