WIP capture and record locking

Thanks for the reply Bill. Our capture takes 2 hours because it's for a month's worth of transactions at once. We also have it set to detail which I'm sure doesn't help. I think I'll restore a backup to Test and set the capture up after hours just to get a time. I realized yesterday that we've never run it outside of business hours when nothing else is running. Accounting has agreed it would be a good idea to schedule some time with an Epicor financial consultant to learn how to modify the settings for the capture, in the meantime they've agreed to run the WIP capture after hours. (We'll see...) Capturing weekly caused problems for us not only because of the performance problem but also because of the way we're locked out of making changes to labor entries after WIP is captured. I found a prior post that said they capture every Friday, but only thru the previous Friday to avoid most problems with locked labor (I think that came from Tom Christie); that may be a good compromise for us. We'll see what accounting works out with the consultant. Thanks again!

Sue
We are on Epicor 9.05.701. We're having trouble with a user running WIP capture during working hours; it takes about 2 hours for the big monthly capture. The database slows down to a crawl; the others users complain. I've monitored the database during this process and there's a tremendous amount of record-locking going on (imagine that!). I increased the -lkwtmo from 180 to 600. The user is getting errors when she captures WIP during working hours and keeps wanting me to increase the parameter to "fix" things. I tried to explain that parameter doesn't stop record locking; it only increases the time before it errors out; is that right? She also thinks nobody should be doing anything in Epicor when she captures WIP. I can't find anything in help or EpicWeb on WIP capture best practices. Do you run your WIP capture during or after working hours?We don't do anything to update inventory (receive, ship, post time slips, etc.) until the WIP capture is done. Are there other areas we shouldn't be working in while WIP is being captured? Any input would be greatly appreciated!

Sue

We run the capture process overnight, using the system agent to set it to run automatically. When we talked to Epicor I'm pretty sure they said this was the best practice. Another thing we found is that the posting rules are set automatically to detail, and it should take a little less time if they are set to summary. That's if you don't need to have each line item entered into the GL. We're on 701 also, but we were told this since we upgraded to 905 from 803. As far as what other areas to stay clear of while it's running, I'm not sure but I would think it would be anything that touches inventory. The only thing Epicor said when we had trouble was to make sure MRP wasn't running at the same time. (Our problem that time turned out to be some BPMs that were slowing things down.)

 

I hope this helps!

Thanks! I placed a call with Epicor first thing Friday morning, but haven't heard anything yet. I'm hoping to get enough verification that I can get backing from management to stop the practice of running WIP capture during work hours. I found the setting about detail and summary when capturing WIP and gave the info to the controller in February. He was supposed to talk to an E9 financial consultant about the settings after we got books closed for the year and hasn't done it yet. I reminded him about that last week. I really appreciate your reply, I was beginning to wonder if I was wrong to ask that it be run after hours.

Sue

Did you have a BPM running that might affect the Capture?

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of snielsen.hipco@...
Sent: Monday, May 05, 2014 11:18 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: WIP capture and record locking

 

 

Thanks! I placed a call with Epicor first thing Friday morning, but haven't heard anything yet. I'm hoping to get enough verification that I can get backing from management to stop the practice of running WIP capture during work hours. I found the setting about detail and summary when capturing WIP and gave the info to the controller in February. He was supposed to talk to an E9 financial consultant about the settings after we got books closed for the year and hasn't done it yet. I reminded him about that last week. I really appreciate your reply, I was beginning to wonder if I was wrong to ask that it be run after hours.

Sue

Thanks for the thought, but I don't believe that's the problem. It consistently takes two hours. It occasionally was sent to the review journal when the GL codes weren't set up correctly. Once the correction was made in the review journal the posting finished very quickly. The errors were lock wait timeout errors and they only happened when the WIP capture was run during working hours; we never received a lock wait timeout error when it was run after hours. I ran PROMON while WIP was being captured once and there was TONS of record locking going on. That makes sense to me as we had other users accessing Epicor at the same time. I tried to explain to the user capturing WIP that the other users were probably blocking her just as often as she was blocking them and PLEASE don't run it during working hours. To be doubly sure (if I can get them to capture WIP after hours!) I think it would be a good idea to rename the BPMExec folder just to be sure a BPM isn't contributing to the problem. Thanks for your suggestion and I will try to eliminate that as a possibility!

Sue

We’re on 905.702A.  We had originally intended to schedule the Capture process to run at night, once a week.  However, we never scheduled it and I prefer to keep it that way.  I run the Inventory WIP Reconciliation Report for a week’s worth of data.   After I’m satisfied there’s nothing to fix (posting to non-existent GL Accounts or wrong GL accounts, usually), I run the Capture process for the same time period.  I run it during the day, but haven’t heard it causing any issues.  It does take awhile, but not 2 hours.

 

----------------

Bill Kingsley

Controller

Compulink Corp.

ComDesign Inc.

Voice (727) 578-6503

Fax (727) 578-0120



CONFIDENTIALITY NOTICE

The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at 727-578-6280 and immediately delete the communication.

"This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."