Hyperion Planning (MOSC)

MOSC Banner

PBCS recommended setup for importing actuals that do not need aggregation

edited Feb 6, 2017 11:39PM in Hyperion Planning (MOSC) 10 commentsAnswered ✓

I am in the process of designing a PBCS application in which we bring in approximately 14 columns of data for Actuals.  Originally, I thought I could import them in as dimensions into an ASO cube and then link the partitions to the BSO cube (8 dimensions)  (following essbase guidelines) but found there is not a way to do that in PBCS (limitation) according to Oracle SR.   

Out of the 14 dimensions- we only need to be able to budget/plan to 7 or 8 of them (BSO) with calculations; 6 or 7 of the actual data is just details or attributes.  Is there a way in PBCS to import the Actuals with the 14 columns, map them to the 7 or 8 to the dimensions in a BSO cube and be able to click on the BSO form to reference the actual data a details like you would in an Excel pivot table?  BSO has limitations and can only have a max of 9 dimensions and even

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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center