PCM_OP_BILL_RERATE_REBILL Fails with PIN_ERR_NONEXISTANT_ELEMENT When Related Accounts Are Specified In Rerating Request

(Doc ID 2322800.1)

Last updated on NOVEMBER 15, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.16.0 and later
Information in this document applies to any platform.

Symptoms

On : 7.5.0.16.0 version, Rerating/Rebilling
Instead of creating multiple re-rating requests, once for each account that is sharing, the user creates and groups sharing accounts into a single request.
A single call to PCM_OP_RERATE_INSERT_RERATE_REQUEST. All sharing accounts specified on input. When send in a single request for all the accounts to be rerated, PCM_OP_BILL_RERATE_REBILL Fails with PIN_ERR_NONEXISTANT_ELEMENT


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
created the rerate request:
r << $ 1
0 PIN_FLD_POID POID [0] 0.0.0.1 /account 490835609613 0
0 PIN_FLD_START_T TSTAMP [0] (1504764000) Sun Jun 17 00:00:00 2018
0 PIN_FLD_PROGRAM_NAME STR [0] "Plan Transition"
0 PIN_FLD_RERATE_FLAGS INT [0] 1
0 PIN_FLD_ACCOUNTS ARRAY [0] allocated 20, used 1
1 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 490835609613 0
1 PIN_FLD_RERATE_ACCOUNTS ARRAY [0] allocated 20, used 1
2 PIN_FLD_POID POID [0] 0.0.0.1 /account 490835604015 0
2 PIN_FLD_START_T TSTAMP [0] (1504764000) Sun Jun 17 00:00:00 2018
1 PIN_FLD_RERATE_ACCOUNTS ARRAY [1] allocated 20, used 1
2 PIN_FLD_POID POID [0] 0.0.0.1 /account 490835611278 0
2 PIN_FLD_START_T TSTAMP [0] (1504764000) Sun Jun 17 00:00:00 2018
1 PIN_FLD_RERATE_ACCOUNTS ARRAY [2] allocated 20, used 1
2 PIN_FLD_POID POID [0] 0.0.0.1 /account 490835611278 0
2 PIN_FLD_START_T TSTAMP [0] (1504764000) Sun Jun 17 00:00:00 2018
0 PIN_FLD_EVENTS ARRAY [0] allocated 20, used 1
1 PIN_FLD_EVENT_OBJ POID [0] 0.0.0.1 /event/session/telco/gsm/st_data -1 0
0 PIN_FLD_EVENTS ARRAY [1] allocated 20, used 1
1 PIN_FLD_EVENT_OBJ POID [0] 0.0.0.1 /event/session/telco/gsm/st_sms -1 0
0 PIN_FLD_EVENTS ARRAY [2] allocated 20, used 1
1 PIN_FLD_EVENT_OBJ POID [0] 0.0.0.1 /event/session/telco/gsm/st_mms -1 0
0 PIN_FLD_EVENTS ARRAY [3] allocated 20, used 1
1 PIN_FLD_EVENT_OBJ POID [0] 0.0.0.1 /event/session/telco/gsm/st_content -1 0
0 PIN_FLD_EVENTS ARRAY [4] allocated 20, used 1
1 PIN_FLD_EVENT_OBJ POID [0] 0.0.0.1 /event/session/telco/gsm/st_vmtt -1 0
0 PIN_FLD_EVENTS ARRAY [5] allocated 20, used 1
1 PIN_FLD_EVENT_OBJ POID [0] 0.0.0.1 /event/delayed/session/telco/gsm/st_voice -1 0
0 PIN_FLD_EVENTS ARRAY [6] allocated 20, used 1
1 PIN_FLD_EVENT_OBJ POID [0] 0.0.0.1 /event/delayed/session/telco/gsm/st_data -1 0
$
xop PCM_OP_RERATE_INSERT_RERATE_REQUEST 0 1

nap(15244)> xop PCM_OP_RERATE_INSERT_RERATE_REQUEST 0 1
xop: opcode 3766, flags 0
# number of field entries allocated 20, used 3
0 PIN_FLD_POID POID [0] 0.0.0.1 /account 1 0
0 PIN_FLD_RESULTS ARRAY [0] allocated 20, used 1
1 PIN_FLD_POID POID [0] 0.0.0.1 /job/rerate 490835611175 0
0 PIN_FLD_RESULTS ARRAY [1] allocated 20, used 1
1 PIN_FLD_POID POID [0] 0.0.0.1 /job_batch/rerate 490835607847 0


Changes

 

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