You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Data retrieval time in SmartView for Level 0 member is worse than for its ancestor

in Planning 5 comments

Summary:

Say I have a retail operations database with an Employee Type dimension that has three children:

Employee Type

  • Customer-facing employees (CFEs)
  • Back office employees (BOEs)
  • NoEmployee

CFEs have different employee types, such as clerks, supervisors, and shift managers. BOEs also have different employee types, including warehouse operators, administrative staff, and drivers. NoEmployee is a Level 0 member.

Some of my metrics, such as Revenue, Fleet Maintenance, or Warehouse Rent are recorded for the entire operation and loaded to the NoEmployee member. Others, such as compensation or number of employees are employee-type specific and loaded to a specific employee type member. There are several EPBCS cubes and one Essbase database with the same structures and data; EPBCS cubes are used for data input and some reporting; Essbase is used to consolidate data from EPBCS databases.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!