Show TOC

Defining Data SlicesLocate this document in the navigation structure

Use

You can use data slices to protect the central data in a real-time InfoCube (or the data in a DataStore object for direct updates in planning mode) against changes. This protection affects all InfoProviders from planning that contain this InfoProvider. It affects all input-ready queries and planning functions that use this InfoProvider.

Note

For more information, see Data Slices.

Prerequisites

You are on the Data Slices tab page and have selected the required InfoProvider.

Procedure

The display mode provides you with an overview of the available data slices. In change mode, you can change data slices and define new data slices:

  1. To create a data slice, choose Create New Data Slice. The row of the data slice to be created is selected.

  2. In the Description field, enter a text for the new data slice.

  3. Specify whether the data slice should be based on a selection or an exit class.

  4. If the data slice is based on a selection, set the required characteristic values in the lower screen area:

    • Select the characteristic that you want to restrict.

    • Select the symbol in the Values column. The dialog box for specifying the characteristic restriction appears.

    • In the value list, select one or more values. The selection can also contain variables, provided that the variables do not send any dialogs at runtime.

    • Choose Add and save your selection by pressing OK.

  5. If you want the data slice to be based on an exit class, enter the name of the exit class.

    • Under Restricted, choose the characteristics that you need in the exit. You will only get the current values for these characteristics in the exit. If you are also interested in the initial values in the exit, set the flag in the also # column. If this flag is not set for a characteristic, the exit is not called for aggregation levels that do not contain this characteristic. The characteristic value would be initial in this case.

    • The exit class must implement interface 'IF_RSPLS_DS_EXIT'. Only these types of classes are offered for editing in maintenance. We recommend that the customer class inherits from template class 'CL_RSPLS_DS_EXIT_BASE'. The template class itself can be run directly, but does not execute an action. Re-implement method 'IS_PROTECTED'. Note the example source code given in the template class too: An infrastructure for buffering can be provided here.

  6. If you want the data slice to be initially inactive, remove the flag from the Active field.