Issue With Stored Procedure BILLING_UPDATES Called During Billing (Doc ID 1173404.1)

Last updated on OCTOBER 03, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.5.0.0.0 [Release 7.3.1 to 7.5.0]
Information in this document applies to any platform.
***Checked for relevance on 16-May-2012***

Symptoms


During billing of customer, the stored procedure BILLING_UPDATES is called. One of the input variables (the 12th) is BILL_NO – here is the cm.pinlog call:

This procedure performs the following sql statement:
Select mod_t from BILL_T where BILL_NO = :1

This statement is unnecessary for many reasons:
• Cm has all the fields and could pass the MOD_T (as an input parameter to the stored procedure) if needed.

Expected Result

The extra select mod_t from bill_t where bill_no = :1 should not be called

Changes

 

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