Does anyone else seem to have an issue with Cash Requirements Payment Selection taking an unusually long time to complete? It might be partly due to volume but some of our check runs can take close to two hours to complete with the majority of that processing time due to Payment Selection.
Though volume could be a contributing factor I think it also is due to the initial set selection defined in the source LPL which uses only the fields below:
Vendor Group
Pay Group
Process Group
Company
Process Level
Payment Code
Every instance returned by that set is evaluated by multiple large rule blocks. For example that initial set selection could select a bucket of 30K open payments but the final selected payments when the job completes is 6k payments. It's possible there is some superfluous processing there that is slowing the process down.
The slow processing time might also be due to the manner in which the legacy Cobol was ported over to Java in the the Infor v11 code uplift; certain processes in Cobol are probably faster than Java and vice versa.
I'm considering putting in an enhancement request to have payment selection optimized, but am curious if other customers are experiencing similar issues.
Thanks!
Andy
