I don't THIN you need AMM for this. WHERE the backflush occurs is determined by the backflush whse/bin called for in the job detail method OP's scheduled resource that is tied to the material.
Note: 400 series has a bug (perhaps resolved in 406+?) where it is really the resource GROUP's backflush whse/bin that controls where the backflush is done from.
I believe AMM only extends the number of OPs a method can have and also provides auto-move capability for WIP between OPs.
Rob
Note: 400 series has a bug (perhaps resolved in 406+?) where it is really the resource GROUP's backflush whse/bin that controls where the backflush is done from.
I believe AMM only extends the number of OPs a method can have and also provides auto-move capability for WIP between OPs.
Rob
--- On Tue, 1/20/09, Karl Dash <dashkarl@...> wrote:
From: Karl Dash <dashkarl@...>
Subject: [Vantage] Component Backflushing
To: "Vantage Group" <vantage@yahoogroups.com>
Date: Tuesday, January 20, 2009, 12:11 PM
Apparently I don't understand the options available to me for backflushing components on a job. We don't have AMM, so that may be part of the reason I'm not seeing what I want.
Â
We have "free stock" components like nuts, bolt, screws that we would like to know what the on-hand quantity is but NOT have to mass issue to the job. Rather, when the job operation they are associated with is complete, the on-hand would be reduced.
Â
What I am seeing is that I have a choice between A) non-quantity bearing parts that must have a zero on-hand (not desired). That will, at least, not require a mass issue to the job; or B) maintain parts as quantity bearing with an on-hand balance but now it needs to be evaluated in the process of mass issuing to a job.
Â
The backflush checkbox on the part plant record only gets into sharing the withdrawal of the component from multiple plants.
Â
Given my multiple wants is that possible within the constraints of the standard modules or is this an optional-cost AMM need? We are on 406 Progress.
Â
Thanks,
-Karl
[Non-text portions of this message have been removed]