What field is the best field to consistently find the current OnHand quantity for any given item in the database? I have been using the field titled "TotalQTY" in tblstockitems but this field seems to be out of date most of the time. The only time this field is correct is after a "Check Resync Compact" is there a better method to find the actual OnHand quantity?
I have created a production planning spreadsheet for our production team but it is somewhat useless with out of date inventory numbers.
Thanks
By: Guest
Posted on: Jun 20 2023 at 08:49:01 AM
Look in tblStockItems for the .ItemID then use that ItemID in tblItemLocation.LocStockID to find the correct row.
The reason for the two table is that since v4 MiniMRP (v4E and v5Pro versions) has been able to store the same part number in multiple different warehouses so the quantity for each warehouse/location is in tblItemLocation. The old place tblStockItems.TotalQty is now just a place where minimrp does some math when deciding if an item exists in more than one place.
By: Guest
Posted on: Jun 20 2023 at 12:46:40 PM
Got it. So similar to how xCost is used for calculations and it is more reliable to lookup the default cost in tblitemsupplier for component cost.
For costing I have found that xCost is a good place to look for assembly build cost. Is this accurate?
Thank you for helping and supporting questions related to where to find this information using Excel . One of the best things about MiniMRP for our organization is the freedom it gives us with accessing our data.
By: Guest
Posted on: Jun 21 2023 at 10:45:46 AM
The most accurate place to look at an assembly's build cost is in the BOM view. Whenever you bring up the BOM view of an assembly the build cost is calculated fully based on the component costs.
But yes. that xCost is where MiniMRP stores the build cost so that it can get at it quickly.
Reply - add a comment to this topic.
You may enter letters, numbers and standard punctuation only. HTML and other scripts/tags will be rejected.
