Unable To Close Service On BRM 7.5 With Custom PIN_FLD_NODE_LOCATION
Last updated on OCTOBER 15, 2015
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.5.0]
Information in this document applies to any platform.
On : 18.104.22.168.0 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?
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