My Oracle Support Banner

PCM_OP_CUST_MODIFY_PAYINFO Opcode Looking For PIN_FLD_INHERITED_INFO Structure (Doc ID 1970091.1)

Last updated on AUGUST 07, 2018

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.5.0]
Information in this document applies to any platform.


On Oracle Communications Billing and Revenue Management(BRM), version, Customer Registration, while updating a /payinfo object using 'PCM_OP_CUST_MODIFY_PAYINFO' opcode it throws the below error where it is looking for 'PIN_FLD_INHERITED_INFO' structure in the input flist to update the /payinfo object.

e.g. input flist
0 PIN_FLD_POID POID [0] /payinfo/invoice 3875617 0
0 PIN_FLD_RELATIVE_DUE_T TSTAMP [0] (5184000) 01/03/1970 19:00:00:000 PM
0 PIN_FLD_INHERITED_INFO SUBSTRUCT [0] allocated 20, used 0
>xop 74 0 1
xop: opcode 74, flags 0
XOP "74" failed: err 3:PIN_ERR_NOT_FOUND, field 0/66:PIN_FLD_INHERITED_INFO,
loc 6:PIN_ERRLOC_FLIST, errclass 1:PIN_ERRCLASS_SYSTEM_DETERMINATE, rec_id 0, resvd 0
# number of field entries allocated 20, used 2
0 PIN_FLD_POID POID [0] /error_poid 3875617 0

 Here the /payinfo object does not have a 'PIN_FLD_INHERITED_INFO SUBSTRUCT' when checked on the Object browser or when a robj is done on the /payinfo object.


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

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