Is "out of box" Planning flawed?

Question

Hi,
I just joined a company that is rolling out Planning v11.1 and noticed the same flaw in design that I found in Planning v9.3.1 over a year ago.
In fact, Pillar was designed right - Take Forecasting of Payroll Taxes for example- Pillar calculates Payroll Tax, but give planners a "Override Payroll Tax" in case the calculation does not work (e.g. for foreign entites).
However, Hyperion Planning does not have "manual Override" build into its "out of box" design. I had to introduce "Manual Override" members to almost all accounts (e.g. Salary, Depreciation, Op Ex accounts). Is it just me or are all other implementations of Hyp Planning customized heavily to all manual overrides to any account that is calculated by Business Rules or seeded?
Thanks in advance

Answer 1

Thanks Jake. Well, I think Pillar had given users a system closer to what most users want.
One more question:
I describe below a couple of ways to implement "override". Which do you prefer or use more often?
Using the example of "Payroll Taxes"
1) in Measures, add two members:
Misc_members
|____ Calculated Payroll Taxes (~)
|____ Manual Override Payroll Taxes (~)
Write a script that loads Calculated Payroll Taxes into Measure "Payroll Taxes", then override that if there there is a value in "Manual Override Payroll Taxes".
2) Add Children to Scenario:
Budget
|_____ Calculated Budget (~)
|_____ Manual Override Budget (~)
This method works for all measures including "Payroll Taxes".
Write a script that loads Calculated Budget into Budget then override that if there there is a value in "Manual Override Budget".
Edited by: user8806264 on Nov 19, 2009 9:36 AM
Edited by: user8806264 on Nov 19, 2009 9:37 AM