My Oracle Support Banner

Rerating With Backout Is Not Working With Custom Field Option (Doc ID 2447705.1)

Last updated on MARCH 12, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.18.0 and later
Information in this document applies to any platform.

Symptoms

On : 7.5.0.18.0 version, Rerating/Rebilling

Followed the steps provided in doc https://docs.oracle.com/cd/E16754_01/doc.75/e16711/prc_rerate_pin_rerate_use.htm#BRMPR926
and created the custom parameter for account, eventpoid and etc.

ACTUAL BEHAVIOR
---------------
On executing pin_rerate with pin_rerate -r -backout -account account.txt -t 07/21/2018, one could see the adjustment event getting created successfully as expected.
Note: The account.txt contains /account <account_poid>

On executing pin_rerate with pin_rerate -r -backout -eventPoid eventPoid.txt -t 07/21/2018 one could not see the adjustment event getting created.
However the status on the pin_rerate shows as successful.
Note: The eventPoid.txt contains /event/delayed/session/telco/roaming/gsm .

EXPECTED BEHAVIOR
-----------------------
On executing pin_rerate with pin_rerate -r -backout -eventPoid eventPoid.txt -t 07/21/2018 an adjustment event should have created.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Follow the steps provided in doc https://docs.oracle.com/cd/E16754_01/doc.75/e16711/prc_rerate_pin_rerate_use.htm#BRMPR926
2. select an account that has usage events and try to rerate by running custom field option

Example: eventPoid

pin_rerate -backout -eventPoid eventPoid.txt -t 07/21/2018



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
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.