Oracle Hyperion DRM Basics | Exports (1 of 2)

In our last technical post we saw how to create a query. We are now going to look at creating exports so that you can extract masterdat, which is a large topic that will require a couple of posts. Technically, exports are the tool you must use to send the masterdata out to the other systems. Oracle Hyperion DRM (Data Relationship Management) exports can only write to database tables or text files, so you should consider this when designing your solution.

Let’s start by opening Oracle Hyperion DRM Data Relationship Management (DRM) and navigating to the “Exports” section of the home tab. You will see some export options and a list of saved exports. As there were with queries, exports are grouped by access level (user, standard and system). In the following screenshot, there are no exports yet.

So we can create an export by clicking on “New export”.  Oracle Hyperion DRM will immediately start by giving you the choice between different export types.












The most useful and the one we are going to look at in more detail is the Hierarchy export. This feature allows you to export nodes and property values in a table format according to a given query. Selecting the Hierarchy Export option and Oracle Hyperion DRM opens a new tab. As for queries, you will notice the “save”, “save as” and “run” buttons on the top and some configuration tabs below.

The first configuration tab is the source. In this tab, you must select the version that will be the source of the masterdata, then the hierarchies and top node. You can select as many hierarchies as you need. Remember that the export will only return masterdata from the selected hierarchies.

The second configuration tab is the style. In this tab you can tweak some of the export options like only consider leaf or limb nodes. Leave these options as they are by default. The next tab is the filter tab.

The first filter you can set is a validation. This is a feature that justifies a blog of its own and we will do this this shortly. The second filter is a property query. You can select a query you have saved or create a new query. Have a look at our post on queries if you haven’t seen it yet. If you do not include a query, the export will return all the nodes of the hierarchy. If you include a query, the export will only include the nodes that respect the query criteria. Finally, if necessary you can also use a text file to include or exclude nodes.

We’ll build on this introduction to Exports from Oracle Hyperion DRM in the next blog post. In the meantime you know where we are if we can help.


This entry was posted in Technical and tagged , , , , . Bookmark the permalink.

Comments are closed.