Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Andere mochten auch
Andere mochten auch (20)
Ähnlich wie Redesigning Hyperion Planning - Is going from Block Storage (BSO) to Aggregate Storage (ASO) an option for you?
Ähnlich wie Redesigning Hyperion Planning - Is going from Block Storage (BSO) to Aggregate Storage (ASO) an option for you? (20)
Mehr von finitsolutions
Mehr von finitsolutions (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Redesigning Hyperion Planning - Is going from Block Storage (BSO) to Aggregate Storage (ASO) an option for you?
- 1. Redesigning Hyperion Planning Is going from Block Storage (BSO) to Aggregate Storage (ASO) an option for you? January 15, 2016 Cindy Eichner, Director ©2016
- 2. ©2016 Agenda Page 2 • Finit Introduction • Options • ASO Plan Types • Hybrid • Map to Reporting Application • Case Study • Questions and Answers
- 3. ©2016 About the Presenter Page 3 Cindy Eichner ceichner@finitsolutions.com • Director of Finit’s Planning and Essbase Practice • Delivering performance management solutions for over 30 years while specializing in Hyperion products for over 18 years • Certified implementation specialist • Hyperion Planning • Essbase • Hyperion Financial Management (HFM) • Hyperion Data Relationship Management (DRM) • Frequent speaker at KScope, OOW
- 5. ©2016 Finit Delivers Unmatched Experiences Page 5 At Finit, we believe that value and success is not just the end achievement of a project – we believe that value and success is achieved through the entire journey and experience of delivering a solution to a need. Our values, process and craft guide us in this effort: • Advocacy & Integrity • Craftsmanship & Delivery • Stewardship We combine our values, process and craft with your goals and team to deliver more than just a solution: We deliver an unmatched experience.
- 6. ©2016 Our Culture We employ approaches inside Finit to align our employees to our values and principles: • We use employees, not contractors • We actively and continually seek feedback • We base employee compensation on customer satisfaction, not billable hours • We invest in training and growth in our consultants • We foster innovation and collaboration • We are debt free and are committed to the success of our clients’ programs before the profit of ours Page 6
- 7. ©2016 Our Services and Solutions Page 7 We craft, deliver, and sustain solutions that improve an organization’s capabilities, controls and insights in the following areas: • Financial Close & Consolidation • Financial Planning • Profitability & Management Reporting • Integration and Infrastructure
- 8. ©2016 Our Company Page 8 • Founded in 2002 • 80 employees in 21 states • All Finit owners are actively involved in Finit’s operations • We provide solutions and support during and after implementations • Finit Answers
- 9. ©2016 Finit Customer Success Page 9 Our values, culture, and approach to becoming a trusted advisor to our customers has led to 100% customer success for every Finit client (250+) and for every Oracle Hyperion project (450+)
- 12. ASO Plan Type
- 13. ©2016 ASO and Planning • Planning imposes constraints on both BSO and ASO • Required dimensions • Features not supported • Administration considerations • Maintenance • Complexity and points of failure • ASO specific maintenance; i.e. buffers, otl compactions • ASO licensing is not part of Planning • Server memory requirements for ASO plan types • Different from BSO • ASO aggregation is performed in memory Page 13
- 14. ©2016 ASO Plan Type Page 14 • New with Version 11.1.2.3 • Separate Essbase application for each ASO plan type • NO required dimensions – Entity, Account, Scenario, Version, Year, Period • Approvals may not apply if all approval dimensions are not included • Will work with Forms, data loads, Smart View Planning provider
- 15. ©2016 ASO Plan Type Page 15 • May have one ASO plan type for each BSO plan type plus one consolidating ASO plan type • Must have at least one BSO plan type
- 16. ©2016 ASO Plan Type Page 16 • May specify different Data Storage and formulas for members for each plan type
- 17. ©2016 ASO Plan Type Page 17 • Copy Data does not work • No Dynamic Time Series • May not be used with EPMA (and no data sync) • No XREF on ASO • Can have XREF from ASO to BSO • Security filters not created or updated • All access through Planning or for FR through Planning ADM driver
- 18. ©2016 ASO Plan Type Page 18 • No Fx • How many ASO plan types are in production? • No such thing as suppress missing blocks • Forms which drill into two or more dimensions may not (do not) render • Stored hierarchies only use “+” or “~” • Users must enter as a negative
- 19. ©2016 ASO Plan Type • Calc Manager business rules • Procedural calcs are available to calculate on level 0 members • May be associated with a form • May run a BSO rule from an ASO form • Pass variables • Run on save • BSO business rule may use @CalcMgrExecuteMaxL… • May run from any plan type • May address any plan type Page 19
- 20. ©2016 ASO Plan Type Page 20 • Administrators have to learn how to use the ASO engine and all associated maintenance • Formulas use MDX syntax • Restructures impact both database engines • Have to consider both engines when performing maintenance • Have to perform some maintenance with MaxL and scripts for outline compacts, merging slices, etc. • Business rule complexity
- 21. ©2016 ASO Plan Type Page 21
- 22. Hybrid
- 23. ©2016 Hybrid • BSO level 0 • ASO-like aggregation • Hybrid Essbase first available with 11.1.2.3.500 • Essbase.cfg setting • ASODYNAMICAGGINBSO [App [DB]] None|Partial|Full • Change upper level members to dynamic • Many functions are now supported in 11.1.2.4 • Only 16 functions were supported in 11.1.2.3.500
- 24. ©2016 Hybrid • Supported functions • Unsupported functions
- 25. ©2016 Hybrid • May be used with EPMA • Queries may use Hybrid Aggregation Enabled, not use it, or use both • Queries will eventually return data • Use Essbase.cfg settings: • QRYGOVEXECBLK [App [DB]] n • QRYGOVEXECTIME [App [DB]] n
- 26. ©2016 Hybrid • Not supported for hybrid mode • Attribute calculations • Formulas with cross-dimensional operators • Dynamic Calc members with formulas that are a target of transparent partitions • Queries which include both two-pass and one-pass dynamic calc members from the same dimension • XOLAP • Text measures / text lists
- 27. ©2016 Hybrid Page 27 • Formulas can run in hybrid mode in these cases • Sparse-to-Sparse • The formula is set on a sparse dimension member, and the formula only references member combinations from sparse dimensions. • Dense-to-Dense • The formula is set on a dense dimension member, and the formula only references member combinations from dense dimensions. • Sparse-to-Dense/Sparse • The formula is set on a sparse dimension member, and the formula references member combinations from both dense and sparse dimensions. The dense dimension members must be stored.
- 28. ©2016 Hybrid Page 28 • PAG and IND files for level 0 • ASO directory structure for ASO • Directories are created when application is started • Directories are removed when application is stopped • If database was ever set to be hybrid but no longer is then directories still create
- 29. Map to Reporting Application
- 30. ©2016 Map to Reporting Application Page 30 • Introduced in version 11.1.2.0 • Transfer data from within Planning to another Essbase database • Dimension mapping defined in Planning • PushData.exe utility (11.1.2.1) available on server • Batch jobs • Scheduled pushes • May map Smart Lists to dimensions • Report by Smart List • Smart Lists may be synchronized to the reporting app
- 31. ©2016 Map to Reporting Application Page 31 • Reporting app may not have attribute dimensions • Reporting app may not have “Duplicate Members Allowed” option • Cannot map member names
- 32. ©2016 Setting Up Map to Reporting Application Page 32 • Runs a DATAEXPORT calc script • Loads to reporting app
- 33. ©2016 Smart Push • New in version 11.1.2.4 • Available now in PBCS • To be included with next full release of on premise Hyperion Planning • Uses Map to Reporting specifications with forms • Utilizes the form’s POV to move data on save • Game changer! Page 33
- 34. Case Study
- 35. ©2016 Case Study Page 35 • Original application • Background • The First Solution Which Did Not Work • Alternate Solution #1 • Alternate Solution #2 • Alternate Solution #3 • Comparison of Four Solutions
- 36. ©2016 Original Application Page 36 • 2 plan types • Plan – BSO • Sales – BSO • A lot more data is being retained than originally scoped • Poor user experience at save with calculations and for data retrieval • Poor consolidation performance • EPMA maintained app with shared dimensions to HFM Original Sales (BSO) Plan (BSO)
- 37. ©2016 Original Application Page 37 • Nightly defragmentation takes over 2 hours • Restructures take 4 hours • Aggregation of one planning cycle will take over 1 hour by the end of the day • Consolidated Sales plan type in production is over 36 GB in size (pag and ind files)
- 38. ©2016 Original Application Page 38 • Dimensions • Standard eight for multi-currency application • Additional 4 custom dimensions • 1 attribute dimension
- 39. The First Solution Which Did Not Work
- 40. ©2016 First Solution Which Did Not Work Page 40 • Transparent Partition from an Essbase ASO cube • SalesASO holds all historical data • Sales plan type holds only active data (current year actual and current planning cycle data) with total size of 2-3 GB • User experience does not change • Nightly process keeps meta data in sync • Drop partition and delete SalesASO • Rebuild SalesASO from Sales outline • Reload SalesASO • Create partition • Worked great with ad hoc and reports Solution Which Did Not Work Sales (BSO) Plan (BSO) SalesASO (ASO) Transparent Partition
- 41. ©2016 What Did Not Work? • Planning forms which suppress data (rows, columns, blocks) do not work with transparent partitions • Even if the form is only pulling data that actually resides in the Sales plan type and does not come through the partition • Known bug that Oracle has not fixed and probably will not since ASO plan types are now available • Show stopper as forms without suppression were unwieldy and took forever to render (if at all) Page 41
- 42. Alternate Solution #1 Additional BSO Plan Type
- 43. ©2016 Alternate Solution #1 – Additional BSO Page 43 • 3 plan types • Plan – BSO • Sales – BSO • SalesInp – BSO • Only one planning cycle in SalesInp at a time • No change to original FDM processes • EPMA application • Additional business rules to move data to Sales and Plan from SalesInp at time of save Additional BSO Sales (BSO) Plan (BSO) SalesInp (BSO)
- 44. ©2016 Alternate Solution #1 – Additional BSO Page 44 • New composite forms with read only Sales referential data and writeable SalesInp
- 45. ©2016 Alternate Solution #1 – Additional BSO Page 45 • Additional business rules to aggregate Sales on demand and nightly during defragmentation process • Additional business rules to move data to SalesInp from Sales to initialize planning cycle • Sales and SalesInp outlines are identical • HSP_NOLINK UDA added
- 46. ©2016 Alternate Solution #1 – Additional BSO Page 46 • Takes a bit more time to administer • Adds complexity • Much improved user experience • Faster saves • Faster consolidations • Users and upper level management now have to wait until a consolidation happens to see total company compared to historical data in the same retrieve
- 47. Alternate Solution #2 Hybrid Plan Type
- 48. ©2016 Alternate Solution #2 – Hybrid Page 48 • 2 plan types • Plan – BSO • Sales – Hybrid • Essbase.cfg setting • ASODYNAMICAGGINBSO S_Hybrid Sales FULL • No change to original FDM processes • EPMA application • Customer and Entity dimensions parent levels still stored Hybrid Sales (Hybrid) Plan (BSO)
- 49. ©2016 Alternate Solution #2 – Hybrid • Material dimension all dynamic • EndUse dimension all dynamic Page 49
- 50. ©2016 Alternate Solution #2 – Hybrid Page 50 • Aggregation business rules changed • Calculate level 0 members and aggregate two remaining “sparse” dimensions • Dynamic members not allowed in FIX…ENDFIX • Aggregate TotalEndUse and TotalMaterial as needed using @SUMRANGE
- 51. ©2016 Alternate Solution #2 – Hybrid Page 51 • Retrieves • Fast retrieves will enable Hybrid Aggregation Mode • Very slow retrieves will use the traditional calculation engine due to complex formulas • Some retrieves will use both • Retrieving top of the house is slow
- 52. ©2016 Alternate Solution #2 – Hybrid Page 52 • Forms were slower at first • Redesigned to eliminate member with formula which uses cross dimensional members • Resulting in changed user experience
- 53. ©2016 Alternate Solution #2 – Hybrid Page 53 • Many more changes to business rules • Material and EndUse parent level calculations • Data movement and allocations • Many, many changes to forms • Member with cross dimensional member formula no longer utilized to control column suppression • Different user experience
- 54. Alternate Solution #3 Writeable ASO Plan Type
- 55. ©2016 Alternate Solution #3 – Writeable ASO Page 55 • 2 plan types • Plan – BSO • Sales – ASO • Rearranged hierarchies for ASO dimensions • Redesigned forms • Would not render as originally designed • FDM process must be customized • Cannot load naturally to ASO (FDM classic) • Must be classic administration and not EPMA Writeable ASO Sales (ASO) Plan (BSO)
- 56. ©2016 Alternate Solution #3 – Writeable ASO • Batch process to move data as necessary • MDX query • Essbase report • Retrieves at top of the dimensions are much slower than BSO • Very complex solution for data movement and calculations • Administrators need to learn ASO • Having Sales as writeable ASO plan type just did not work for this client Page 56
- 58. ©2016 Comparison of Four Solutions Page 58 Writeable ASO Sales (ASO) Plan (BSO) Hybrid Sales (Hybrid) Plan (BSO) Additional BSO Sales (BSO) Plan (BSO) SalesInp (BSO) Original Sales (BSO) Plan (BSO)
- 59. ©2016 Comparison of Four Solutions Page 59 • Original application with BSO Sales plan type • Too big and slow • Additional BSO plan type for current planning cycle • It works • Hybrid Sales plan type • Has a lot of limitations • Writeable ASO Sales plan type for input • Complex • Lots and lots of limitations • Calculations are very difficult
- 60. ©2016 Comparison of Four Solutions Page 60 • Original application with BSO Sales plan type • Too big and slow • Additional BSO plan type for current planning cycle • It works • Hybrid Sales plan type • Has a lot of limitations • Writeable ASO Sales plan type for input • Complex • Lots and lots of limitations • Calculations are very difficult Wait a minute!
- 61. ©2016 Comparison of Four Solutions Page 61 What About Alternate Solution #4?
- 62. Alternate Solution #4 Additional ASO Plan Type
- 63. ©2016 Alternate Solution #4 – Additional ASO Page 63 • 3 plan types • Plan – BSO • SalesInp – BSO (rename Sales to SalesInp) • Sales – ASO • Must be classic and not EPMA • Sales plan type • Only for aggregation – no other calculations • All historical data and current data • “Rack and Stack” Additional ASO SalesInp (BSO) Plan (BSO) Sales (ASO)
- 64. ©2016 Alternate Solution #4 – Additional ASO Page 64 • SalesInp plan type • Only current planning cycle and actual data • All calculations performed here • Classic FDM must point to SalesInp (BSO) • Periodic conversion • Foreign currency translation • Copy data to Sales after calculation • Business rules all work with SalesInp and Plan
- 65. ©2016 Alternate Solution #4 – Additional ASO • Batch process to move data from SalesInp to Sales on a schedule • Actual • Current planning cycle data • May use Map to reporting and PushData.exe • Can now use Smart Push with PBCS ! • Forms showing aggregated data cannot use suppression of blocks • Better to use FR or Smart View ad hoc • FR and Smart View must use Planning adapter due to no filters in Essbase for ASO plan type Page 65
- 66. Summary
- 67. ©2016 Summary Page 67 • Client is on 11.1.2.2 • Hybrid and ASO Plan Types would require upgrade • Map to Reporting is an option with a standalone ASO database (not an ASO plan type) • If client upgraded to 11.1.2.3 • Would allow an ASO plan type • Initial release of Hybrid with only 16 supported functions • FDM classic could still be used • If client upgraded to 11.1.2.4 • FDM classic would need to be migrated to FDMEE (including integrations for HFM) • Hybrid with 8x the supported functions • Smart Push is new for data movement (only in PBCS)
- 68. ©2016 Summary Page 68 • Many options available – weigh the pros and cons • Minimize complexity – use the KISS theory • Consider future maintenance (and by whom!) • Do not use it just because it is there!
- 69. ©2016 What Did the Client Do? Page 69
- 70. ©2016 What Did the Client Do? Page 70 Alternate Solution #1 – Additional BSO is being used • It works! • No upgrade required • Tried and true BSO solution • No changes to FDM • Administrators did not need to learn ASO or Hybrid
- 72. ©2016 Future Webinars and Contact Information Page 72 Today’s Presenter: Cindy Eichner ceichner@finitsolutions.com General Questions: Greg Barrett gbarrett@finitsolutions.com Copy of the slides: Email us for a copy of the slides or a link to the recording insights@finitsolutions.com Follow us on Twitter for updates: @Finit_Solutions Automating Data Loads with FDMEE Friday, January 22nd, Noon EST The Benefits of a Rolling Forecast Friday, January 29th, Noon EST