Validation Rules for Default Members

Default members in the reporting cube store the data that is moved from the source Planning application. If any of the following constraints are not met, or if a dimension in either application isn't mapped and has no valid default member, then a mapping isn't valid and an error message is displayed.

Rules:

  • If the reporting cube is an aggregate storage database, then the default members must be level 0 members.

    For information on block versus aggregate storage application databases, see the Administering Oracle Analytics Cloud - Essbase .

  • If the reporting cube is a block storage database, then the default members can be any members with the Store Data property.

  • If the Planning application has only dimension to dimension mappings, then the default members can be any level or data storage type.

  • If the Planning application has Smart List to dimension mappings, then default members must be only level 0. In addition, the source cube must contain a dense Account dimension with at least one member associated with a Smart List.

  • If Descendants (Acct_Default) is selected in a mapping, the Acct_Default member must exist in the reporting cube.

Note:

Mappings that were once valid can become invalid if dimensions, members, or Smart Lists are renamed, removed, or added. If a target cube has a change in dimensionality, you must select the corresponding application mapping on the Map Reporting Application screen and click Refresh icon to refresh the data.