My Oracle Support Banner

Object /uniqueness Entries Are Not Getting Rolled Back Once PCM_OP_CUST_DELETE_ACCT Execution Is Failed (Doc ID 2496857.1)

Last updated on APRIL 01, 2019

Applies to:

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

Goal

On BRM 7.5 PS21;

One is using PCM_OP_CUST_DELETE_ACCT to delete accounts in a multi-schema setup, using a custom wrapper opcode.

It is observed that when there is some error during this opcode execution, the transaction is rolled back, however the /uniqueness object entries are not being rolled back.

It is to be noted that in the current design, /uniqueness entries exist in primary schema, so the opcode flow opens a new context(transaction) to take care of deleting the same in primary (given that the account to be deleted can be in a different schema).

So the issue is that when PCM_OP_CUST_DELETE_ACCT is called from a wrapper opcode, any error after the opcode execution does not revert changes in the /uniqueness object. This is happening because /uniqueness deletion happens in new context.

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!


In this Document
Goal
Solution
References


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