My Oracle Support Banner

Pin_recover is Failing while calling PCM_OP_PYMT_COLLECT with Wrong Input Flist (Doc ID 2925979.1)

Last updated on MAY 22, 2024

Applies to:

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

Symptoms

pin_recover application ran with recover_payment command line argument and is failing in production since it is calling PCM_OP_PYMT_COLLECT with wrong input flist
Application command used: pin_recover -recover_payment -pay_type 10003 -vendor <vendor_name> -verbose

Application is calling opcode with below input flist

0 PIN_FLD_POID POID [0] 0.0.0.1 /account 1 0
0 PIN_FLD_PROGRAM_NAME STR [0] "pin_recover -recover_payment"
0 PIN_FLD_CHARGES ARRAY [0] allocated 20, used 7
1 PIN_FLD_COMMAND ENUM [0] 9
1 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 9415520 0
1 PIN_FLD_EVENT_OBJ POID [0] 0.0.0.1 /event/billing/charge/cc 340443984340938599 2
1 PIN_FLD_ACH INT [0] 4
1 PIN_FLD_CHANNEL_ID INT [0] 0
1 PIN_FLD_BILLS [0] allocated 10, used 1
2 PIN_FLD_BILL_OBJ POID [0] 0.0.0.1 /bill 340373615596759175 0            !!!!!!!!!!!!!!!
1 PIN_FLD_BILLINFO_OBJ POID [0] 0.0.0.1 /billinfo 9414880

Here, PIN_FLD_BILL_OBJ is passed at level 2 under PIN_FLD_BILLS array (as mentioned by opcode specification)

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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