Select language:

Function documentation InfoProvider  


InfoProviders that contain real-time InfoCubes provide the data basis for BI Integrated Planning. Aggregation levels are a type of virtual InfoProvider and are created on the basis of a real-time InfoCube, or a MultiProvider that contains InfoCubes of this type. Aggregation levels are specifically designed so that you can plan data manually or change it using planning functions.

For more information about the types of InfoProvider, see:

  Real-Time InfoCubes



In the Modeling functional area of the Data Warehousing Workbench, you create InfoProviders as the data basis for BI Integrated Planning.

For more information, see InfoProviders, Creating InfoCubes, and Creating MultiProviders.

In the Planning Modeler, you select the InfoProvider that you want to use as the data basis for BI Integrated Planning. On the Aggregation Levels tab page, you create one or more aggregation levels for this InfoProvider.

For more information, see Aggregation Levels.


You have created a suitable InfoProvider as the data basis for BI Integrated Planning and filled it with data.


InfoProvider Selection

You can restrict the number of InfoProviders displayed by specifying the technical name or description or by making an entry for last changed by.

You can change, check and save the selected InfoProviders.


On the InfoObjects tab page, the system displays the InfoObjects that belong to the InfoProvider (see InfoObject). They are listed in the following tables:

  Dimensions, with the characteristics assigned to them

  Navigation Attributesfor the characteristics contained in the InfoProvider

  Key figures


Under Settings, you can choose to display additional columns. 

Characteristic Relationships and Data Slices

In change mode you can define the permitted combinations of characteristic values in the form of characteristic relationships and create data slices for the data that you want to protect for real-time-enabled InfoCubes.

For more information, see Characteristic Relationships and Data Slices.

Default Key Date for Planning

On the Settings tab page in change mode, you can set a Key Date as the default key date for planning. If time-dependent objects, such as attributes or hierarchies, are used in objects of the planning model, you can always refer to the default key date for planning. In this way, you can ensure that a uniform key date is used in the planning model. The objects in the planning model that are relevant for this are characteristic relationships, data slices and parameters of planning functions.

For more information see Standard Key Date in Planning Functions.




Was this page helpful to you?