Last updated on SEPTEMBER 19, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 7.5.0]
Information in this document applies to any platform.
Given the input flist to PCM_OP_CUST_UPDATE_SERVICES below.
This includes three SERVICE array elements, only the first of which has a PIN_FLD_STATUS field.
One of the first jobs of the PCM_OP_CUST_UPDATE_SERVICES opcode, looking at the logs, is that it takes any SERVICES element that has a status on it and executes a PCM_OP_SEARCH to see if this service corresponds to the SUBSCRIPTION_OBJ. If it is, it will then slate some status changes on the same flist for all associated services with PIN_STATUS_FLAG_DUE_TO_SUBSCRIPTION_SERVICE set in the STATUS_FLAGS.
This resulted in incorrect results, as it found a /service/subscription object at element 1 even though there's no status change on that element.
Only the search on first service should have even occurred, as it's the only element with a PIN_FLD_STATUS on it.
If the PIN_FLD_STATUS element is the last element in the flist, as opposed to the first, there's no issue as it's already at the end of the flist.
We expect this search for related services to only occur for PIN_FLD_SERVICES elements where there is a status change.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms