Last updated on JUNE 19, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.5.0]
Information in this document applies to any platform.
***Checked for Relevance on 1st June 2016***
On Oracle Communications Billing and Revenue Management(BRM), 184.108.40.206.0 version, 'PCM_OP_SUBSCRIPTION_SET_BUNDLE' opcode locks balance group when /event/billing/bundle events are generated.
The 'PCM_OP_SUBSCRIPTION_SET_BUNDLE' opcode calls the 'PCM_OP_ACT_USAGE' opcode and due to which there is a significant delay in execution time.
Here the user did the below configuration and there is significant improvement in the execution time and locks are also reduced.
As the event /event/billing/bundle is not specified in the config rum, the rating should not be done.
Here the user have tested this RUM change and it resolves the performance issues they were having with respect to PCM_OP_SUBSCRIPTION_SET_BUNDLE. The problem with PCM_OP_SUBSCRIPTION_SET_BUNDLE is related to the fact that the notification event is being rated - it should not be.
Out of the box, these notification events should not be considered by the rating engine - these events are similar to the /event/group/sharing/discounts/create events, for example, which are correctly configured in pin_rum.
If the RUM is set to 'None' in the pin_rum file for the notification events, the locking is not required as no rating is done. In the current case, PCM_OP_ACT_USAGE is called to register the /event/billing/bundle/create and /event/billing/bundle/update events.
As these events are created without PIN_FLD_SERVICE_OBJ, PCM_OP_ACT_USAGE is triggering /account level locking - for no reason.
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