Bob_Hansen
Senior Member Members
    Offline
 WOW, They have the Internet on computers now!
Posts: 1861
Location: Salem, NH
Joined: Nov 24 th, 2002
|
Re: xpost question
Reply #2 - Apr 4th, 2005 at 3:32am
|
Print Post
|
It may be too late or too much work, but I would recommend a sub table of locations for each part.. Each record would have the PartNumber, Location ID*, Qty, Status (Available, Allocated,Scrap, MRB, etc.), Last Date Counted, Cycle Count Frequency, etc.
You will also need to set up to handle transactions to move parts between locations.
*Location ID can have sections and truncated. Location could have multiple parts, a primary locations group for computer transactions, but lower level locations that do not need to be tracked on system. Example, Location could be Warehouse, Aisle, Rack, Shelf, Bin. You may only need to track to the Rack level to minimize inventory transactions, and only need entries if changeing Racks or higher. That gives you some flexibility on the shelves as qtys go up and down.
Location format could have multiple sections: Facility-WH-Aisle_Rack-(Shelf-Bin) Each of those sections can have their own coding databases/LU values and concatenated from pick lists.
This may sound too complex, but the key is still to have separate records for each Part/Location.
Take advantage of the hierarchical structure of Sesame. The design you have described now sounds like a carryover of flat file structures like we had with Q&A. Don't fall into that trap, use the more powerful tools.
|