Oracle DRM Blog

Good news, I have something really cool for you Essbase lovers in building your existing hierarchy into Oracle DRM, almost seamlessly. Many of us look to Oracle DRM to provide a facility to load our parent-child text file and import a hierarchy. Well it just doesn’t work that way. Oracle DRM has it’s own flat file format that’s not very common…I mean HFM or BPMA maybe the closest but still if you are working on a project and you have a simple CSV file, you’re out of luck. Be prepare for hours of programming or manual tweaking the file before it can be imported into Oracle DRM. Well now, here is a cool solution.

I have decided to help some of us to do it the easy way. I have decided to create a series of tools. I am calling it the DoReMe Tools. Ah it rhymes with D.R.M. doesn’t it? Click here to take a look…

Now the first tool is the Parent-Child Import Automator. What you do is submit a Parent-Child CSV file and you will get back an automator script that can readily be loaded into Oracle DRM. It’s that easy.

Why is this a big deal?

• A parent-child CSV file should be easy to produce by most systems;
• To make it a hierarchy, we do the hard work to re-arrange the order so that you won’t be building a child without it’s parent being produced first. This is not easy to do.
• We create the Automator script that will build the hierarchy, the parent, and the children. When you build a hierarchy with automator, you know you have audit trail for SOX purposes. When you use the native import function, you don’t have any audit trail.

To access the tool, again please click here. Let’s take a look at the input fields:

• Version Name – enter the version name you will be building the hierarchy
• Hierarchy Name – enter the name you wish to call the new hierarchy
• Node Suffix – enter a suffix for the node members (optional)
• Upload File – click the Browse button and select a local file to upload. This file will need to be comma-separated CSV file.
• Node – column where the node member is located
• Node Alias – column where the node description is located
• Node Parent – column where the parent node is located