My Oracle Support Banner

Is It Possible To Rollback Everything While Calling OP_PYMT_COLLECT Opcode (Doc ID 2412965.1)

Last updated on JULY 06, 2018

Applies to:

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

Goal

On : 7.5.0.19.0 version,

Scenario:

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.

Question:

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?
 

Solution

To view full details, 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 a vibrant support community of peers and Oracle experts.