Skip to Content

The hierarchy flattening transform can analyze a parent-child relationship and provide a description of the hierarchy in a flattened format (vertically flattened/ horizontally flattened). Each row in the output will contain 1 parent-child relationship.

For example consider the following reporting structure in an organization:

/wp-content/uploads/2012/08/pic1_130146.jpg

The input data is in a table EMP_MGR. The data is corresponding to the hierarchy structure in the above diagram.The below figure shows the data in the table EMP_MGR.

/wp-content/uploads/2012/08/pic2_130147.jpg

This data is taken as the input to the Hierarchy Flattening Transform. In this example we will see the horizontal flattening by Hierarchy Flattening Transform. This will mean that each root to node relationship will be “flattened” and presented as a row, eg: MGR_1 : EMP_2, MGR_1 : MGR_2, MGR_1 : MGR_2:EMP_4 etc. The figure below shows the Dataflow containing the hierarchy transform.

/wp-content/uploads/2012/08/pic3_130157.jpg

We will configure the Hierarchy Flattening Transform such that the MGR_ID as the parent column and EMP_ID as the Child column. Since this example deals with only 2 columns (representing Parent and Child) we will not be populating the Parent attribute List and the Child Attribute List. If we had additional columns in the source table , that are associated with the Parent column, we could have added them to the Parent attribute List. Similarly , if we had additional columns in the source table , that are associated with the Child column, we could have added them to the Child attribute List. Configure the Input schema columns only. After that , if you click on “Validate” button, the right hand columns are created automatically. The number of columns (…upto LEVEL 3 in this snapshot) depend on the maximum depth that is selected.The figure below shows the configuration of the hierarchy flattening transform.

/wp-content/uploads/2012/08/pic4_130158.jpg

Maximum depth is taken as 3 in the initial run.  The root node (MGR_1) has zero level depth, MGR_2 has depth 1 , EMP_4 has depth 2 and so on. So having a maximum depth =3 will mean that we cannot fully represent EMP_6 which has a depth =4. This is illustrated when we run the Job and look at the output.

/wp-content/uploads/2012/08/pic5_130159.jpg

We see that the last row is incomplete.

If we reset Maximum Depth= 4 and run the job again then we get the output as shown below . Here the last row shows the root to node relationship completely for EMP_6.

/wp-content/uploads/2012/08/pic6_130160.jpg

Note :

If the input data is erroneous, that is there exists cyclic relationship, then a run-time error is produced.

To report this post you need to login first.

5 Comments

You must be Logged on to comment or reply to a post.

  1. sapkrisboedge mac

    Thanks for posting to the Hierarchy Flattering transformation. I have One more question priya. Can you please help me..

    how to load the  Oracle exception errors  automatically to the target table(Oracle)?

    My Source is Oracle ,

    My target is Oracle.  please let me know  It is very Urgent…

    (0) 
  2. Prabhakar Teegavarapu

    Thanks for the blog Debapriya. that was very usefull.

    I am trying to find a solution incase of cyclic hierarchy issue.

    based on your example. If Manager1 reports back EMP6 and I have split such data and report in a different file

    Can you suggest something on this?

    Thanks

    Prabhkar

    (0) 

Leave a Reply