My Oracle Support Banner

PIN_FLD_DEBIT_NUM Is Not Getting Populated in Event_billing_payment_cc_t in BRM 12 PS4 (Doc ID 2868551.1)

Last updated on MAY 11, 2022

Applies to:

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



The class /event/billing/payment/cc was customized and the field PIN_FLD_DEBIT_NUM added to that class to support a custom business requirement. After upgrading system from Billing and Revenue Management (BRM) 7.5 to 12 Patch Set 4, issue is that after making a payment the field PIN_FLD_DEBIT_NUM is not getting populated in event_billing_payment_cc_t (it is updated as null), but it was getting populated in BRM 7.5. 

As a result, for payment inquiry, debit card number is not visible as the said field is null in the BRM database.

More context:

As per the business requirement PIN_FLD_DEBIT_NUM was a necessary information once the payment is successfully posted in BRM, so /event/billing/payment/cc class was being used instead of /event/billing/charge/cc class (where the PIN_FLD_DEBIT_NUM is already present out of the box). Also as per business requirement flow, different card details can be used for each payment which needed to be stored with the payment event.


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

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