Profitability and Cost Management Validations

For Profitability and Cost Management, the following conditions are validated:

Table 11. Profitability Validations

Validation LevelValidations
Application
  • The name of the application must be seven characters or fewer, and cannot contain special characters.

  • At least one dimension must be set to POV type. Up to four dimensions may be marked as POV dimensions. Only one occurrence of each POV dimension class is allowed.

  • At least one business dimension must be defined.

  • At least one Measures dimension must be defined.

  • At least one AllocationType dimension must be defined.

  • There is only one dimension of type “Account.”

  • There is only one dimension of type “Entity.”

  • Application names do not include Essbase special characters and reserved words.

Dimension
  • Root members of business dimensions must have the ASO and BSO data storage set to LabelOnly.

  • Dimension Sort Order is set for all dimensions in the model, excluding Alias and UDA dimensions, and satisfies the following conditions:

    • A dimension sort order must be set for every dimension in the model, except Alias and UDA dimensions.

      Note:

      The Alias and UDA dimensions are ignored for Dimension Sort Order.

    • The dimension sort order must be sequential.

    • Measures dimension is set to 1 by default.

    • AllocationType dimension is set to 2 by default.

    • POV and business dimensions are set to 3 or higher.

    • Attribute dimensions are sorted as the last dimensions.

      For example, if you have four attribute dimensions in a sequence of 12 dimensions, the attribute dimensions must be set as 9, 10, 11, and 12.

  • Duplicate members do not exist in the same dimension.

  • POV dimensions must have at least one member.

  • Attribute dimensions must satisfy the following conditions:

    • Only a Level-0 member from the attribute dimension may be assigned as an attribute.

    • Attributes may be assigned only to members at the same level in the base dimension.

    • Attribute dimensions can only be associated with sparse dimensions.

Member
  • Allow only ASO and BSO data storage to be defined.

  • No shared members are allowed in the first Gen 2 member.

  • A Shared Member must always appear after its corresponding Base Member in the outline order.

  • NoMember must be set as the last generation 2 member for all business dimensions and must be set to Ignore (~) in the Property Grid.

    Note:

    This requirement does not apply to POVs, Measures, AllocationType, Alias, UDA, or Attribute dimensions.

  • Shared members must reside in a Dynamic hierarchy, using one of the following methods:

    • The Gen 1 member is HierarchyType=dynamic

    • The Gen 1 member is HierarchyType=HierarchiesEnabled, and the Gen 2 ancestor of the shared member is HierarchyType=dynamic

  • No duplicate member names or aliases exist for any members within the dimension.

  • Member names do not include Essbase special characters and reserved words.