My Oracle Support Banner

Change In Rerate_Rebill Behavior After Applying Patch 8431843 (Doc ID 942485.1)

Last updated on MARCH 06, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 and later
Information in this document applies to any platform.

Goal

After applying the <Patch 8431843> , the rerating behavior is changing.

The following is the difference in the search template to retrieve events to be rerated :

Before applying the patch :

 

Q1) In the input flist to rerating, if passed in the flag value as 2 (PIN_FLD_RERATE_BY_CREATED_T 0x02) , rerating should search and rerate events based on CREATED_T, but in the search above (after patch), it has END_T and CREATED_T.

Q2) What is the significance of the change in the search query template ?

Solution

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
Goal
Solution
References


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