PCM_OP_PYMT_COLLECTION Opcode Create Item Even When It Fails
(Doc ID 1599346.1)
Last updated on MARCH 23, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.5.0]
Information in this document applies to any platform.
On BRM 7.5 ,When attempting to do a payment refund through Payment Tool (by calling PCM_OP_PYMT_COLLECT), when an error occurs, the refund item was created even if the pymt_collect opcode was failed.
/item/refund was created even there was an error and it has changed account due.
All objects created by this opcode are rolled back and leave customer due unchanged.
1. Try to create a refund batch (with one refund) from Payment Tool for a custom pay type. Skip one of the mandatory fields that is mandatory for the refund
2. Submit the refund.
3. An error will occur, but the /item/refund was created even with the error.
Sample input flist for PCM_OP_PYMT_COLLECT:
op_pymt_collect input flist
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