My Oracle Support Banner

Pin_rerate Generates Duplicate Cycle Forward Charges When Using a Custom Parameter (Doc ID 1596211.1)

Last updated on MARCH 22, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.1.0 to 7.4.0.1.0 [Release 7.4.0]
Information in this document applies to any platform.

Symptoms

A custom "-batch_id" parameter has been 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


Actual behavior:
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.

Expected behavour:
Only 1 new Cycle Forward Charge would have been created to replace the 1 event which had been tagged with BATCH_ID=XYZ.




Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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