My Oracle Support Banner

PIN_FLD_DESCR In EVENT_T Is Not Populated By PCM_OP_PYMT_RECYCLE_PAYMENT (Doc ID 1914714.1)

Last updated on MARCH 22, 2019

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

PIN_FLD_DESCR of EVENT_T is not populated by PCM_OP_PYMT_RECYCLE_PAYMENT in below scenario.

Scenario:

  1. Enable Payment Suspense in BRM
  2. Create Suspense Account
  3. Create a customer account
  4. Perform Billing.
  5. Perform a cash payment with wrong account id so that the payment will be suspended.
  6. Allocate the payment to correct account (First Recycle) using opcode, with a custom description in PIN_FLD_DESCR. Check the custom description in the corresponding /event/billing/payment/cash . It is present.
  7. Reallocate the payment to the suspense account (Second Recycle) using opcode, with a custom description in PIN_FLD_DESCR. Check the custom description in the corresponding output /event/billing/payment/cash . It is NOT present. This is the issue.
  8. See below example :
     

 

 

 

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.