Transaction Register Performance Issue
(Doc ID 731377.1)
Last updated on FEBRUARY 12, 2018
Applies to:Oracle Receivables - Version 126.96.36.199 to 188.8.131.52 [Release 11.5.10]
Information in this document applies to any platform.
Running the concurrent program 'Transaction Register' has very poor performance. The process takes more than a day to complete and is unusable.
Review of the TKPROF identifies the following select statements that are executed excessively:
RA_CUSTOMER_TRX_LINES WHERE CUSTOMER_TRX_ID = :B1 ORDER BY LAST_UPDATE_DATE
RA_CUST_TRX_LINE_GL_DIST WHERE CUSTOMER_TRX_ID = :B1 AND ((ACCOUNT_CLASS =
'REC' AND LATEST_REC_FLAG = 'Y') OR (ACCOUNT_CLASS <> 'REC' AND
ACCOUNT_SET_FLAG = 'N')) ORDER BY LAST_UPDATE_DATE DESC
AR_PAYMENT_SCHEDULES PS, AR_CONS_INV CONS_INV WHERE PS.CONS_INV_ID =
CONS_INV.CONS_INV_ID AND PS.STATUS = 'OP' AND PS.CUSTOMER_TRX_ID = :B1
SELECT NVL(MIN(PS.DUE_DATE), ARPT_SQL_FUNC_UTIL.GET_FIRST_DUE_DATE(:B3 ,
AR_PAYMENT_SCHEDULES PS, RA_CUSTOMER_TRX CT WHERE CT.CUSTOMER_TRX_ID=
PS.CUSTOMER_TRX_ID(+) AND CT.CUSTOMER_TRX_ID = :B1
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
|1. Bug Summary|
|2. Fixed Files|
|3. Recommended Patches|
|4. Solution Steps|