Is It Possible To Rollback Everything While Calling OP_PYMT_COLLECT Opcode
(Doc ID 2412965.1)
Last updated on MARCH 11, 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.
On : 220.127.116.11.0 version,
Consider a use case/scenario in which one wants to rollback everything while calling op_pymt_collect opcode for credit card payment type. To meet this purpose, a transaction is opened before calling the opcode and is aborted after the opcode call but it is seen that the /charge/cc event is gets committed in the database(DB). It appears like this happens to track the check point payments. However the requirement here is that the event should not be committed in the DB.
Is there a way or a workaround to achieve this use case in BRM(Billing and Revenue Management)?
Is there a flag which can be passed while calling OP_PYMT_COLLECT opcode which will ensure this event will not be committed in the DB?
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