How to Import Hierarchy into DRM through flat file?
In this post, we’ll learn how to build and use DRM Imports as we load each dimension/hierarchy into a separate version.
DRM underpins essential and exchange chains of command, and you can make the same number of as you need. DRM additionally bolsters numerous part hub mappings crosswise over various pecking orders — which means you can relate data between various chain of command structures. Dimensions, domains, and hierarchies are terms often used interchangeably. When you hear someone say “dimension” or “domain,” it might imply multiple hierarchies.
In DRM, the term “hierarchy” has a very specific meaning — a hierarchy is defined by its “top node” and the top node might also have a parent in an alternate hierarchy.
Types of hierarchies include:
The following is taken from Oracle’s online DRM User Guide Documentation…
Utilizing Data Relationship Management, you can import information removed from outside frameworks, social database tables and sees, or physically made by clients utilizing a multi-area, content document group. Imports are constantly performed on new, void variants made as a major aspect of the import procedure. This methodology enables you to check that information was imported effectively and resolve any issues previously sparing the information to the database or converging with information in different variants. After you check the information, you can utilize the blender to join imported information with information starting from different sources.
The content for our Import will be a series of text files created by extracting and transforming the metadata from Sample.Basic. Each time you run an Import, a new version is created.
An Import can have up to 5 sections:
Version – This section can be used to populate Version-level properties for the version being created by your Import. Only the Version Name property is required.
Hierarchy – This section creates the hierarchies (and populates Hierarchy-level properties) that will exist in your new version. The Hierarchy Name & Top Node properties are required. In Essbase-speak, the Top Node is similar to the dimension root in an outline, it is the first parent from which all limbs and leaves will be created.
Node – This section creates nodes in a new version, and can populate Global-level node properties only. The only required property is Node Name.
Relationship – This section creates nodes and structures your hierarchy (based on Parent-Child relationships). Both global and local-level node properties can be populated. We’ll be using this section to create our nodes in the correct structure and populate all properties in a single pass. There are 2 required properties, Parent Node Name & Node Name.
Hierarchy Node – This section can assign local-level node property values specific to a hierarchy. For that reason, if using this section, you must also have a Hierarchy section in your file. The required properties are Hierarchy Name & Node Name.
The Right side of this screen Instruct DRM how to deal with copy hubs in your import document. At the point when a copy hub is experienced, DRM will attach an addition to the hub name (for instance, product!100-20:Shared-001). Notwithstanding the post fix being included, DRM will likewise empower the System hub property Shared Node Flag.
Proceed onward to the Columns tab, this is the place we'll reveal to DRM what our import documents resemble. For each segment, we have to disclose to DRM which properties we will populate, and according to the pattern in which they show up.
For the Version section, I’ve left the default properties, as this will match our import file.
Stay on the Columns tab, but switch the section to Hierarchy.
I’ve added the columns we have in the import file, and confirmed they are in the correct order.
Now switch to the Relation section for the last step on this tab.
Again I’ve added the properties from the import file and confirmed they are in the correct order.
Move to the Filters tab.
Commonly you're going to need these alternatives empowered when running an import, yet you have to thoroughly consider it. The alternatives on the left side reveal to DRM how to deal with void property fields in the import record. These are altogether empowered as a matter of course.
The choices on the right side train DRM how to deal with property estimations in the import document that coordinate either the default property estimation, acquired esteem, or determined esteem separately. These are critical in light of the fact that they will enable you to keep your database as little as could reasonably be expected. Utilizing default esteems and business rationale is incredible on the grounds that it can rearrange application support and lessen the capacity impression of your database.
Lastly, move over to the Target tab.
For the Version Name, I have just entered File. It really doesn’t matter what you put here since the version name will be coming from the import file, but you won’t be able to save your Import without putting something in this field.
I have enabled the option to Save Version to Repository.
Save the Import, give it a name and a description if you like. For the object access group I have chosen Standard.
-> Once your Import is saved,
-> Go back to the Source tab,
-> Click Browse to select one of your import files,
-> Click run to kick off the import process.
You can see the Import result at the base of the screen. On the off chance that you arranged anything erroneously in your Import, DRM will tell you. The blunder and cautioning messages you get are normally straightforward and resolve.
One of the more common errors you may keep running into is if an area in your import document has an alternate number of fields that what you have in your import.
Without leaving this screen, click Browse once more, select the following import record, and after that click Run once more. Run every one of your import documents.
Click on the Home tab, and then navigate to the Browse section.
Here you can see all of the versions you just created with your Import. Each of these versions contains only a single hierarchy, so now we need to merge all of these hierarchies into a single version, which we’ll accomplish using a Blender.
First, we need to create an empty Version, which we will blend all of the hierarchies into.
Click on the new version button.
Enter a name and a description, and then Click OK.
We’ve chosen “Sample_Basic_” and today’s date.
Need to discover progressively about utilizing hands-on and live understanding, Endeavor to Remember or in case you discovered this post vital, Make beyond a shadow of a doubt, you can look at our Web based Learning of Hyperion DRM course for more tips, traps and procedures for successfully to reveal emerge bits of data from your information.