DRM

This is one of the tools available in the Oracle Hyperion hub. Prior to the need of this tool we shall discuss the drawbacks or bottleneck situations in the current system.

Is there any way to track the changes done in the outline by the developers in Hyperion Essbase?

If one hierarchy is being shared across in 3 different Essbase applications and if new member has to add to that hierarchy means, do I need to build the same member in different hierarchies separately?

with my limited knowledge if i have to answer to the above questions, I have to pull up the screen for DRM show, Here

• You are maintaining the metadata in the form of outline but in two dimensional database ( since we are not storing the data)
• The Aggregation symbols, Aliases, Storage Properties etc are stored in the place holders called properties.
• You can write queries to get the required metadata output from the hierarchy.
• You can track the changes very precisely by user, by property and by data and many more.
• You can export the metadata to target tables directly or you can FTP the file to the target server directly.
• Supports three types of metadata build Automators, Imports and Blendars.
• You can specify the access very granular.
• You can do compassion between two metadata files for the similarities and differences.
• You can write validations and verification's to maintain the consistency in the metadata

and lot many......