Steven,
 In v8 there is no automatic, incremental lot number created for each receipt so the person in Receiving needs to have a log of the next number to be used or you will need a customization to create such a number. We have gone that route storing the number in the Company table. I understand that this has been corrected in v9 much the way serialization is handled.
-Karl
________________________________
From: Steven Gotschall <sgotschall@...>
To: "vantage@yahoogroups.com" <vantage@yahoogroups.com>
Sent: Wednesday, March 28, 2012 7:00 AM
Subject: Re: [Vantage] Re: Lot control
Â
Thanks. That helps a lot.
________________________________
From: carl.heeder <carl.heeder@...>
To: vantage@yahoogroups.com
Sent: Wednesday, March 28, 2012 9:47 AM
Subject: [Vantage] Re: Lot control
Â
We are on 8.03.409 and use lot extensively. There are a lot of subtle things about it but basically, you can require lots to be used for specific parts. Once you do, any receipt of this part, issue of the part, etc. will require using a lot number. Lot numbers are unique by part in 8.03. Inventory quantities by lot are stored in the PartBin table. There is no stock status report by lot - you will have to develop your own if you want it. There are a few places where a user can create a lot when you might want to keep that from happening. For example, o conformance requires providing a lot on the "in" side and allows creation of a different lot on the "out" side. Also if you use AMM, you cannot request a move of a specific lot so the move order does not specify the lot to be moved; the lot is identified once the material is actually moved. There is no such thing as a global lot (like a global part) so lots between companies has to be managed yourself.
But overall, it works well if you can live with a few holes in the controls it offers.
If you want to discuss, call me or write 281-525-2188 cheeder@...
 In v8 there is no automatic, incremental lot number created for each receipt so the person in Receiving needs to have a log of the next number to be used or you will need a customization to create such a number. We have gone that route storing the number in the Company table. I understand that this has been corrected in v9 much the way serialization is handled.
-Karl
________________________________
From: Steven Gotschall <sgotschall@...>
To: "vantage@yahoogroups.com" <vantage@yahoogroups.com>
Sent: Wednesday, March 28, 2012 7:00 AM
Subject: Re: [Vantage] Re: Lot control
Â
Thanks. That helps a lot.
________________________________
From: carl.heeder <carl.heeder@...>
To: vantage@yahoogroups.com
Sent: Wednesday, March 28, 2012 9:47 AM
Subject: [Vantage] Re: Lot control
Â
We are on 8.03.409 and use lot extensively. There are a lot of subtle things about it but basically, you can require lots to be used for specific parts. Once you do, any receipt of this part, issue of the part, etc. will require using a lot number. Lot numbers are unique by part in 8.03. Inventory quantities by lot are stored in the PartBin table. There is no stock status report by lot - you will have to develop your own if you want it. There are a few places where a user can create a lot when you might want to keep that from happening. For example, o conformance requires providing a lot on the "in" side and allows creation of a different lot on the "out" side. Also if you use AMM, you cannot request a move of a specific lot so the move order does not specify the lot to be moved; the lot is identified once the material is actually moved. There is no such thing as a global lot (like a global part) so lots between companies has to be managed yourself.
But overall, it works well if you can live with a few holes in the controls it offers.
If you want to discuss, call me or write 281-525-2188 cheeder@...
--- In vantage@yahoogroups.com, "Steven" <sgotschall@...> wrote:
>
> We are on Vantage 8.03.408A Progress and are considering implimenting lot control on some of our parts. Could someone provide a brief description on how lot control works in Vantage or point me to some documentation about it. The help file is pretty skimpy on the subject.
>
> Thanks
>
> Steven G.
>
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]