Same here on 8.03.405a: $h!tcatcher bin A-0 (lowest alphanumeric in our bin schema).
Doesn't solve the problem but at least provides a way to clean up the inevitable messes.
Also (wherever practical) we put VB client code in place to overcome Vantage's deficient behavior (forcing whse bin when the process is consistent).
Rob Brown
--- Original Message ---
From:"Mark Wonsil" <mark_wonsil@...>
Sent:Sun 6/21/09 3:25 pm
To:<vantage@yahoogroups.com>
Subj:RE: [Vantage] Re: Job Receipt to Inventory - Bin & Warehouse Defaults
vantage@yahoogroups.com wrote:
periodically check that bin for activity.
Mark W.
Doesn't solve the problem but at least provides a way to clean up the inevitable messes.
Also (wherever practical) we put VB client code in place to overcome Vantage's deficient behavior (forcing whse bin when the process is consistent).
Rob Brown
--- Original Message ---
From:"Mark Wonsil" <mark_wonsil@...>
Sent:Sun 6/21/09 3:25 pm
To:<vantage@yahoogroups.com>
Subj:RE: [Vantage] Re: Job Receipt to Inventory - Bin & Warehouse Defaults
vantage@yahoogroups.com wrote:
> Vic:We created a "00" bin (zero - zero) and called in the catch-all bin. We
> Don't know if this relates to you, but we found that the
> "default" used is sometimes the first bin available. We are
> on verison 803-404BS. In some cases, for some reason (i.e.
> like a part not set up with a primary bin) the system will
> default to the bin that equals the first bin available in the
> system. To determine the first bin available, do an inquiry
> on all bins available, the first one listed is what I mean by
> the first available. In this case what we had done was create
> a bin called 1_Default Bin. That way it becomes obvious when
> the system incorectly wants to default there. (Sounds crazy I
> know, but we haven proven this one out)
periodically check that bin for activity.
Mark W.