Create an Accounting Hierarchy

Background
Your company uses hierarchies in reports, cross validation rules revaluations, segment value security,
allocations, and COA Mapping.

Note: Even though you could theoretically use the same tree for all of the above processes, you would
typically create at least two different trees: One for reporting and allocations and another for cross-
validation rules, segment value security, revaluations and COA Mappings. You need to carefully consider
the usage for your trees. 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.

Note about Segment Value Security: It is very common for companies to use segment value security in
reports to prevent certain users from being able to view balances for certain cost centers, accounts, etc. If
your customer has this requirement, then you should use your reporting hierarchy when defining segment
value security rules. If you do not, then segment value security rules will only be applied to transactions.

Note

Background
Your company uses hierarchies in reports, cross validation rules revaluations, segment value security,
allocations, and COA Mapping.

Note: Even though you could theoretically use the same tree for all of the above processes, you would
typically create at least two different trees: One for reporting and allocations and another for cross-
validation rules, segment value security, revaluations and COA Mappings. You need to carefully consider
the usage for your trees. 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.

Note about Segment Value Security: It is very common for companies to use segment value security in
reports to prevent certain users from being able to view balances for certain cost centers, accounts, etc. If
your customer has this requirement, then you should use your reporting hierarchy when defining segment
value security rules. If you do not, then segment value security rules will only be applied to transactions.

Note

Background
Your company uses hierarchies in reports, cross validation rules revaluations, segment value security,
allocations, and COA Mapping.

Note: Even though you could theoretically use the same tree for all of the above processes, you would
typically create at least two different trees: One for reporting and allocations and another for cross-
validation rules, segment value security, revaluations and COA Mappings. You need to carefully consider
the usage for your trees. 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.

Note about Segment Value Security: It is very common for companies to use segment value security in
reports to prevent certain users from being able to view balances for certain cost centers, accounts, etc. If
your customer has this requirement, then you should use your reporting hierarchy when defining segment
value security rules. If you do not, then segment value security rules will only be applied to transactions.
Note

Background
Your company uses hierarchies in reports, cross validation rules revaluations, segment value security,
allocations, and COA Mapping.

Note: Even though you could theoretically use the same tree for all of the above processes, you would
typically create at least two different trees: One for reporting and allocations and another for cross-
validation rules, segment value security, revaluations and COA Mappings. You need to carefully consider
the usage for your trees. 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.

Note about Segment Value Security: It is very common for companies to use segment value security in
reports to prevent certain users from being able to view balances for certain cost centers, accounts, etc. If
your customer has this requirement, then you should use your reporting hierarchy when defining segment
value security rules. If you do not, then segment value security rules will only be applied to transactions.

Note

Background
Your company uses hierarchies in reports, cross validation rules revaluations, segment value security,
allocations, and COA Mapping.

Note: Even though you could theoretically use the same tree for all of the above processes, you would
typically create at least two different trees: One for reporting and allocations and another for cross-
validation rules, segment value security, revaluations and COA Mappings. You need to carefully consider
the usage for your trees. 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.

Note about Segment Value Security: It is very common for companies to use segment value security in
reports to prevent certain users from being able to view balances for certain cost centers, accounts, etc. If
your customer has this requirement, then you should use your reporting hierarchy when defining segment
value security rules. If you do not, then segment value security rules will only be applied to transactions.

Note

Background
Your company uses hierarchies in reports, cross validation rules revaluations, segment value security,
allocations, and COA Mapping.

Note: Even though you could theoretically use the same tree for all of the above processes, you would
typically create at least two different trees: One for reporting and allocations and another for cross-
validation rules, segment value security, revaluations and COA Mappings. You need to carefully consider
the usage for your trees. 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.

Note about Segment Value Security: It is very common for companies to use segment value security in
reports to prevent certain users from being able to view balances for certain cost centers, accounts, etc. If
your customer has this requirement, then you should use your reporting hierarchy when defining segment
value security rules. If you do not, then segment value security rules will only be applied to transactions.

Note