Bin locations Blank Title 62525

Yahoo Archive
1
It sounds to me like all of that information belongs to the warehouse
bin. The warehouse bin has dimensions and a description. You could add
any additional fields you needed to describe the bin (like number of
bins).



Charlie Smith

Smith Business Services / 2W Technologies LLC

www.vistaconsultant.com <http://www.vistaconsultant.com/> /
www.2WTech.com







From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of jahatcher43
Sent: Monday, February 11, 2008 10:08 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Bin locations



I recently discovered that Vantage actually deletes PartBin records
once the balance goes to zero. We tend to use persistent locations for
parts and find this behavour to be undesireable since we wish to attach
additional bin data to the part bin. (ie. physical location, bin size,
number of bins, etc.)

Does anyone know of any way to modify this behavour or worked out
another approach for storing bin data that needs to be persistent?

I know I could use a user defined table but this puts us in the
position of trying to keep it in "sync" with the partbin table.

Any advise/experience would be greatly appreciated.

Thanks,

John





[Non-text portions of this message have been removed]
2
I recently discovered that Vantage actually deletes PartBin records
once the balance goes to zero. We tend to use persistent locations for
parts and find this behavour to be undesireable since we wish to attach
additional bin data to the part bin. (ie. physical location, bin size,
number of bins, etc.)

Does anyone know of any way to modify this behavour or worked out
another approach for storing bin data that needs to be persistent?

I know I could use a user defined table but this puts us in the
position of trying to keep it in "sync" with the partbin table.

Any advise/experience would be greatly appreciated.

Thanks,

John
3
John,

We also use persistent locations for our tooling parts. Our
part's "PrimBin" in the "PlantWhse" table defines where the parts
should be stored Couldn't you utilize this table?

--- In vantage@yahoogroups.com, "jahatcher43" <johnh@...> wrote:
>
> I recently discovered that Vantage actually deletes PartBin records
> once the balance goes to zero. We tend to use persistent locations
for
> parts and find this behavour to be undesireable since we wish to
attach
> additional bin data to the part bin. (ie. physical location, bin
size,
> number of bins, etc.)
>
> Does anyone know of any way to modify this behavour or worked out
> another approach for storing bin data that needs to be persistent?
>
> I know I could use a user defined table but this puts us in the
> position of trying to keep it in "sync" with the partbin table.
>
> Any advise/experience would be greatly appreciated.
>
> Thanks,
>
> John
>