Top-up Payment Opcode Causes Transaction Locking When Called From Custom Pay-type
Last updated on JULY 24, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 7.5.0]
Information in this document applies to any platform.
On : 220.127.116.11.0 version, Payments
Top-up payment opcode causes transaction locking when called from custom pay-type
Customer is implementing a new payment type for handling Paypal payments.
When calling PCM_OP_PYMT_TOPUP the balance group is getting locked.
When call the PCM_OP_PYMT_COLLECT opcode with the exact same flist separately, the payment is processed properly.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms