Last updated on APRIL 16, 2013
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 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:
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
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