Subject: Job/Purchase requirements...BOM?

I sincerely agree with your statements below. It sounds like our procedure
(or lack of) is exactly the same as yours, if we need another part, we just
add it to the job and the run suggestions so it is generated. On 3.0, this
worked well for us, but since 4.0, it takes up to 10 minutes to generate and
has been awful, so we have stopped using the generate, which has been
harmful to us as well. We also did not always schedule our jobs, but now, a
suggestions will not be generated unless the job is scheduled, so we now
have to schedule every job before we buy, which has also caused us time and
problems. Apparently, this change was due to MRP, but companies without
MRP are very negatively affected without any benefit, Very frustrating for
the users!
We used to use this all the time. This new "feature" of having to schedule
the job to see purchasing requirements has really hurt us. We use the job
as the BOM, so when we need more of one part, we add another material line,
so we're not grouping all the same parts together. This wouldn't be such a
huge issue if we had a good BOM.

Anyone have a good BOM either from the PM or from the Job?

And we can't generate suggestions over and over b/c it takes so long.

Thank you.

Amy MacKay
Parkinson Technologies

Message: 2
Date: Thu, 25 Jan 2001 18:23:59 -0000
From: "Ben Roush" <broush@...>
Subject: Job/Purchase requirements

I would like to know if anyone else is having this problem. We are
running 4.00.904. and have been since the first of the year. When we
create a job with all the details, we generate purchasing suggestions
to purchase the material (to the Job). The material has been received
to the job. Then a release comes in to increase the job qty, we then
increase all areas, rescheduled, it shows the increase for the extra
material in job tracker, but it won't show up in time phase or
generate a new suggestion to purchase anymore material. This is a BIG
problem for us as we have alot of changes all the time! Any help
would be appreciated. Epicor knows about this problem and has NO fix
at this time.