You want to define a tree or hierarchy for use in reports and allocations.
What three aspects should you remember when creating the tree?
A.
The tree should have at least two tree versions to reduce report and allocation maintenance.
B.
You need to flatten the rows to be able to use drilldown in Smart View and you must publish the tree to view
the hierarchy in Essbase cubes.
C.
You must flatten the columns and publish the tree to view the hierarchy in Essbase cubes.
D.
You only need to flatten the columns if you plan to use the hierarchy in Oracle Transactional Business
Intelligence (OTBI).
E.
It is fine to have the same child value roll up to two or more different parent values.
A C E
A C E
A, E
https://www.linkedin.com/pulse/account-hierarchies-fusion-gl-suresh-mishra
D
https://docs.oracle.com/cloud/latest/common/FAHCA/FAHCA2263863.htm
Sorry, the correct answer seems to be A D E and not A, C, E
A, E
https://www.linkedin.com/pulse/account-hierarchies-fusion-gl-suresh-mishra
D
https://docs.oracle.com/cloud/latest/common/FAHCA/FAHCA2263863.htm