Oracle Financials Cloud – General Ledger Hierarchies

Oracle Financials Cloud – General Ledger Hierarchies 

If your organization uses Hierarchy Structure (specially used by the banking firms) for chart of accounts mapping then most common issue often faced by the business/consultants that child values will start getting populated as parent ones in your OTBI/BIP reports which eventually creates chaos and improper analysis of data.

 

This issue occurs because hierarchies are defined after uploading the journals through FBDI or after entering the journals into your fusion application resulting in posted balances of child values will be considered as parent level journal balances and it causes reconciliation issues along with hierarchy data misinterpretation.

 

Below basic points must be taken care while working with Hierarches.

1)     You should create duplicate of hierarchies in order to reduce maintenance and while writing code for your report mention the condition to fetch only current hierarchies because it is always recommended that one must name active hierarchies as XYZ - CURRENT and copied ones as XYZ - BASELINE.

2)     Copied hierarchies must be audited, flattened and finally published

3)     An organization uses hierarchies in reports, cross validation rules, revaluations, segment value security, allocations, and Chart of Accounts Mapping.

4)     You need to create two different trees for different purposes; one for reporting and allocation and another for revaluations, segment value security, and chart of accounts mapping.

5)     For reporting purpose you need to flatten the COLUMNS and use the following table gl_seg_val_hier_cf,

for any other purpose you need to flatten rows.

6)     You must define hierarchies before importing and entering the journals

 

But in case hierarchies are defined after importing the journals then in order to avoid such entities in your report you can use the below logic.

In fnd_flex_values_vl table there is a column name summary_flag, it must be hardcoded to ‘N’ then only the correct entities will be populated in the BIP report.

And if you want to extend this query in order to fetch hierarchy data for all segments mapped in COA, you can refer the query given in below screenshot.

 

NOTE: If you have observed then below condition is given in the query for avoiding the treatment of child entities as parent one.


Comments

Popular posts from this blog

While creating expense report facing the following error java.lang.IllegalArgumentException : peerExceptioms list should only contain OAException elements.

IExpense error : The specified approver is not a user of the application.