Unable to Close Service With Custom PIN_FLD_NODE_LOCATION
(Doc ID 2058414.1)
Last updated on JUNE 21, 2022
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.5.0]
Information in this document applies to any platform.
On 22.214.171.124.0 version of Billing and Revenue Management (BRM), Subscription Management:
As a business requirement, one user has invoking PCM_OP_CUST_UPDATE_SERVICES to close the service in BRM. To store an external unique product identifier, the field NODE_LOCATION has been 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 Out of Box (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 PIN_FLD_NODE_LOCATION is no longer there, the search failed and the transaction aborted.
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 user populate the PIN_FLD_NODE_LOCATION?
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