It does make a difference as to the user id but if you are running it as a security manager you are okay.
As to locking up, I have found this to happen mostly from 2 different reasons:
1. Using more than 1 MRP Processes and or more than 1 Schedulers.
2. You have a new part in the BOM with an unapproved revision.
Number 1 will cause it if you have a long running MRP regen. I know of people that use more than 1 process without any problems and I have been able to do so if MRP does not process for a long period of time. I have not tried it for a while since I just gave up on it. Our business has dropped off enough that MRP does not take very long to process anyway.
Number 2 should not happen but it does. As indicated, it is a new part without an approved revision but it was added to a current BOM. I have never submitted it to support but I have brought it up at user group meetings when the Epicor MRP manager was present.
When you submit MRP select at least MRP for the logging level. You can then look in the logs and see when MRP locked up. If it is being caused by number 2 then you can narrow down the culprit.
Charles Carden
IT Manager
Manitex, Inc.
Georgetown, Texas
As to locking up, I have found this to happen mostly from 2 different reasons:
1. Using more than 1 MRP Processes and or more than 1 Schedulers.
2. You have a new part in the BOM with an unapproved revision.
Number 1 will cause it if you have a long running MRP regen. I know of people that use more than 1 process without any problems and I have been able to do so if MRP does not process for a long period of time. I have not tried it for a while since I just gave up on it. Our business has dropped off enough that MRP does not take very long to process anyway.
Number 2 should not happen but it does. As indicated, it is a new part without an approved revision but it was added to a current BOM. I have never submitted it to support but I have brought it up at user group meetings when the Epicor MRP manager was present.
When you submit MRP select at least MRP for the logging level. You can then look in the logs and see when MRP locked up. If it is being caused by number 2 then you can narrow down the culprit.
Charles Carden
IT Manager
Manitex, Inc.
Georgetown, Texas
----- Original Message -----
From: leann_37
To: vantage@yahoogroups.com
Sent: Monday, March 08, 2010 11:44 AM
Subject: [Vantage] 408b MRP question
We are on 8.03.408b. Just started running MRP (regen) on our test server, in preparation for running in Production, and it is hanging up every night. I didn't have it logging, so we're starting that tonight, and infrastructure is finding out what else is happening at night on the test server. In the meantime, he asked me a question I can't answer to his satisfaction. who's login does vantage use for database authentication when it runs? I always figured as long as it runs from either manager or a security manager login, it didn't matter whose login it fired from, but that may be my ignorance. Does it make a difference?
Thanks in advance!
- leAnn
[Non-text portions of this message have been removed]