Considerations for Working with Planning Dimensions

You create hierarchical relationships within dimensions by creating and organizing members, which are components of dimensions. You can add dimension members individually or using Import Profiles. Dimension names must use the conventions detailed in Naming Restrictions for Dimensions, Members, and Aliases.

Sparse dimensions lack data values for the majority of member combinations, and have a low percentage of available data positions filled. Dense dimensions have a high probability that one or more data points are occupied in every combination of dimensions.

To optimize database performance, designate dimensions as sparse or dense. If a dimension is sparse, Planning calculates only data values that are occupied in each dimension combination. This optimizes performance by decreasing calculation time and lowering disk usage. By default, Planning designates the Account and Period dimensions as dense and other dimensions as sparse.

Dimension hierarchies define structural and mathematical relationships, and consolidations between members in the database. Members of the same level that belong to the same dimension or member are called siblings. Members that belong to a dimension are called children of the dimension. Members that belong to a member are called children of that member.

For important information about applications, see Properties Applicable to All Planning Dimensions and Properties Common to Multiple Planning Dimensions. Additional considerations include:

  • New dimensions created in the Dimension Library do not have any default associations.

  • For dimensions loaded from a flat file, the association must be specified in the flat file.

  • For applications transformed from Planning to Performance Management Architect, the associations may be assigned.

  • It is not necessary to associate a Smart List with a dimension (such as Account or Entity), but Smart Lists are associated in the Smart List property field. Smart Lists should be associated with members in the Shared Library. Any member associated with a Smart List should have its Data Type set to Smart List.