Data Form - Super Slow - PBCS

elwayisgod

Hi Experts,

Hoping someone can shed some light on how PBCS works on the Data Forms.  I'll explain:

• Form is a review form only.  So it's really a report.  It has 4 columns that are formula columns ([A] - [B]).  Very basic.  Two columns reference a Scenario which is a Dynamic Calc.  It's sparse thus another issue
• Issue is in the Rows.  There are 3 dims referenced 'CC, Future and 30 Accounts).  All at iDescendants.  There are 450 total CC, 148 Future and 30 Accounts.
• We have suppression on and I'm toying with Valid Intersections.
• During forecast cycle when users open this form it takes approx 3 min to load.  So they are not happy.
• If I move CC dim from Rows to Page, it takes seconds to run.  But more cumbersome as some managers are in charge of hundreds of CC's and they want to see the big picture.

So there are just too many rows to populate.  I tried building and FR report that mimics this form and it won't even run.

When I remove the columns that are calculated, I do get better performance, but not by much.   My question is this:

When formulas are used in a Data Form column, when the form is opened is the calculation only happening on the rows that are displayed or does it calculate for all of them ahead of time to accomodate if user drills etc.?

Thanks in advance!!!

Robert Angel

Two main thoughts - if it is really a report then why not just using FRS and build a report, your 3 minutes would not happen there.

On hundreds of CCs, I assume these are linked to parents, grandparents etc up the hierarchy, why not enable dynamic user variable and let them change it at runtime to filter the subset of their hundreds of CCs that they see in one go?

And no, the rows not displayed but drillable could not be calculated in advance.

Robert Angel

See this for what I am referring to on user variable form, albeit Cameron's purpose is different -> Cameron's Blog For Essbase Hackers: Row-driven Focused Aggregations in Planning, finally

elwayisgod

I did build a report, with only the first column.   I didn't prompt, but suppose I could.  Issue there is some users would have to run the report 100 times or it would need bursted to Excel....

elwayisgod

Well one CC runs and finishes and it 35 pages long .   Issue here is we can't apply valid intersections.  That would be nice.