
A local provider is not available for a MultiProvider.
Aggregation levels are a type of virtual InfoProvider. They are based on a planning-relevant InfoProvider or a MultiProvider that contains an InfoProvider of this type. Aggregation levels are specifically designed so that you can plan data manually or change data using planning functions.
For more information about InfoProviders, refer to the following links:
Characteristic Relationships and Data Slices
In the context of BW-integrated planning, you can define the permitted combinations of characteristic values for planning (in the form of characteristic relationships) and create data slices for the selected data that you want to protect.
If the generic types of characteristic relationships (attribute, hierarchy, DataStore) and data slices (selection) do not meet specific customer requirements, you can implement characteristic relationships and data slices of type Exit.
Default Key Date for Planning
You can still create a key date for an InfoProvider, which is suitable for planning, as the default key date for planning. If time-dependent objects (such as attributes or hierarchies) are used in objects in the planning model, you can always refer to the default key date for planning. This allows you to ensure that the same key date is used throughout the planning model. The planning model objects that are relevant for this are characteristic relationships, data slices and parameters of planning functions.
More information: Default Key Date in Planning Functions.
In Planning Modeler, you can select InfoProviders that you want to use as the data basis for BW Integrated Planning. More information: Selecting InfoProviders.