BSP Metada Sync Failed With 'An object with the name 100 already exists' Errors on BSP 8.0 Application
(Doc ID 2138827.1)
Last updated on JUNE 10, 2021
Applies to:
Oracle Financial Services Balance Sheet Planning - Version 8.0.0 to 8.0.1 [Release 8]Information in this document applies to any platform.
Oracle Financial Services Balance Sheet Planning (BSP)
Symptoms
On BSP 8.0.0 the metadata sync failed after upgrade from 6.1 and install and initialize BSP 8.0 application.
Currently upgrading a BSP 6.1 application to BSP 8.0 running on EPM 11.1.2.4. The interest rate curve noted was created back in 2014 and the rate type field doesn't appear to be editable when opening this particular item (in master maintenance -> interest rates) and checking to edit the item noted.
ERROR
/Plan Type/Rates/Standard Dimensions/RateElement:- LCM migration failed for the following reason - Of 61 records, 2 failed: *Record 26* failed as Error because java.lang.RuntimeException: com.hyperion.planning.DuplicateObjectException: An object with the name 100 already exists. *Record 46* failed as Error because java.lang.RuntimeException: com.hyperion.planning.DuplicateObjectException: An object with the name 400 already exists.
These curves are created upstream in OFSA and synchronized to BSP standalone, and changing or deleting these may not be feasible which means these elements will continue to flow into BSP and generate the errors unless these are addressed some other way.
The issue can be reproduced at will with the following steps:
1. Run metadata sync
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |