EAR 9.2: AR_UPDATE Performance Degraded At Step AR_PGG_SERV.CCOFFST1.CF_LOOP Due To Join Removed From Existing FSCM 9.1 Codeline
(Doc ID 2553160.1)
Last updated on JANUARY 21, 2020
Applies to:PeopleSoft Enterprise FIN Receivables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
After a systems upgrade from PeopleSoft Enterprise FSCM 9.0 Version, to Release FSCM 9.2, the Receivables Functional Team has detected a performance degradation when running AR Update (Application Engine Program AR_UPDATE) when trying to post a somewhat large number of Payment Groups (around 70+).
When doing some trace analysis, the below Step has been detected as the main cause of performance degradation:
- Application Engine Program, Section, and Step: AR_PGG_SERV.CCOFFST1.CF_LOOP
In FSCM 9.0 Version, this Step AR_PGG_SERV.CCOFFST1.CF_LOOP had a standard join as follows:
AND R.BANK_SETID = B.SETID
AND R.BANK_CD = B.BANK_CD
AND R.BANK_ACCT_KEY = B.BANK_ACCT_KEY
However, in FSCM 9.2 Release, such join was updated to the below codeline instead:
AND R.BANK_SETID = %Bind(PGG_RECORD_AET.BANK_SETID)
AND R.BANK_CD = %Bind(PGG_RECORD_AET.BANK_CD)
AND R.BANK_ACCT_KEY = %Bind(PGG_RECORD_AET.B.BANK_ACCT_KEY)
It seems that the join was replaced with the Bind variables, causing the program to loop through hundreds of thousands of lines.
1.- Create several new Payment Worksheets, and place them all into Post Action Batch Standard
2.- Launch AR Update Run Control ID with the 'Payments' option selected
3.- Notice that the AR Update is taking a long time to complete, stuck at Step AR_PGG_SERV.CCOFFST1.CF_LOOP for a long time
The performance seems to have degraded to a level of taking over 6 hours to process 72 Payment Group transactions. This is blocking further processing on other needed daily programs, affecting the tasks, and data processing of the business.
The delivered AR Update AE Program should be able to handle in a timely manner all Payment Groups processing needed, without experiencing any performance degradation.
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