Last updated on JANUARY 20, 2017
Applies to:Oracle Financial Services Analytical Applications Infrastructure - Version 7.3.1 to 22.214.171.124.0 [Release 7]
Oracle Financial Services Funds Transfer Pricing - Version 6.0 and later
Oracle Financial Services Profitability Management - Version 6.0 and later
Oracle Financial Services Asset Liability Management - Version 6.0 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
In Oracle Financial Services Analytical Applications (OFSAA) Infrastructure 7.3.1 or higher, you cannot migrate Batches that contain PFT Allocations, FTP Processes, SQL Rules, etc. from a source environment to a production environment using Metadata Archive / Restore. When the Batch is restored in the target environment, the <config>.BATCH_PARAMETER_MASTER table contains the wrong System ID value for the "Process Name". As a result, the Batch no longer references the correct Allocation, FTP Process, SQL Rule, etc.
You used Object Migration to move Allocations, FTP Processes, SQL Rules, etc. from a source environment to the production environment. When the EPM rule is migrated, the process gives it a new System ID in the target environment. However, when the Batch is migrated using Metadata Archive / Restore, it still references the old System ID from the Source environment. It no longer references the correct System ID for the EPM Rule. As a result, the Batch will either fail in the target environment or execute the wrong rule.
Steps to Reproduce:
1. Create an Allocation in the source environment
2. Create a Batch that executes the Allocation
3. Go to Administration > Utilities > Object Migration
4. Create an Object Migration rule to migrate the Allocation to a new environment/infodom
Note that the Allocation is given a new System ID in FSI_M_OBJECT_DEFINITION_B when the migration complete.
5. Go to Unified Metadata Manager > Metadata Restore/Archive
6. Make an Archive of the Batch with the SQL Rule
7. Restore the Batch in the new environment
The Batch references the old System ID of the SQL Rule from the source environment and not the new System ID of the SQL Rule in the target environment.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms