Business Hierarchy Refresh Still Running When Mapper Refresh is Launched
(Doc ID 2621217.1)
Last updated on DECEMBER 18, 2019
Applies to:Oracle Financial Services Funds Transfer Pricing - Version 6.1.1 and later
Oracle Financial Services Asset Liability Management - Version 6.1.1 and later
Oracle Financial Services Analytical Applications Infrastructure - Version 22.214.171.124.0 and later
Oracle Financial Services Profitability Management - Version 6.1.1 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
In OFSAA 7.3.x, when running RUNIT.sh, the UMM Hierarchy re-save utility, in a Batch, the Task is completing before the Hierarchy re-save is complete.
As a result, the next Task, the Mapper Refresh (MapPushDown.sh), is launched too soon and the Mapper Refresh fails.
Below is an example of the parameters used for the UMM Hierarchy Re-save:
Executable = ./RUNIT.sh,<infodom>, <user>, AMHM_123456
Wait = Y
Batch Parameter = Y
You expect the Hierarchy re-save to complete before the Mapper refresh is launched.
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