Go live MRP mishapp

You should run an MRP regeneration (not net change) after you get your inventory updated. This will remove the existing unfirm job, recalculate the requirements and then create new unfirm jobs.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Tony Hughes
Sent: Thursday, December 29, 2011 11:01 AM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Go live MRP mishapp





You want to use DMT to delete the MRP####### job suggestions?
Just dump a spreadsheet with company in one column and the MRP jobs in another, and use DMT (Production -> Job Header) to delete them. It's slow going, maybe 8-9 jobs per minute for me, so keep that in mind.

--- On Wed, 12/28/11, Anon <jgiese@... <mailto:jgiese%40wisconsinconverting.com> > wrote:

From: Anon <jgiese@... <mailto:jgiese%40wisconsinconverting.com> >
Subject: [Vantage] Go live MRP mishapp
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Date: Wednesday, December 28, 2011, 1:23 PM



Our production manager ran MRP before we had inventory in our live database. It locked up the system, and after a reboot all is well, except there are bogus jobs in there. Will we be able to DMT in our lots and inventory while also updating some other parts already in the system, without issue or...? Any way to remove the demand links and jobs or would that make no difference at this point?

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
Our production manager ran MRP before we had inventory in our live database. It locked up the system, and after a reboot all is well, except there are bogus jobs in there. Will we be able to DMT in our lots and inventory while also updating some other parts already in the system, without issue or...? Any way to remove the demand links and jobs or would that make no difference at this point?
If they are unfirm jobs, MRP should delete them and recalculate next time it is run.

--- In vantage@yahoogroups.com, "Anon" <jgiese@...> wrote:
>
> Our production manager ran MRP before we had inventory in our live database. It locked up the system, and after a reboot all is well, except there are bogus jobs in there. Will we be able to DMT in our lots and inventory while also updating some other parts already in the system, without issue or...? Any way to remove the demand links and jobs or would that make no difference at this point?
>
Yes load in your inventory then re-run MRP and all unfirm jobs will be removed expect those that are required based on any demands in the system.

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Anon
Sent: 28 December 2011 13:24
To: vantage@yahoogroups.com
Subject: [Vantage] Go live MRP mishapp



Our production manager ran MRP before we had inventory in our live database. It locked up the system, and after a reboot all is well, except there are bogus jobs in there. Will we be able to DMT in our lots and inventory while also updating some other parts already in the system, without issue or...? Any way to remove the demand links and jobs or would that make no difference at this point?



[Non-text portions of this message have been removed]
You want to use DMT to delete the MRP####### job suggestions?
Just dump a spreadsheet with company in one column and the MRP jobs in another, and use DMT (Production -> Job Header)Â to delete them. It's slow going, maybe 8-9 jobs per minute for me, so keep that in mind.


--- On Wed, 12/28/11, Anon <jgiese@...> wrote:

From: Anon <jgiese@...>
Subject: [Vantage] Go live MRP mishapp
To: vantage@yahoogroups.com
Date: Wednesday, December 28, 2011, 1:23 PM








Â









Our production manager ran MRP before we had inventory in our live database. It locked up the system, and after a reboot all is well, except there are bogus jobs in there. Will we be able to DMT in our lots and inventory while also updating some other parts already in the system, without issue or...? Any way to remove the demand links and jobs or would that make no difference at this point?






















[Non-text portions of this message have been removed]