Data Slices

Data slices are a concept for protecting the main data of a real-time enabled InfoCube against changes. This protection affects all input-ready queries and planning functions that use this InfoCube.

Example Example

If you want to ensure that certain plan versions cannot be changed after a certain point in time for example, and prevent current data from being overwritten, you can use a data slice containing these plan versions.

End of the example.

Prerequisites

Data slices are created on a real-time enabled InfoCube. They then affect all planning InfoProviders that contain this InfoCube. More information: InfoProviders.

Features

There are two types of data slice:

Data slices based on a selection. Here, you set the restrictions for the characteristics that you want to protect against changes.
Data slices based on an exit class. In the exit class, you can implement a customer-specific logic to protect data records.

The following basic rules apply for data slices:

If no data slices is defined for a real-time enabled InfoCube, any valid characteristic combination can be posted to this InfoCube (see Characteristic Relationships).
Every data record in the selection in a data slice is protected against changes. The corresponding cells in input-ready queries cannot be changed. You cannot use planning functions to change or save this kind of record. The data slices cumulate.
If a real-time enabled InfoProvider contains a data slice without any characteristic value restrictions, the data slice acts as a lock for postings of all types in the entire real-time enabled InfoProvider.
Once you have created a data slice it is activated automatically. The settings in the data slice definition have an immediate effect on the ability to update data. You can deactivate an existing data slice at any time (status inactive). This data slice is then ignored.

Activities

For more information on defining data slices in Planning Modeler, see Defining Data Slices .