9.05 Time and Expense Entry slow

I believe the issue is around scheduling.  Try putting some esitmated hours against a phase operation (try a large figure like 2000) after waiting for the phase job/operation to update try to put some time against that phase operation......Go get a coffee....have some lunch...perhaps even come back tomorrow.....No not exactly that bad but there is a significant delay. This is replicatable in the education database.  We are on 9.05.701 SQL 64 bit

Cheers
Simon Hall
According to some old posts, some of you have had trouble with time and expense entry being slow (the posts were for 9.05.702A, we are on 9.05.701). Our time slips are entered manually in the daily grid. What took 2 hours in Vantage takes over 4 in Epicor. Our testing wasn't thorough enough to show us there would be that much of a difference in entry time.  Traces show the time being lost is the DefaultJobNum method under the labor BO. We've played with the retrieve options under actions and tested without form customizations or BPMs without finding anything that helps. Sometimes the lag times are worse than others so I've been working on tuning the database...that's something that I've always meant to do, and maybe it would help. I've got a call into Epicor for slow time and expense entry which hasn't gotten very far. The tech keeps telling me that it just takes a while to verify the job information. The time ranges from 7-10 seconds to a couple of minutes. I had the tech watch our entry person today to show her what she goes thru every day. The topic is supposed to be brought up at a development meeting tomorrow to see if there really is a problem (um...yes there is!) and if there are any plans to do anything about it. Did any of you find anything to help this situation?

Sue

Hi Sue,


We had a big problem with this just after upgrading from 9.04.507A to 9.05.702A... it turns out I had an old UNENABLED BPM that was somehow impacting the system. I deleted that BPM, and our problems went away.

As I recall, we had a slowdown on the same DefaultJobNum object. Look around carefully and make sure you have no BPMs in place.


Ernie Lowell

Diba Industries