Performance Issue: Billing Batch Performance Degradation for Sub Bill Segment Query
Last updated on JANUARY 12, 2018
Applies to:Oracle Financial Services Revenue Management and Billing - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On RMB v18.104.22.168.0 against FW v22.214.171.124, during BILLING batch run, the following statement is doing more than 8 million executions and every time returning 0 records:
SELECT BS.BSEG_ID, SAT.BI_PROC_SEQ, SA.SA_ID FROM CI_BSEG BS, CI_SA SA, CI_SA_TYPE SAT WHERE BS.BILL_ID = :1 AND BS.MASTER_BSEG_ID = :2 AND SA.SA_ID = BS.SA_ID AND SAT.CIS_DIVISION = SA.CIS_DIVISION AND SAT.SA_TYPE_CD = SA.SA_TYPE_CD ORDER BY SAT.BI_PROC_SEQ , SA.SA_ID /* SQL for COBOL program 'CIPBBSGF', SQL name 'S_SUBBS' */
The statement queries for sub bill segments for each of the bill segments generated.
This article provides guidance on how to turn off the feature to suppress this problematic SQL or be removed from the BILLING processing as it causes unnecessary performance degradation to the batch job. This affects production where the job is at risk for not completing within the expected time frame for slower performance.
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