Hyperion Planning (MOSC)

MOSC Banner

Shared Hierarchy definitions in Hyperion Planning

edited Jan 1, 2018 4:00AM in Hyperion Planning (MOSC) 5 commentsAnswered

Assume the following case,

Account

|--------->AG1000 (Dynamic Calc)

                    |-------->AP1000 (Dynamic Calc)

                                   |---------->AC1000 (Store)

                                   |---------->AC1001 (Store)

                    |--------->AP2000 (Dynamic Calc)

                                   |---------->AC2000 (Store)

                    |--------->AP3000 (Dynamic Calc)

                                   |---------->AC3000 (Store)

|---------->SH1000 (Dynamic Calc)

                    |--------->AC1000 (Shared)

                    |--------->AC1001 (Shared)

|----------->SH1002 (Dynamic Calc)

                    |--------->SH1000 (Shared)

                    |--------->SH1001 (Shared)

|----------->SH1001 (Dynamic Calc)

                    |--------->SH1000 (Shared)

                    |--------->AC2000 (Shared)

Is there any limitations/issues defining this Base & Shared Hierarchy in Hyperion Planning/Essbase?

Tagged:

Howdy, Stranger!

Log In

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

Register

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

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center