Designing Account Hierarchies in Oracle Fusion Application- Part 2

In this training article we will learn how to create account hierarchies step by step. We would also discuss the prerequisite setups required to achieve the task.

Prerequisite Setup for designing account hierarchies:

Before creating account hierarchies we must configure the chart of account and value set values. While creating value set values for parent and child we must adhere to the following requirements. For child values we need to select Summary as No and allow posting and allow budgeting as Yes

In case of parent values we need to select Summary as Yes and allow posting and allow budgeting as No - 

Similarly we can create values for parent and child Company-

Prerequisite Setup for designing account hierarchies:

In order to create a new hierarchy we will configure the task Manage Account Hierarchies-

Let us create hierarchy of Company-

Input the value set of the company created in bind value set code field for both parent and details values and click on Save before clicking on Next. If the data is not saved before moving ahead, the system will throw an error message.

Click on Next

Click on Submit button

Now select the hierarchy created (in this case its ANMU_Company as highlighted) and click on create Tree Version from Actions down arro

Input the name and details of the version and click on next

We can see that a blank version is created. Click on Submit. 

We can see that the Version 1 has been created successfully.

Now click on Version 1 

Click on Next button

Then Submit. We will get the below screen

Select Data Source as Accounting Flexfield Hierarchy Parent value. We will get the parent values which we can select and go to next task

We can see that the parent value is created. Now to attach the child value, select one of the parent value and click on Add icon 

This time select Data Source as Accounting Flexfield Hierarchy detail values. All the child values will pop up. Select the required value and click on OK 

Similarly we can repeat the above task for APAC Regional Office 

We can see that the hierarchies are created. Click on Submit

We get the hierarchy for which the status is draft. This indicates that version 1 is still under progress. If we publish this hierarchy it will not publish in Essbase until the status is active. So once we are done with all the changes we will change the status to active

Click on Online audit

We can see that the hierarchy created is successful. 

We can see that the status became active. Now if publish this hierarchy after ledger creation, it will automatically get published in Essbase cube and we can use this hierarchy for reporting purpose.

Anjan Mukerji

Add comment