PCM_OP_ACT_GET_CANDIDATE_RUMS Not Returning The Proper Output RUM QUANTITY
(Doc ID 2548675.1)
Last updated on OCTOBER 22, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, Rating
While using the custom event configured with custom rum quantity expression (PIN_FLD_INHERITED_INFO.PIN_FLD_QUANTITY), though the pin_rum file is properly configured and custom event is added in the fag end of the file, the DB has its own row_num for the records while listing it. Since the order is different while accessing the /config/rum object in cache, the order of processing is not proper.
(e.g) Custom event is "/event/activity/PayrollEE", and loaded as the REC_ID 197 and the default /event is in REC_ID "0". Due to the DB order, it is cached in different order and the same being used for the processing as well. If the custom event is ahead of the "/event" in the cache, then the CUSTOM expression PIN_FLD_INHERITED_INFO.PIN_FLD_QUANTITY is getting overridden by the default value as "1".
Actual Behavior: Instead of the value been picked from the PIN_FLD_INHERITED_INFO.QUANTITY of the custom event "/event/activity/PayrollEE", it is returning the QUANTITY as "1" which is of "/event" config.
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