Pcm_op_pymt_collect Payment Opcode Returns Error, But Payment Goes Through

(Doc ID 753382.1)

Last updated on SEPTEMBER 20, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.
***Checked for relevance on 28-Nov-2011***


-- Problem Statement:
When there is an error converting from original currency to primary during PCM_OP_PYMT_COLLECT, the payment still get posted to the account when the PCM_OP_PYMT_COLLECT indicates the opcode is failing as below. The behavior will mislead the CSR to re-post the same payment to the account.

nap(24814)> xop PCM_OP_PYMT_COLLECT 0 1
xop: opcode 113, flags 0
# number of field entries allocated 20, used 2
0 PIN_FLD_POID POID [0] /account 1 0
0 PIN_FLD_RESULTS ARRAY [0] allocated 20, used 6
1     PIN_FLD_ACCOUNT_OBJ POID [0] /account 191286 0
1     PIN_FLD_TYPE ENUM [0] 0
1     PIN_FLD_DESCR STR [0] "service unavailable"

-- Steps To Reproduce:

  1. Create a GSM account with monthly_cycle_forward event on May 1, 2008
  2. PVT to June 1, 2008
  3. From Development Center, locate the /item/cycle_forward event for the account and set PIN_FLD_CURRENCY to 0.
  4. From Payment Tool, pay the due amount.
  5. The Payment Tool pops up a message box and complains:
    "One or more payments could not be submitted. For detailed information for a particular payment, read the message displayed in the status-bar. Do you want to include the failed payments in a new batch and validate them again"?
  6. Click on Cancel to close the pop-up message box.

Expect Result:
The payment should not get posted to the account.

Actual Result:
The payment posted to the account.


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