My Oracle Support Banner

Unable To Close Service On BRM 7.5 With Custom PIN_FLD_NODE_LOCATION (Doc ID 2058414.1)

Last updated on FEBRUARY 19, 2019

Applies to:

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


On : version, Subscription Management

As a business requirement, the user is invoking PCM_OP_CUST_UPDATE_SERVICES to close the service in BRM. To store an external unique product identifier, the field NODE_LOCATION was used for that exact purpose in the custom code.

Just to be clear, the only change was to fill the field NODE_LOCATION in the purchased_product table. By doing so, the OOB search on the fm_subscription_cycle_utils.c code adds the field NODE_LOCATION to the search on the /event/billing/product/fee/cycle structure, but because the field is no longer there, the search fails and the transaction is aborted.

On checking /event/billing/product object, it is noticed that the field PIN_FLD_NODE_LOCATION is not present in this class and hence the search is failing.

The question is why is the search based on a non-existent field in the database?
What queries or what part of the code could cause problems if the customer populate the node_location field?


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

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