Entering content frame

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.

See also: Structure linkDocuments.

This graphic is explained in the accompanying text Version Comparison

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

·        the active and modified versions

·        the active and Content versions

·        the modified and the Content versions

This graphic is explained in the accompanying text Transport Connection

You can choose and transport DataStore objects. All BI objects that are needed to ensure a consistent status in the target system are collected automatically.

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

You determine which other objects in the BI system also use a specific DataStore object. You can determine what effects changing an DataStore object in a particular way will have, and whether this change is permitted at the moment.

Business Content

In DataStore objects from Business Content, you can jump to the transaction to transfer the Business Content, copy the DataStore object, or compare it with the customer version. For more information see Structure linkBusiness Content (Versions).

Structure-Specific Properties of the InfoObject

With the context menu you can assign InfoObjects specific properties that are valid only in the DataStore object you are currently processing.

These settings correspond for the most part 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 also the corresponding section in Tabpage: Business Explorer.

You are also able to specify constants for characteristics:

When you assign a constant, a fixed value is assigned to a characteristic. This means that the characteristic is available on the database (for verifications, 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 for 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 verification for the storage-location master table runs correctly with this value for the plant. In the query, however, only the storage location appears as a characteristic.

Example 2:

For an InfoProvider, you make the setting that only the constant 2005 appears for the year. In a query on a MultiProvider that contains this InfoProvider, the InfoProvider is disregarded if the selection is for year 2004. Query performance is improved in this way as the system knows from the outset that it does not have to search for any records.

Special case:

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

For key figures, the settings Decimal Places and Display are available. See also the corresponding section in Tab Page: Additional Properties.

Info Functions

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

·        The log display for the save, activation and deletion runs of the DataStore object,

·        The DataStore object status in the ABAP/4 Dictionary and on the database,

·        The object catalog entry.

Performance Settings:

With Extras  ® DB Performance you can set the DB-Save Parameters. If you are using the database platform DB2 UDB for UNIX, Windows and Linux, you can also use Clustering.

 

Leaving content frame