My Oracle Support Banner

No first Prorated Cycle Forward Charge For The Cycle in a Rerating scenario. (Doc ID 757847.1)

Last updated on AUGUST 17, 2018

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.
This problem can occur on any platform.

Article seems to relevant.


-- Problem Statement:
The product is purchased backdated with non-zero value for END_T. Rerating is done with the
"pin_rerate -rerate" after the backdate purchase and  it is observed that the pin_rerate backs out the
cycle charges for the CF event generated but does not apply the CF charges again for the account.

-- Steps To Reproduce:

1. Create the account with DOM 1 on 15 Nov 2008
2. Purchase the deal on 16 Nov 2008 and backdate the transaction to 15 Nov 2008 15:00:00 by
setting END_T on level 0
3. As the backdated transaction happens, /job_batch/rerate is created
4. Run pin_rerate -rerate


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.