From: Phil D. <ph...@du...> - 2004-10-05 01:13:05
|
I hope you dont mind Chris - we had a discussion on warehouse mgt earlier today and I though Jesse may well be interested in this project too.... Created on 5 October 2004 14:09:27. 05/10/2004 (09:15:03) chris_bice says: Phil, Did you say you thought it would be better to add a table called Bins, where it would have BinID, LocCode with a Constraint to Locations, LocCode, then add a field into LocStock, a BinRef field, Contrainted to BinID in Bins?? (09:15:30 ) Phil Daintree says: Yes I thought this would be the approach (09:16:01) chris_bice says: cool. I have alot of the code done then (09:16:26 ) Phil Daintree says: I have done a whouse mgt system before and it is kinda nice to know in one table what is where. It was in VB unfortunately (09:17:04 ) Phil Daintree says: Not sure about adding a field into Locstock (09:17:05) chris_bice says: Im a fan of VB. Its kind fo a hog, but it does a good job (09:17:20 ) Phil Daintree says: Not used it since that system (09:17:36 ) Phil Daintree says: Why do you need Bin in LocStock? (09:18:21) chris_bice says: So you dont have to update two tables when you update your stock (09:18:37 ) Phil Daintree says: Right. (09:18:53 ) Phil Daintree says: I need to chew this a bit (09:19:37) chris_bice says: Cause then all ther exsisting scripts will still work the same. The Select Sum(Qty) from LocStock where Location = ""Blah" will work fine (09:20:05 ) Phil Daintree says: Yeah ok, but what about a qty that is split accross several bays. The Quantity in LocCode is 4000 but this is in a bunch of Bins (09:20:51 ) Phil Daintree says: This would mean that there would need to be a gazillion LocStock records. We really only have one for each Location and StockID at the mo (09:21:03 ) Phil Daintree says: Called away will come back (09:21:09) chris_bice says: Here is my idea, from the StockStatus, screen your Location is Hyperlinked to a LocStatus screen that shows you the Bin Qty's for the said part, with in the Selected Location,and a Picture or diagram of where that bin is in the warehouse (09:21:13) chris_bice says: k (09:37:08 ) Phil Daintree says: Kinda like the serial number/batches inquiry? Have you played with the Serialised stock items yet. May be worth you having a look at - Make a new item and define it as controlled - the item can be defined as serialised ie only one item per reference or have many items per reference ie lot/batch control. When you receive PO items you need to enter the batch/serial no references. An inquiry from stock status shows what batches/S/Ns you have on hand (09:39:53 ) Phil Daintree says: I still like the idea of having the warehouse bins defined separately. ie one defines the warehouse bins available separately in the Bins table and this table is updated when the stock is booked in with the bin references where it is stored. It would easy to make a nice graphical picture of the warehouse bins with what is in each bin (09:45:11) chris_bice says: The only thing that "scares" me about doing it that way, is what happens if a SQL adds the items to the Bins table but doesn't update the LocStock with the correct Amount?? (09:47:56 ) Phil Daintree says: OK it means updating another table at the time of receiving and this is a downer, but it preserves all the existing functionality for invoicing/receiving/crediting/adjusting/transfering without a re-write. We then have an if $WarehouseManagementActive - not a Chris variable name I realise!! then update the bins. (09:48:29 ) Phil Daintree says: The bigger scare to me is having the LocStock quantites wrong. This is one vital area we cant afford to bugger up!! (09:49:50) chris_bice says: But The LocStock would potentially be wrong if your Bin table is correct, but your LocStock wasn't updated correctly?? (09:50:01 ) Phil Daintree says: Also some Locations may have warehouse management active and others not - i guess this is a flag in the Locations table. The system would need to inspect this flag on receiving stock to ensure that the appropriate link is available to allow allocation of the stock received to bins (09:50:40 ) Phil Daintree says: We are not changing anything about the LocStock logic under this scenario - so we can be confident it is not compromised (09:51:12 ) Phil Daintree says: The bin table stands apart - for those locations where warehouse management is active. (09:51:35) chris_bice says: K (10:21:13) chris_bice says: I dont like that Idea. It seems like we are going to have to create alot more scripts. But I see your point. Let me chew on it tonight, and start transforming some of my code over. (10:21:56) chris_bice says: IM also working on getting my RMA Code switched over as well (12:55:20 ) Phil Daintree says: The beauty of the approach is that a lot of the new scripts are already written albeit in a slightly veiled guise - called controlled/serialised stock. These would only need to be modified to use the new Bins table and Bob's ur fathers auntie! Phil |