PCM_OP_SEARCH Opcode Returning Multiple Records (Doc ID 977432.1)

Last updated on SEPTEMBER 24, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.3.1.0.0 [Release 7.3.1]
Information in this document applies to any platform.
***Checked for relevance on 14-May-2013***
*** Checked for relevance on 07-25-2015 ***

Symptoms


Problem Statement


PCM_OP_SEARCH opcode flist returns multiple records for the same object.

Steps To Reproduce

1) Create the input flist of PCM_OP_SEARCH opcode as given below:

0 PIN_FLD_POID POID [0] 0.0.0.1 /search 0 0
0 PIN_FLD_FLAGS INT [0] 256
0 PIN_FLD_TEMPLATE STR [0] "select X from /collections_action/policy_action where ( F1 = V1 and F2 = V2 and F3 = V3 ) "
0 PIN_FLD_RESULTS ARRAY [0] allocated 8, used 8
1 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.0 / 0 0
1 PIN_FLD_BILLINFO_OBJ POID [0] NULL
1 PIN_FLD_CONFIG_ACTION_OBJ POID [0] NULL
1 PIN_FLD_DUE_T TSTAMP [0] (0) 01/01/1970 05:30:00:000 AM
0 PIN_FLD_ARGS ARRAY [1] allocated 1, used 1
1 PIN_FLD_DUE_T TSTAMP [0] (1263234600) 12/01/2010 00:00:00:000 AM
0 PIN_FLD_ARGS ARRAY [2] allocated 1, used 1
1 PIN_FLD_STATUS ENUM [0] 2
0 PIN_FLD_ARGS ARRAY [3] allocated 1, used 1
1 PIN_FLD_POID POID [0] 0.0.0.1 /collections_action/policy_action -1 0



2) Below is the output flist for PCM_OP_SEARCH opcode:


0 PIN_FLD_POID POID [0] 0.0.0.1 /search 0 0
0 PIN_FLD_RESULTS ARRAY [0] allocated 5, used 5
1 PIN_FLD_POID POID [0] 0.0.0.1 /collections_action/policy_action 277670 2
1 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 256736 0 <===== 1st Record for 256736
1 PIN_FLD_BILLINFO_OBJ POID [0] 0.0.0.1 /billinfo 254432 14
1 PIN_FLD_CONFIG_ACTION_OBJ POID [0] 0.0.0.1 /config/collections/action/custom 202408 0
1 PIN_FLD_DUE_T TSTAMP [0] (1263234600) 12/01/2010 00:00:00:000 AM
0 PIN_FLD_RESULTS ARRAY [1] allocated 5, used 5
1 PIN_FLD_POID POID [0] 0.0.0.1 /collections_action/policy_action 273932 2
1 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 264045 0
1 PIN_FLD_BILLINFO_OBJ POID [0] 0.0.0.1 /billinfo 264429 6
1 PIN_FLD_CONFIG_ACTION_OBJ POID [0] 0.0.0.1 /config/collections/action/custom 202408 0
1 PIN_FLD_DUE_T TSTAMP [0] (1263234600) 12/01/2010 00:00:00:000 AM
0 PIN_FLD_RESULTS ARRAY [2] allocated 5, used 5
1 PIN_FLD_POID POID [0] 0.0.0.1 /collections_action/policy_action 255312 2
1 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 256736 0 <===== 2nd Record for 256736
1 PIN_FLD_BILLINFO_OBJ POID [0] 0.0.0.1 /billinfo 254432 6
1 PIN_FLD_CONFIG_ACTION_OBJ POID [0] 0.0.0.1 /config/collections/action/custom 202408 0
1 PIN_FLD_DUE_T TSTAMP [0] (1263234600) 12/01/2010 00:00:00:000 AM
0 PIN_FLD_RESULTS ARRAY [3] allocated 5, used 5
1 PIN_FLD_POID POID [0] 0.0.0.1 /collections_action/policy_action 258814 2
1 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 254048 0
1 PIN_FLD_BILLINFO_OBJ POID [0] 0.0.0.1 /billinfo 257120 6
1 PIN_FLD_CONFIG_ACTION_OBJ POID [0] 0.0.0.1 /config/collections/action/custom 202408 0
1 PIN_FLD_DUE_T TSTAMP [0] (1263234600) 12/01/2010 00:00:00:000 AM


In the output flist we are getting two records for "/account 256736" and "/billinfo 254432". This behavior is unexpected.

Cause

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