My Oracle Support Banner

System Ids of Migrated EPM Objects Incorrect In ICC Batch After Importing With Object Migration Causing Batch Failure on Target (Doc ID 2887315.1)

Last updated on JANUARY 12, 2024

Applies to:

Oracle Financial Services Analytical Applications Infrastructure - Version and later
Oracle Financial Services Profitability Management - Version and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Profitability Management (PFT)
Oracle Financial Services Funds Transfer Pricing (FTP)
Oracle Financial Services Asset Liability Management (ALM)
Oracle Financial Services Enterprise Performance Management (EPM)


On OFSAA, it is expected that if a new sys ID is given to a processing task on Target after object migration, the ICC batch will also be updated.

After migrating the OFSAA rules and batch to higher environment, as expected behavior of retain ids as 'Y' for the object migration, if "ID already exists in Target with different object- then the object is migrated to target environment and a new ID is generated." This causes the OFSAA batch to fail as it does not find the rule/model associated with task. Due to this it is required to manually update batch every time after migration for the tasks which get new sys ids.

The following query is used to identify objects which have updated sys ids after migration:

SELECT p.v_batch_id, p.v_task_id, p.i_parameter_order, t.short_desc FROM
<CONFIG>.batch_parameter_master P INNER JOIN FSI_M_OBJECT_DEFINITION_TL T ON p.v_parameter_value = t.object_definition_id
AND v_parameter_name = 'Process Name'
ORDER BY TO_NUMBER(REPLACE(p.v_task_id,'Task',''));

Expect that the ICC batches are also updated after migration in the case where a new sys id is assigned.

It is confirmed that after migrating the batch, AAI_OBJ_REF_INFO is updated with the new and old Allocation Sys IDs, but the BATCH_TASK_MASTER table is NOT updated.

The issue can be reproduced at will with the following steps:

1. Export allocation rules from source
2. Export batches which include allocation rules from source
3. Import allocation rules on target
==> some allocations are assigned new Sys IDs as expected due to the sys ID already being used on target
4. Import batches on target
==> confirm that AAI_OBJ_REF_INFO is populated with new and old sys ids
5. Attempt to run successfully migrated batch on target
==> batch is failed as BATCH_TASK_MASTER is NOT updated with the new sys ID




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.