GL.IS_REVENUE And GL.IS_AR Functions In The GL Summary Queries Prevent Parallelism
(Doc ID 2582832.1)
Last updated on OCTOBER 31, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
During execution of G/L (General Ledger) Summary reports, issue is that the GL.IS_REVENUE and GL.IS_AR functions in the G/L Summary sql queries prevent parallelism, that is, including these function calls in the SQL for G/L Summary reports (for example, GL Summary UNBILLED UNEARNED, GL Summary BILLED) causes the Oracle query optimizer to serialize execution of the queries.
It is expected that these functions should not prevent parallelism while executing the GL Summary sql queries as it leads to poor performance.
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