Pin_recover -resubmit Option Dropping Fields Populated in fm_pymt_pol_pre_collect.c
(Doc ID 2208294.1)
Last updated on MARCH 17, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : 18.104.22.168.0 version, Payments
pin_recover -resubmit option dropping fields populated in fm_pymt_pol_pre_collect.c
Consider the below scenario:
1. Created an Direct debit account and the payment has failed and it check pointed
2. Run pin_clean to get the batch_id of the failed payment
3. Run pin_recover -reubmit with the same batch_id
There was a custom DM (Data Manager) named DM_global_pay to send the payment request out of BRM, which needed some customized information to process the payments like BILL_N , PIN_FLD_SOURCE and couple of other fields. The user populated those in fm_pymt_collect_pre_collect file for normal payment collect calls, and the same has been done when submitting payment again through pin_recover.
In pre_collect, when the request was coming from pin_recover with -resubmit option, the COMMAND will be 8. The user populated PIN_FLD_CHARGES array in pre_collect by searching the event using the batch_id and populated the other fields like BILL_NO and SOURCE field, which the custom DM required to process the payment.
However, by the time request reaches custom DM via charge_dd opcode, the fields added by fm_pymt_collect_pre_collect.c have been dropped and caused the request to fail.
The same did not happen in case of normal payment_collect calls for collect_DD and cancel_dd calls.
Ideally, the fields should not be dropped, or there should be some more hooks before the call to DM_global_pay to add those fields.
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