Pin_rerate Generates Duplicate Cycle Forward Charges When Using A Custom Parameter
(Doc ID 1596211.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 7.4.0]
Information in this document applies to any platform.
A custom "-batch_id" parameter was added to allow selective rating of individual events.
Prior to running pin_rerate, an account had 7 Cycle Forward Charges - only one of which was tagged with BATCH_ID=XYZ.
Executed: pin_rerate -t MM/DD/YYYY -batch_id batch_list -r
After pin_rerate, 1 Cycle Forward charge had been adjusted (the one which was tagged with BATCH_ID=XYZ, but 7 new Cycle Forward Charges had been created.
The expected behaviour was that only 1 new Cycle Forward Charge would have been created to replace the 1 event which had been tagged with BATCH_ID=XYZ.
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