If you were called in for an interview without Hyperion on your resume, it is probably just an employer wish and not a requirement. Maybe just ask thoughtful questions to see what hyperion applications they are using, how they are using them, what their biggest challenges are, if the chosen candidate will be expected to develop reports, webforms or other apps or if you would just be an end user running reports created by others and ad hoc queries?
I am really only familiar With EPM side. If they are truly needing someone with in depth Hyperion knowledge, then it's probably not the right fit. You don't want to oversell yourself and end up being let go either. Just be enthusiast about learning and relate it to your previous companies software and overall skill set.
Good luck!! Let us know how it goes. If you can master the tool, you'll definitely raise your value as an employee. That being said, your use of hyperion will vary depending on what position you're applying for. The same would apply for Financial reporting and Consolidations. Now if you're part of a regional accounting team, then your use of hyperion will generally be more limited. You're usually just pulling a few accounts for your section and your region.
I think it would be difficult to teach yourself hyperion from just a manual or tutorial. It's more important to learn about the structure of the organization and chart of accounts before delving in and just creating reports and pulling balances from the various cubes that hyperion offers.
If you're here, you've got questions — and we've got answers. Book your consultation to ask us about any range of topics, including:. Filling out this table will help you get started: Planning, Budgeting, and Forecasting Processes As the bridge between finance and IT, you must understand the business processes as well as the system. You should include the differences in the level of detail and types of methods used, such as rolling forecasts.
Describe the budget approval processes. What are the key business drivers considered in budget preparation? Documenting a Single Planning Application If you have a single Hyperion application, you are allowed three custom plan types and two modules: Workforce and Capex. Documenting Multiple Planning Applications However, there are many reasons for having multiple applications, such as use between separate operating units with disparate planning processes; the need for distinct processing windows; or running out of plan types.
Typical customization includes: Updating smart list attributes for use with an organization Modification to forms or rules to allow for budget and forecast processes that converge Updating metadata: employees, asset category, etc.
Need to offload some of your Hyperion Planning tasks? Register for the webinar Discoverer for example is just a query tool and you can learn it end-to-end without needing to know anything about how it's used. Oracle BI Enterprise Edition is the same, whereas the BI Applications typically require you to know as much about the source system it works with as about the tool itself. The Hyperion toolset is a bit like this but much more weighted towards the business side; Essbase and tools like Essbase Studio, WebAnalysis and SmartView can be learnt as just a bit of technology, but most Hyperion developers at one time or another have had a background in accountancy, planning or other financial functions as you'll need this to properly understand the role of applications such as Hyperion Financial Management, Hyperion Strategic Management, Hyperion Profitability and Cost Management and Hyperion Performance Scorecard.
These are obviously not tools you'd pick up on a wet Sunday afternoon and have a play around with for the fun of it. Hyperion Planning has always interested me though, as it's built on top of Essbase and at one time or another, most of us have made financial plans. They might be to work out if we can afford to buy a new car, or pay off a credit card, or we might have been in charge of a department and asked to plan out staff numbers and payroll for the year.
As such, its a process that most of us can identify with, and if like me you're a director of a company it's something you could actually see yourself using. So what is Hyperion Planning then, what's it used for and what's the technology underneath it?
More importantly, is it something you could set up yourself as a bit of home learning and how much does it build on your Essbase and ETL experience? Over this and two other postings, I'm going to be looking at Hyperion Planning firstly, by explaining what it is; secondly, by taking you through a demo that you can set up yourselves, and thirdly, by going through a planning system I've created myself that shows how the development process works. But first of all though, what is Hyperion Planning?
Hyperion Planning is an application that sits on top of the Essbase OLAP server and is used by organizations to perform planning and budgeting.
Using the tool, you work with standard dimensions such as period, year, scenario, entity and accounts to which you can add other custom dimensions such as product and geography, with an Essbase cube being built using these into which you add budgeting and planning data.
0コメント