Considerations for Initial Publishing of Account Hierarchies

If you start with one version of a hierarchy and you add multiple versions of the hierarchy later, then the fully qualified member name changes.

Therefore it is recommended that you 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 future.

Recommendations

To avoid maintenance efforts when more hierarchies are published, it is recommended for you to follow these recommendations:

• Create two tree versions of the same tree before creating any financial reports or allocations to force the fully qualified name to be generated.

• Keep the two tree versions in sync always to guarantee fully qualified names are used in financial reports and allocations.

• Use the same tree version names over time to avoid breaking your reports or configurations.

• Use different hierarchies if you have requirements to roll the same child to more than one parent.

The initial configuration steps must be completed before the definition of any financial reports, allocation rules, or Smart View queries