Oracle Hyperion DRM Basics | Imports (1 of 2)

So now you know how to extract or export data from Oracle Hyperion DRM (Data Relationship Management) a logical next step is to understand how we get data into Oracle Hyperion DRM. Imports and scripts (or automators) are the two main tools available to get large amounts of data into Oracle Hyperion DRM. Imports are the best method if you need to import complete hierarchies with properties. Scripts are better to load specific property values, or changes, to a hierarchy that already exists. We will focus on imports in this post and then we will look at scripts in a future post.

To build your import you must:

  1. Set the flat file in the correct format;
  2. Set up the import;
  3. Execute the import;
  4. Check the log; and
  5. Save the resulting version.

Getting the flat file in the correct format is quite simple. You can use whichever file editing tool you prefer, such as notepad++ or notepad. The first thing you must choose is your separating character. The typical choices are the comma or semi-colon. You can also choose tab, or any special character. Oracle Hyperion DRM is quite flexible so you should focus on choosing one that is never used in the masterdata you are importing. Second, you must start building your sections. Your flat file can be divided into up to 5 sections. Sections are delimited by headers.

The five sections that can be included in the import are:

  1. Version – This section should contain a line with the version name and any property value to be associated to the version (default header: [version]);
  2. Hierarchy – This section should contain a line for each hierarchy to be created. The required information is at least the name and the hierarchy top node (default header: [hier]);
  3. Nodes – This section allows you to import a list of nodes and values for global properties (default header: [node]);
  4. Relation – This section should contain the relation between nodes, in a parent child format and any additional property values. Any node in the child column that does not exist will be created (default header: [relation]); and
  5. Hierarchy Nodes – This section should contain nodes to be imported and associated to a specific hierarchy. This will allow you to import nodes and the value for local properties (default header: [hiernode]).

A simple import file can contain only two sections: the hierarchies and the relations. So here is an example of a very simple import file:


My hierarchy;TopNode;This is a new hierarchy


TopNode;A;Node A

TopNode;B;Node B

B;B1;Node B1

A;A2;Node A2

A;A1;Node A1

This import file will create a new version (the name of the version will be required during the import as it is not specified in the file) with one hierarchy called “My hierarchy”.

In our next technical blog we will continue to explore how to import and specifically how to import the file we have just created.

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

Comments are closed.