Bruce
What are your app server logs saying?
Gary
________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Bruce Antonides
Sent: 06 November 2006 23:34
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Pre-MRP Exception Report
No, we don't have Product Configurator.
Bruce
--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"Gary Parfrey" <garyp@...> wrote:
Behalf
40yahoogroups.com> ] On
[Non-text portions of this message have been removed]
What are your app server logs saying?
Gary
________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Bruce Antonides
Sent: 06 November 2006 23:34
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Pre-MRP Exception Report
No, we don't have Product Configurator.
Bruce
--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"Gary Parfrey" <garyp@...> wrote:
>have
> I was asking because the MRP in Vantage 8.00.809 will hang, if you
> any unconfigured 'Configured' products in Firm Sales orders[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
>
>
>
> Gary
>
> ________________________________
>
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Behalf
> Of Gary Parfrey<mailto:vantage%40yahoogroups.com>
> Sent: 06 November 2006 18:35
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: RE: [Vantage] Re: Pre-MRP Exception Report
>
>
>
> Are you using the product configurator?
>
> Gary Parfrey
>
> ________________________________
>
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com><mailto:vantage%
40yahoogroups.com> ] On
> Behalf<mailto:vantage%40yahoogroups.com>
> Of Bruce Antonides
> Sent: 06 November 2006 17:20
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Re: Pre-MRP Exception Reportto
>
> I am not on SQL but on the Progress database. When we've had MRP
> hang, we've had to overwrite the whole database with a new copy.
> Currently, we're running MRP in our TEST account so it's not such a
> big deal but we it's difficult to justify using MRP if it's going
> tie our database up to the point where we have to restore a backup.at
> Is anyone else having a problem like this?
>
> A pre-MRP report to identify potential problems might help us to,
> least, continue our testing<mailto:vantage%40yahoogroups.com>
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com> ,<mailto:vantage%40yahoogroups.com>
> "Brad Feazell" <Brad_feazell@>
> wrote:
> >
> > If you are on V8 and SQL there are several SQL maintenance tasks
> that
> > will hang MRP. I've seen it happen when any of the following runs
> > during an MRP session: full text catalog population, SQL backup,
> index
> > rebuild/reorg.
> >
> > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com> ,the
> "Bruce Antonides" <bantonides@>
> > wrote:
> > >
> > > I've been studying the MRPLog report recently to research why
> MRPThis e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses.
> > > process hung. It was pointed out to me that a report that looks
> for
> > > problems in the database that may prevent MRP from processing
> would
> > be
> > > nice to run ahead of time to try and clear problems.
> > >
> > > Do any of you have a pre-MRP report like this?
> > >
> >
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
[Non-text portions of this message have been removed]