Performance - PO Generate Suggestions

Yahoo Archive
1
Wayne,

I've never had to change the partplant.generatesugg field, but if I
did I would first ask Epicor about the write trigger on the field and
what potential effects. I would GUESS (emphasis on guess) it would
be safe. Without source code it's hard to tell.

If Epicor couldn't help, I would view the data dictionary help for
the field, and all related fields, for clues. If comfortable, test
on training db over and over until sure. Write an RB report to view
results in all related fields.

OK- all I said was obvious...

Good Luck,
Lonnie


--- In vantage@y..., Wayne Cox <wmc@u...> wrote:
> Any suggestions on how to speed up the purchasing "Generate
Suggestions"
> process on Vantage 4? Or if it's improved at all in 5.0?
>
> I tried tweaking some system parameters with no luck. Looks like
it just
> needs a fast network connection, and some reasonable CPU power.
Still
> takes about 5 minutes, though.
>
> Wonder how much could be knocked off getting rid of that absurd
part number
> display as it runs?! Stuff like that is usually a sign of a novice
> programmer developing with an unreasonably small test database.
>
> I did manage to knock about 40% off the time in our test DB by un-
setting
> the "generate suggestions" flag on all the Manufactured parts. Why
it
> process them at all is a bit of a mystery. Any ideas on
how "safe" it is
> to programmatically set PartPlant.GenerateSugg = false ? I let it
rip on
> our test stuff just to experiment, but don't like writing into
sensitive
> areas of our live data.
>
> -Wayne
2
Any suggestions on how to speed up the purchasing "Generate Suggestions"
process on Vantage 4? Or if it's improved at all in 5.0?

I tried tweaking some system parameters with no luck. Looks like it just
needs a fast network connection, and some reasonable CPU power. Still
takes about 5 minutes, though.

Wonder how much could be knocked off getting rid of that absurd part number
display as it runs?! Stuff like that is usually a sign of a novice
programmer developing with an unreasonably small test database.

I did manage to knock about 40% off the time in our test DB by un-setting
the "generate suggestions" flag on all the Manufactured parts. Why it
process them at all is a bit of a mystery. Any ideas on how "safe" it is
to programmatically set PartPlant.GenerateSugg = false ? I let it rip on
our test stuff just to experiment, but don't like writing into sensitive
areas of our live data.

-Wayne