Rerating with Backout Does Not Have a Option to Backout a Particular Event
(Doc ID 2421080.1)
Last updated on SEPTEMBER 01, 2020
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On Oracle Communications Billing and Revenue Management(BRM), 22.214.171.124.0 Version,
Rerating with backout does not have a option to backout a particular event.
There is an option of backing out a particular event with the pin_rerate -r -backout parameter where you can give a custom parameter in the input file that was prepared for pin_rerate.
In the input file, you can give a particular event poid for which you want to do back_out only, but there is an issue with this where the opcode called op_subscription_rerate_rebill doesn't return the corresponding event from a search which is called in the flow.
There seems to be an issue with the SEARCH formed here. Because the search has event adjustment type as the 5th argument and 6th argument is actual /event poid which comes in search though the condition ( F5 = V5 or F6 = V6 ), it doesn't return anything. If I just run the plain search just by changing the sequence of arguments for example 5th argument as actual event poid and 6th argument as event adjustment poid type, then the search returns proper result. So there seems to be an issue with search formed to get the actual event from op_subscription_rerate_rebill opcode.
In this environment Elastic Charging Engine (ECE) is the rating engine.
The user is expected that re-rating with backout should have an option to backout a specific event to support Remote Application Platform Intelligent Network (RAP-IN) processing.
Not able to process RAP-IN records and thus not able to send the corrected records to partner operators.
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