You want to define a tree or hierarchy for use in reports and allocations. What three aspects should you remember when creating the tree?

Question

Options

• AYou need to flatten the rows to be able to use drilldown in Smart View and you
• BYou must flatten the columns and publish the tree to view the hierarchy in Essbase cubes.
• CThe tree should have at least two tree versions to reduce report and allocation maintenance.
• DYou only need to flatten the columns if you plan to use the hierarchy in Oracle Transactional
• EItis fine to have thesame child value roll up to twoor more different parent values.

• A
  84% (41)
• B
  10% (5)
• E
  6% (3)

Explanation

If using the tree for reporting and allocations, you need to flatten the rows to be able to use drilldown in Smartview and you must publish the tree to view the hierarchy in the Essbase cubes. If using the tree for other purposes outside of reporting and allocations, then you must flatten the rows, but you do not need to publish the hierarchy. If using the tree for OTBI, you must flatten the columns. Hierarchies used for reporting and analysis and allocations cannot have the same child value rolling up to 2 different parents. If you do this, the Essbase cube will not be created when you try to Publish the hierarchy. Always create at least two hierarchy versions before creating any financial reports or allocations. This will force the fully qualified member name path to be generated and refers to the full tree name, tree versions, and minimize the report maintenance, if you must add another version in

No community discussion yet for this question.