Thanks for the tip. We were on 809b and were waiting for 809d
because Epicor told us it would fix our errors. Yesterday we were
again told it would be ready tomorrow, so we went ahead and installed
809c and ran a regen last night. No errors!! Thank you, Kelly!!
because Epicor told us it would fix our errors. Yesterday we were
again told it would be ready tomorrow, so we went ahead and installed
809c and ran a regen last night. No errors!! Thank you, Kelly!!
--- In vantage@yahoogroups.com, Kelly Potratz <kpotratz_05@...> wrote:
>
> Yes, we had the same thing occur. We were told to apply 809C.
This fixed the issue.
>
> markewhittaker <markewhittaker@...> wrote: We are trying
to get one of our sites live on Version 8.0 after
> conversion from 6.1. One thing that is hanging us up is the fact
> that MRP Regen keeps dumping errors in the mfgsys80.server.log. We
> were able to eliminate most of the errors by doing some data
cleanup,
> but we still get the following two errors:
>
> [06/10/04@09:50:11.524-0500] P-001188 T-004140 1 AS --
> (Procedure: 'ApplyShopLoad es/SchedEngine.p' Line:1624) **
> GroupShopLoad already exists with Company "BAE"
ResourceGrpID "SMCNC"
> ResourceID "" Date 06/07/07. (132)
>
> [06/10/04@10:00:32.458-0500] P-002052 T-003504 1 AS --
> (Procedure: 'ApplyShopLoad es/SchedEngine.p' Line:1416) ** ShopLoad
> already exists with Company "BAE" ResourceGrpID "PROC"
> ResourceID "PRPIN" Date 08/06/07. (132)
>
> Those errors occur repeatedly (with different values for
> ResourceGrpId and ResourceID). We don't get any errors in the mrp
> logs, just the server log. We didn't even realize there was a
> problem until our Sys Admin noticed that he was running out of disk
> space and found that the server log file had gotten huge.
>
> We did one MRP run with Global Finite Scheduling checked and it ran
> error free. The next run without Global Finite started dumping
these
> errors again. We have been working with Epicor for weeks about this
> and no one has given us an explanation of what this error means or
if
> it will cause problems. They say the 809D patch will fix it and
have
> been promising it would be out since the beginning of last week.
>
> They told us that no one else gets these errors. But we converted
> their 6.1 training database to 8.0 and started MRP and got the same
> errors, as well as others. My guess is that no one else has thought
> to look for MRP errors in the server log. Has anyone else noticed
> these types of errors?
>
>
>
>
>
>
> ---------------------------------
> All-new Yahoo! Mail - Fire up a more powerful email and get things
done faster.
>
> [Non-text portions of this message have been removed]
>