Additional Functions in DataStore Object Maintenance

Use

Documents

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

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

Transport Connection

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

Where-Used List

You can find out which other objects in the BW system use a specific DataStore object. You can determine how a given change would affect a DataStore object and whether or not this change is currently permitted.

Business Content

In BW Content DataStore objects, you can jump to the transaction for installing BW Content, copy the DataStore object, or compare it with the customer version. More information: Business Content (Versions).

Structure-Specific Properties of InfoObjects

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

Most 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 assign it a fixed value. This means that the characteristic is available in the database (for validation for example) but not displayed in the query anymore (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 in the application, you can assign a constant to the plant. Validation against the storage location master table is then performed using this value for the plant. In the query, the storage location only appears as a characteristic however.

Example 2:

For an InfoProvider, 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 2004. This improves query performance, as the system knows that it does not have to search for records.

Exception:

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

For key figures, you have the settings Decimal Places and Display. See the corresponding sections under Tab Page: Additional Properties..

Info Functions

Various information functions are offered for 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 catalog entry

Performance Settings:

To set the DB memory parameters, choose Start of the navigation path Extras Next navigation step DB Performance End of the navigation path . If you are using DB2 UDB for UNIX, Windows and Linux as your database platform, you can also use Clustering.