Maintenance Hierarchies
As your organization changes or there are updates to your chart of accounts values, you can make updates to your hierarchy versions.
Changes must be in the two hierarchy versions to minimize errors related to member name paths in financial reports, allocation rules, or Smart View queries. Both hierarchy versions must be published to the balances cube.
To keep an audit history, copy the hierarchy version and use the copy as the version for audit history. After you copy the hierarchy version, modify that same version to use as the latest version. You don't have to change reports.
Hierarchy Versions Configuration
Perform the following steps before updating the current hierarchy version:
-
Copy the current hierarchy version to create cost center 2018 to keep an audit history for year 2018.
-
Update the effective date for the Current hierarchy version to the current period. Set the effective dates for the copied hierarchy version to what the past dates were.
-
Make all of your current hierarchy changes to the Current hierarchy version.
-
Set the status to Active again.
-
Delete the Baseline hierarchy version in the Manage Account Hierarchies page. You don't unpublish the hierarchy from the cube, as long as you follow the naming conventions discussed in the following steps.
-
Copy the Current hierarchy version and name it Baseline. You must name it the same exact name because Baseline still exists in the cube. The procedures overwrite the hierarchy version named Baseline in the cube.
-
Use effective dates that don't overlap and that are before periods used by previously active hierarchy versions.
-
Set the status for the Baseline hierarchy version to Active.
-
Publish both hierarchy versions, Current and Baseline, to their respective cube.
-
Publish the cost center 2018 to the cube if the version is still needed for financial reporting, Smart View queries, or allocation rules.
-
Review the published results using Smart View.
You have the following three versions:
-
The new copied version: This version is used to track the history of the old version, for example, cost center 2018 and has been end dated.
-
Current version: This version has been modified to reflect the new hierarchy and is now active.
-
Baseline version: This version should continue to be the duplicate of the Current version. Rather than modifying this manually, delete the old baseline version and create another copy of the now updated active Current version. These steps should be followed each time when there are hierarchy changes that must be published.