Problems With Reversals Via Payment Tool When Attempting To Validate Reason Code
(Doc ID 1359946.1)
Last updated on FEBRUARY 25, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
There is a requirement to validate the reversal reason code. Customization has been done to add the appropriate code in PCM_OP_BILL_POL_REVERSE_PAYMENT and set the ebuf properly. However, this causes inconsistent behavior in the processing of a batch reversals.
In the case of a reversal batch with a bad reason code in the middle, it will successfully process all elements up to the bad reversal code, then process nothing after that, and report a message that the batch was in error.
When reviewing the pinlog file, the ebuf remains set throughout the life of the batch, but the flist is destroyed and causing an error to be generated in the fm_bill_reverse_payment.c.
Need the reversals to allow validating the reason code, by letting the customized reversal policy opcode affect the calling opcode and respond to the error buffer properly without generating an error and aborting the remaining batch.
Steps to Reproduce:
- Add code to PCM_OP_BILL_POL_REVERSE_PAYMENT to validate the reason code provided as part of the reversal batch
- Create 3 customers with payments that need to be reversed
- Use Payment Tool to create a reversal batch and set the 1st and 3rd reversal to a good reason code, and the 2nd reversal to a bad reason code
- Validate and submit batch -- the bad reason code should be caught in the policy and set an ebuf
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