The Business Param 31day_billing Is Cached With Different Value In CM Than The Value Stored In DB.
(Doc ID 2866058.1)
Last updated on OCTOBER 02, 2023
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On : 22.214.171.124.0 version, CM
The 31day_billing business param is getting cached with a different values that the value stored in BRM DB. The value in the DB for 31day_billing is 0 but when cm is started user sees that the value is logged as 1 at 7th reference. This is causing issues with the API execution.
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