PIN_ERR_POID_ALREADY_LOCKED Issue In Payment (Doc ID 2048708.1)

Last updated on SEPTEMBER 17, 2015

Applies to:

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

Symptoms

On :  7.5.0.9.0 version, Payments

Getting an error PIN_ERR_POID_ALREADY_LOCKED while running PCM_OP_PYMT_COLLECT, but same is working fine in 7.0

 
Error snippet :



Steps to reproduce:

 1. Create account with DOM 16.
 2. May 16: Run partial billing.
 3. May 17: Run final billing.
 4. Set pvt into Jul 8.
 5. Open transaction in testnap
             nap(55471)> open lock - 0.0.0.1 /billinfo 1690373
 6. Run payment via PCM_OP_PYMT_COLLECT:
 
nap(55471)> r pym.fl 1
nap(55471)> open lock - 0.0.0.1 /billinfo 1690373
nap(55471)> xop PCM_OP_PYMT_COLLECT 0 1
xop: opcode 113, flags 0
XOP "113" failed: err 120:PIN_ERR_POID_ALREADY_LOCKED, field 0/0:opsflds,
loc 5:PIN_ERRLOC_FM, 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] 0.0.0.1 /error_poid 1 0
0 PIN_FLD_ERR_BUF         ERR [0]
<location=PIN_ERRLOC_FM:5 class="PIN_ERRCLASS_SYSTEM_DETERMINATE":1 errno=PIN_ERR_POID_ALREADY_LOCKED:120>
<field num=0:0,0 recid=0 reserved=0 reserved2=0 time(sec:usec)=0:0>
<facility=0 msg_id=0 version=0>


 7. Same step is successful in 7.0.

 

 




 

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