At least one key figure and one characteristic have to be included in the aggregation level.
● The key figures used have to have the database aggregations SUM, MIN or MAX. With MIN or MAX, key figure values can only be displayed. They cannot be changed using manual planning or planning functions.
● For key figures of type date or time, only the data type u2018DECu2019 is supported.
● Referencing key figures (and thus also non-cumulative key figures or elimination of internal business volume) are not supported in aggregation layers.
● If a characteristic is compounded and used in an aggregation level, the aggregation level must also contain all compounding "parent" characteristics.
● If a key figure is used in an aggregation level and does not have a fixed unit of measure or currency, the aggregation level must contain the associated characteristic for the unit.
● If a key figure with exception aggregation is used in an aggregation level, the aggregation level must also contain the characteristic for exception aggregation if it occurs in the underlying InfoProvider
● The aggregation level inherits a navigation attribute from the underlying InfoProvider if it includes the basic characteristic of the navigation attribute. Note that the navigation attribute for an aggregation level is not visible in the Planning Modeler. It is only visible in the Query Designer.
● An aggregation level cannot be created on MultiProviders if a characteristic of an InfoProvider contained in the MultiProvider supplies two different characteristics in the MultiProvider.
● If a characteristic on the InfoProvider that serves as the basis for an aggregation level is constant, this characteristic has to be included in the aggregation level.
Hope this helps.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.