You have the following analysis requirement. Products roll up to Product Family which rolls up to Product Category. You also need to group Products by Product
Manager. Product Managers may manage one or more Products across product families. You do not need to create reports with Product Manager by Product
Family. You need to secure products by Product Manager for planning submissions.
You consider Shared members as a solution because of which two options?
A
Shared members provide cross tab reporting (Product Manager in the rows and Product Family across the column)
B
Shared members provide additional categorization but results in a smaller database then if you were to add Product Manager as a separate dimension
C
You can assign security to shared members
D
Shared members can be assigned to sparse members only
Correct Answer:
BC
The data values associated with a shared member come from another member with the same name. The shared member stores a pointer to data contained in the other member, and the data is stored only once. To define a member as shared, an actual nonshared member of the same name must exist.
Using shared members lets you use members repeatedly throughout a dimension. Essbase stores the data value only once, but it displays in multiple locations.
Storing the data value only once saves space and improves processing efficiency. (B)
Shared members must be in the same dimension. Data can be shared by multiple members.
Incorrect answers:
A: Attributes, not shared members, offers cross-tab, reporting
D. Shared member can be assigned to both dense and sparse members.
Show Answer
