Identify the two true statements assuming you are working with a single application with multiple plan types.
A.
A user-defined custom dimension may exist in one plan type but not the other plan types.
B.
A user-defined custom dimension may have members in one plan type but not the remaining plan types.
C.
All members in the entity dimension must exist in all plan types.
D.
All members in the accounts dimension must exist in all plan types.
E.
All periods must exist in all plan types.
Explanation:
A: Properties for User-Defined Custom Dimensions include property Valid for Plan Types which is used to
select plan types for which the dimension is valid. Clearing this option makes all members of the dimension
invalidfor the deselected plan type.
User-defined custom dimensions differ from the Entity and Account dimensions in that you assign valid plan
types at the dimension level, not at the member level. All members of a user-defined custom dimension are
valid for plan types assigned at the dimension level.
Note: Specify one to three plan types for the application. A separate Essbase database is created for each plan
type. You cannot change the name or number of plan types after creating an application.
As you create accounts, entities, and other elements of the application, you associate them with plan types, so
the database for each plan type contains only information relevant to the plan type. This optimizes application
design, size, and performance.