Audit Revenue Assurance Errors Out When Collections Process Is Creating Bill For Late Fee (Doc ID 1174171.1)

Last updated on SEPTEMBER 24, 2016

Applies to:

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

Goal

As a part of Collections Process Actions, late fee & financial charges are applied to the customer and items billed the very next day, using the "billnow" operation.

Audit Revenue Assurance auditing checks for duplicate bills, using the opcode PCM_OP_PROCESS_AUDIT_POL_CREATE. This opcode checks for duplicate bills using the following four parameters:

PIN_FLD_PROCESS_NAME
PIN_FLD_PROCESS_START_T
PIN_FLD_PROCESS_END_T
PIN_FLD_POID



In an Multi-threaded application it is possible to have all the above same, which is what happens when we execute pin_collections_process.

Hence, this fails and below is the error message:

D Sun Oct 17 01:00:34 2010 MySystem cm:13943 fm_process_audit_pol_create.c:642 1:MySystem:pin_collections_process:13937:6:3820:1275511652:1
duplicate count is 1
E Sun Oct 17 01:00:34 2010 MySystem cm:13943 fm_process_audit_pol_create.c:647 1:MySystem:pin_collections_process:13937:6:3820:1275511652:1
op_process_audit_create duplicate record found
<location=PIN_ERRLOC_FM:5 class=PIN_ERRCLASS_SYSTEM_DETERMINATE:1 errno=PIN_ERR_DUPLICATE:10>
<field num=0:0,0 recid=0 reserved=0 reserved2=0 time(sec:usec)=0:0>
<facility=0 msg_id=0 version=0>



Expected Results: billnow should not fail.

Actual Result: The billnow operation fails and thus the collections action also fails.



Solution

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