During Billing, Why Two Read_field Calls On Same Bill Poid To Retrieve Different Columns? (Doc ID 1125034.1)

Last updated on FEBRUARY 26, 2019

Applies to:

Symptoms

During billing of an account, we can see 2 PCM_OP_READ_FLDS for the same bill poid, for different fields, in a row:
• First read retrieves the following fields:
0 PIN_FLD_POID POID [0] 0.0.0.1 /bill 45872973460 1
0 PIN_FLD_BILL_NO STR [0] ""
0 PIN_FLD_CURRENT_TOTAL DECIMAL [0] 0
0 PIN_FLD_PREVIOUS_TOTAL DECIMAL [0] 0
0 PIN_FLD_SUBORDS_TOTAL DECIMAL [0] 0
0 PIN_FLD_TOTAL_DUE DECIMAL [0] 0
0 PIN_FLD_DUE DECIMAL [0] 0
0 PIN_FLD_ADJUSTED DECIMAL [0] 0
0 PIN_FLD_DISPUTED DECIMAL [0] 0
0 PIN_FLD_WRITEOFF DECIMAL [0] 0
0 PIN_FLD_TRANSFERED DECIMAL [0] 0
0 PIN_FLD_RECVD DECIMAL [0] 0
0 PIN_FLD_NAME STR [0] "PIN Bill"
0 PIN_FLD_BILLINFO_OBJ POID [0] 0.0.0.1 /billinfo 25334622448 59

• The second read immediately after retrieves the ACCOUNT_OBJ_ID0:
0 PIN_FLD_POID POID [0] 0.0.0.1 /bill 45872973460 1
0 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 25334622064 0


There are 2 issues:
• If account_obj_id0 is needed, read it in the first PCM_OP_READ_FLDS (second read is not needed).
• Why reading the ACCOUNT_OBJ_ID0 => this BILL poid is the BILL_OBJ in the BILLINFO_T (this object is read just before, where you already have the ACCOUNT_OBJ?)

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.