Last updated on JULY 08, 2013
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 7.3.0]
Information in this document applies to any platform.
On : BRM 220.127.116.11.0 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:
- Created a multi schema env where in the primary will not have any accounts.
- Created an account on the secondary schema with a product P1.
- From testnap, call the PCM_OP_PRICE_SET_PRICE_LIST with PIN_FLD_DELETED_FLAG to delete the product.
The product gets deleted even though there is an active account in secondary schema which has purchased this product.
The product should not get deleted and a suitable error should be thrown.
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 hundreds of Community platforms