Data Slices

The data slice is a concept for protecting the main data of a planning-relevant InfoProvider against changes. This protection affects all input-ready queries and planning functions that use this planning-relevant InfoProvider.

Data slices are created on a real-time InfoCube, on a DataStore object for direct updates in planning mode, or on a local provider in BW Workspace. They affect all planning InfoProviders that contain this planning-relevant InfoProvider. More information: InfoProviders.

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 a data slice is not defined for a planning-relevant InfoProvider, any valid characteristic combination can be posted to this planning-relevant InfoProvider (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 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 a data slice at any time (status inactive). This data slice is then ignored.

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