My Oracle Support Banner

While Deleting Products, Check Fails On Accounts In Multi-schema Setup (Doc ID 1559721.1)

Last updated on JULY 08, 2013

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.3.0]
Information in this document applies to any platform.


On : BRM version, Pricing module;

The issue is that, on a multi-schema setup where the first schema only contains the uniqueness table and no actual accounts, when calling PCM_OP_PRICE_COMMIT_PRODUCT to delete a product, one will notice that it even deletes products which are currently purchased by active accounts.

It looks like while searching for the products, it does a simple PCM_OP_SEARCH on /purchased_products on the current DB. In the specific case reported here, that's the uniqueness DB which has no accounts, so every product could be deleted.

Steps to reproduce:

  1. Created a multi schema env where in the primary will not have any accounts.
  2. Created an account on the secondary schema with a product P1.
  3. From testnap, call the PCM_OP_PRICE_SET_PRICE_LIST with PIN_FLD_DELETED_FLAG to delete the product.

Actual result:

The product gets deleted even though there is an active account in secondary schema which has purchased this product.

Expected result:

The product should not get deleted and a suitable error should be thrown.


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.