Oracle Hyperion DRM Basics | Exports (2 of 2)

In last week’s post we introduced the export feature for Oracle Hyperion Data Relationship Management (DRM).  Once you have configured your source, style and filter, you can select the columns of your hierarchy exports.

 

You can define the columns by selecting properties. The export will return a line for each node that meets the filter criteria and in each line, it will write the value of each selected property. In this example, we have selected the two basic system properties Name and Description.

There are some additional options per column in the tab Column Options.

The three options are:

  1. Pivot – If a property contains a comma separated list of values, pivoting the column will repeat the line for each value of the list;
  2. Skip Defaults – If a property has a default value that should be replaced by a blank, you can use this option; and
  3. Primary Key – DRM will validate that the property has no repeated value. This should be used if you are exporting to a table that has a primary key.

The final configuration tab is called “target” and allows targets to be selected.

You can select one of three targets:

  1. Client File – Oracle Hyperion DRM will send the result to the client that triggered the export;
  2. Database Table – Oracle Hyperion DRM will write the results to a database table according to the connection, the table name and the column. You can also configure Oracle Hyperion DRM to delete the previous content of the table or partially delete the content if necessary; and
  3. Server File – Oracle Hyperion DRM will write the results into a text file in a folder on the server. You will also need to configure a connection to the folder and set the file name. The other options are the same as for the client file.

In our case, we will use the client file. We would recommend that you always run an export to a client file first to review the results before writing to databases or server folders.

The options when writing to a file are:

  • Column Headings – this option will add a line at the top of the file with the name of the columns;
  • Quoted String – puts text in columns into quotes;
  • Fixed Width – sets the width of the columns;
  • Character Encoding – sets the encoding standard for the file;
  • Replace Options – offers the possibility to replace any character with another during the export process;
  • Header – the text written in the header section will be added at the top of the text file;
  • Footer – the text written in the footer section will be added at the bottom of the text file;
  • Field Delimiter – choose the character that Oracle Hyperion DRM will insert to separate columns; and
  • Record Delimiter – choose the character that Oracle Hyperion DRM will insert to separate records. The default is the line terminator CRLF which means that Oracle Hyperion DRM will start a new line for each record.

Now that we have configured everything, we can run the export. As we created a client file export, Internet Explorer will ask you where you want to save the file that was generated by the Export.

Save it and open with Textpad or Excel to have a look at the results. Exports do not modify data in Oracle Hyperion DRM and by exporting to your client file, you are not affecting any system, so you can play with the export types and options without any wider consequences!

In our next technical post we will talk about importing data into Oracle Hyperion DRM. If you would like to explore any of these points in more detail then do reach out.

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

Comments are closed.