Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Hyperion Essbase (MOSC)

Shared member issue in Essbase Studio

Jun 5, 2014 1:53AM edited Jun 13, 2014 12:00PM in Hyperion Essbase (MOSC) 1 commentAnswered

Hi all,

I'm facing an issue with regards to creating shared members using Essbase Studio (v11.1.2.3.00).

(Keeping it simple) - My hierarchy should look like this:

Customer

-AllCustomers

- AC_Gen2 (AC2_Alias)

- AC_Gen3 (AC3_Alias)

-A (Alias)

-B (Alias)

-C (Alias)

-VIPCustomers

- VC_Gen2 (VC_2Alias) <<-- This is different field in the database from Gen2 under AllCustomers

-A (VC_Alias) (Shared)

-B (VC_Alias) (Shared)

-C (VC_Alias) (Shared)

I could get this hierarchy successfully:

Customer

-AllCustomers

- Gen2 (AC2_Alias)

- Gen3 (AC3_Alias)

-A (Alias)

-B (Alias)

-C (Alias)

-VIPCustomers

- Gen2 <<-- Notice Missing alias here

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month