My Oracle Support Banner

Balance Group Is Not Synced With Pipeline Memory Correctly (Doc ID 2448395.1)

Last updated on APRIL 01, 2021

Applies to:

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


On Oracle Communications Billing and Revenue Management(BRM), version, consider the below scenario where it is observed that Balance Group is not synced with pipeline memory correctly.  


As per business requirement, the user has event level rounding as 6dp(decimal precision), item level rounding as 3dp and bill level rounding at 2dp.

Questions 1:

Why there is difference in behavior while restarting pipeline and syncing via ifw_sync queue for updating current balance via opcode as it is working fine after pipeline restart? Current behavior is not correct as user cannot restart pipeline in Production before every event. So same needs to be correctly handled with in-memory balance without pipeline restart.

Questions 2:

Here in this use-case, since the user has event level rounding as 6dp as per their business requirement,  minimum charge applicable for particular usage is 0.000001. User can't set resource balance as 0 as scenario involve giving discount on usage above 0. Hence we are setting minimum balance as 0.0000001 instead of 0.
When BRM is making 18 digit number into 15 digit, it does not round it and hence wrong value is getting synced with pipeline. Is it possible to round that 15 digits while converting?


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

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