Start of Content Area

Function documentation Additional Functions in DataStore Object Maintenance  Locate the document in its SAP Library structure

This graphic is explained in the accompanying text Documents

You can display, create or change documents for DataStore objects.

More information: Documents.

This graphic is explained in the accompanying text Version Comparison

You can compare changes in DataStore object maintenance for the following DataStore object versions:

●      Active and modified version

●      Active and Content version

●      Modified and Content version

This graphic is explained in the accompanying text Transport Connection

You can select and transport DataStore objects. The system automatically collects all BI objects that are required to ensure a consistent status in the target system.

This graphic is explained in the accompanying text Where-Used List

You can determine which other objects in the BI system use a specific DataStore object. You can determine the effect of changing a DataStore object in a particular way and whether this is permitted at a given time.

BI Content

In BI Content DataStore objects, you can jump to the transaction for installing BI Content, copy the DataStore object, or compare it with the customer version. More information: Installing BI Content in the Active Version.

Structure-Specific Properties of InfoObjects

In the context menu of the InfoObject, you can assign specific properties to InfoObjects. These properties are only valid in the DataStore object you are currently processing.

The majority of these settings correspond to the settings that you can make globally for an InfoObject. For characteristics, these are Display, Text Type and Filter Value Selection upon Query Execution. See the corresponding sections under Tab Page: Business Explorer.

You can also specify constants for characteristics.

By assigning a constant to a characteristic, you give it a fixed value. This means that the characteristic is available on the database (for validation, for example) but is no longer displayed in the query (no aggregation/drilldown is possible for this characteristic).

It is particularly useful to assign constants to compound characteristics.

Example

Example 1:

The storage location characteristic is compounded with the plant characteristic. If only one plant is ever run within the application, you can assign a constant to the plant. The validation for the storage-location master table runs correctly using the constant value for the plant. In the query, however, the storage location only appears as a characteristic.

Example 2:

For an InfoProvider, you specify that only the constant 2005 appears for the year. In a query based on a MultiProvider that contains this InfoProvider, the InfoProvider is ignored if the selection is for year 2004. This improves query performance since the system knows that it does not have to search for records.

Special Case:

If constant SPACE (type CHAR) or 00..0 (type NUMC) is assigned to the characteristic, specify character # in the first position.

Key figures have the settings Decimal Places and Display. See the corresponding sections under Tab Page: Additional Properties.

Info Functions

Various information functions are available with reference to the status of the DataStore object:

●      Log display for the save, activation, and deletion runs for the DataStore object

●      DataStore object status in the ABAP/4 Dictionary and on the database

●      Object directory entry

Performance Settings:

You choose Extras  → DB Performance to set the DB Memory Parameters. If you are using the database platform DB2 UDB for UNIX, Windows and Linux, you can also use clustering.

 

End of Content Area