My Oracle Support Banner

Errors In PCM_OP_PYMT_COLLECT When Blocking the Payment (Doc ID 2058402.1)

Last updated on JUNE 03, 2022

Applies to:

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


On : version, Collections Manager

Errors in PCM_OP_PYMT_COLLECT when block the production of the payment.

ERROR in cm.pinlog:

1) Adding to the pin_event_record_map configuration file to block the production of the payment (and refund) event for the following row:

  /event/billing/batch/payment: 0 

2) Loading of the new file with the utility:

  load_pin_event_record_map -d -v pr_pin_event_record_map

3) Stop and restart of cm;
4) Run of the pin_collect utility on a contract with Direct Debit pay_type.

The steps and results for “/event/billing/batch/refund” are about the same.
The only difference is step 4 for the nature of the operation involved:
Step 4 (refund): on an account with credit, call of PCM_OP_BILL_ITEM_REFUND first, and then PCM_OP_PYMT_COLLECT.

The results were the errors in the CM/DM pinlogs (for pin_collect case). The errors are the same in both payment and refund cases.


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.