Hierarchy Used in Allocation or Lookup Table Not Found After Object Migration to New Environment
Last updated on FEBRUARY 03, 2016
Applies to:Oracle Financial Services Analytical Applications Infrastructure - Version 7.3.1 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
In Oracle Financial Services Analytical Applications (OFSAA) 7.3, when migrating objects from a source environment to a target environment, Hierarchy Filters attached to Allocations and Lookup Table Drivers are not migrated correctly by the Object Migration Utility. For Allocations that use a Hierarchy Filter in the Source or Driver screens, the Hierarchy Filter is not attached to the Allocation after migration. The following message appears in the Allocation screen:
: Hierarchy Filter: Not Found
A similar error appears if the Allocation references a node on a Hierarchy.
For Lookup Table Drivers that use the Hierarchy Match, the Hierarchy is no longer attached to the Lookup Table Driver in the target environment.
This issue causes Allocations to produce incorrect results in the target environment because the Hierarchy Filter no longer works.
Steps to Reproduce:
- Log into OFSAA Infrastructure
- Select the target Infodom
- Go to Administration > Utilities > Object Migration
- Create a new Object Migration rule
- Select an Allocation that uses a Hierarchy Filter from the Source
- Run the migration
The migration completes successfully but when you review the Allocation on the target, the Hierarchy Filter is missing from the Allocation.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms