The most basic and vital use of FDMEE is its mapping functionality. Mapping is so integral to the application that without it users have no way of integrating or validating their data into HFM. This blog will serve as an introduction to a three-part series that covers what to consider when developing your mapping process.
The title above may have you wondering what business software and jungles can possible have in common. In a strict sense, the answer is very little, but a close look at the ever-shifting IT landscape and the analogy pretty well explains itself. I’ve been working with IT infrastructure, and in particular ‘Hyperion’ infrastructure, for the past 20 years. In all of that time, I really cannot think of the IT world being less settled than it is today. We’ve had changes in the Hyperion world over the years. We’ve moved beyond simple consolidation software (those Enterprise days) to analytics (Essbase and Arbor) to multi-server and Java based technology (I’m looking at you Hyperion System 9) and then into virtualization and hosting. But all of those states of sea-change were gradual, and in many respects the EPM world was behind-the-times. What we are seeing now is a game of catch-up in EPM world, and in all of the business facing systems that feed EPM or that EPM feeds.
Over the last five years I have spent the bulk of my career focused on big data and big data technologies. I have advised many of the Fortune 100 companies in regards to their data strategies. Early collaborative discussions with the client help ensure that our strategy is aligned not only with the current big data trends but also aligned with the future of big data. The zigs and zags of big data technology have required not only an agile team but an experienced team. The right technologies, with the right plan designed by the right people can place an organization like yours at the top of a very competitive landscape.
In order to create a report for Hyperion Financial Management, Planning or EssBase you can use Smart View or Financial Reporting. Both products query the data source but often the question remains what is the difference between the two. Which should I use and when?
Is your organization struggling to design effective Data Relationship Governance (DRG) Workflows? Is your data governance process documented? Do you have a clear understanding of how master data is currently created and updated in your downstream applications? Answering these questions is the key to designing effective Data Relationship Governance (DRG) workflows.
The goal of Part 3 will be to demonstrate using the Oracle Database Job Scheduler to control execution of the trigger action script or workflow output.
The goal of Part 2 will be to demonstrate basic configuration and operation of the DRM trigger-event loop.
DRM events - for example: add node, change property - are not exposed to web and batch client programming interfaces; denying the user the opportunity to build automated responses. An event driven implementation would provide many ways to enhance DRM actions with complementary actions. Some examples:
End-to-End Data Integration Design is not just the design and implementation of ETL tools, but also the integration of systems with people. It takes a holistic view of an organization’s people, processes and systems to ensure that all reporting applications are built on a rock-solid data foundation.