Last updated on NOVEMBER 28, 2016
Applies to:PeopleSoft Enterprise FIN Receivables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
AR Update Step AR_PGG_SERV.CHK_RND.GET_RND Runs Very Long
ARUPDATE process includes AR_PGG_SERV.CHK_RND.GET_RND step which is called for each item. The code in this step selects the data from the PS_PENDING_DST table, but does not pass all of the Key Fields on the record.
Therefore, it ends up by using indexes on the table and performing a full table scan to pull the data.
According to customer's statement, within the AR_PDD_SERV.CHK_RND.GET_RND SQL statement there are 3 fields missing as compared to the delivered index on the PENDING_DST record. These missing fields are:- GROUP_ID, GROUP_SEQ_NUM, and DST_SEQ_NUM.
It seems that because these fields are missing causes Oracle to ignore this index and ends up by doing a full table scan of the PENDING_DST which includes 162,964,790 data rows.
1. Run ARUPDATE process for more than 8000 items when creating Finance Charges;
2. The process has been cancelled after 24 hours thinking that something went wrong as Process Monitor hadn't been updated.
3. Tried to speed up the process by creating an index that matches the selected criteria in the SQL step of the App Engine, but still it ran for 7.5 hours for 8900 items.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms