403D: What does "Minimize WIP" actually do?

Yahoo Archive
1
Thanks for pointing me in the right direction Stephen.
Rob Brown

Stephen Edginton <stephene@...> wrote:
Rob,

Just incase you haven't already looked, there is a
explanation and example in the Scheduling Technical Reference guide,
available on Epicweb (documentation - Vantage - 803.400)

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Robert Brown
Sent: Friday, December 21, 2007 5:56 PM
To: vantage@yahoogroups.com
Subject: [Vantage] 403D: What does "Minimize WIP" actually do?

I'm playing with the "Minimize WIP" checkbox (Scheduling Codes field) on
403D and it clearly is having an impact on (forward scheduled jobs)
finite global scheduling results.

Jobs assigned a forward schedule code (with minimize WIP checked) end up
being scheduled as Due (often VERY) late to their Req'd By dates. I'm
finding this to be true even when there is no apparent capacity
contention for a required resource (or any materials with insufficient
o/h to cover requirements - whether 'constrained' material or not).

The Help is useless... It simply says "Use this to"... and doesn't
finish the sentence.

I'm finding nothing on the topic on the Epicor sites other than a few
sales-pitch oriented DataFlow 5.11 docs (with no explanations as to how
it works).

Does anyone have any idea what this scheduling code attribute value
actually does to change the process flow of the scheduling logic?

Any insight would be helpful.

Thanks

Rob Brown

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






---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.

[Non-text portions of this message have been removed]
2
I'm playing with the "Minimize WIP" checkbox (Scheduling Codes field) on 403D and it clearly is having an impact on (forward scheduled jobs) finite global scheduling results.

Jobs assigned a forward schedule code (with minimize WIP checked) end up being scheduled as Due (often VERY) late to their Req'd By dates. I'm finding this to be true even when there is no apparent capacity contention for a required resource (or any materials with insufficient o/h to cover requirements - whether 'constrained' material or not).

The Help is useless... It simply says "Use this to"... and doesn't finish the sentence.

I'm finding nothing on the topic on the Epicor sites other than a few sales-pitch oriented DataFlow 5.11 docs (with no explanations as to how it works).

Does anyone have any idea what this scheduling code attribute value actually does to change the process flow of the scheduling logic?

Any insight would be helpful.

Thanks

Rob Brown


---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.

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

Just incase you haven't already looked, there is a
explanation and example in the Scheduling Technical Reference guide,
available on Epicweb (documentation - Vantage - 803.400)



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Robert Brown
Sent: Friday, December 21, 2007 5:56 PM
To: vantage@yahoogroups.com
Subject: [Vantage] 403D: What does "Minimize WIP" actually do?



I'm playing with the "Minimize WIP" checkbox (Scheduling Codes field) on
403D and it clearly is having an impact on (forward scheduled jobs)
finite global scheduling results.

Jobs assigned a forward schedule code (with minimize WIP checked) end up
being scheduled as Due (often VERY) late to their Req'd By dates. I'm
finding this to be true even when there is no apparent capacity
contention for a required resource (or any materials with insufficient
o/h to cover requirements - whether 'constrained' material or not).

The Help is useless... It simply says "Use this to"... and doesn't
finish the sentence.

I'm finding nothing on the topic on the Epicor sites other than a few
sales-pitch oriented DataFlow 5.11 docs (with no explanations as to how
it works).

Does anyone have any idea what this scheduling code attribute value
actually does to change the process flow of the scheduling logic?

Any insight would be helpful.

Thanks

Rob Brown






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