Is there a way to define a bin quantity per part?
We want to be able to store how many of each part should go into a standard BIN. Among other things we want to use this as logic to calculate how many bins will be needed (and therefore print the correct number of labels) when producing a large number of parts that will need to be put into multiple bins.
For example part X might be defined with 12 per BIN and part Y with 20 per BIN. Producing 60 of each part will need 5 bins for part X and 3 bins for part Y.
The only thing out of the box remotely close to what you want that I can think of are the BIN Replenishment settings:
These settings are used in conjunction with the Replenishment Workbench, the function of this dashboard doesnât sound exactly like what you want, which seems more like guidance for the people doing put aways, to help them know how many labels to print, how many empty BINs they need to find, etc.
Even if you didnât use the Replenishment Workbench dashboard, you may be able to leverage these settings in a custom solution. You have other options here as well. The Part and the BIN allow you to specify cubic volume values, which you could use to help calculate how much space X of part A takes up and how much space you have available in BIN B.
If Replenishment Workbench doesnât get you where you want I think you are looking at a custom solution.
We donât use it so I canât help too muchâŚbut there is a Warehouse Bin Size Group that you can optionally tie to your bins. If your bins are symmetrically arranged (or at least not too many variations) then this might be an option. Donât know if it limits what you receive into the bin (edit: or if itâs just for reporting purposes, estimating available space, etc)âŚ
Thanks for the details.
It seems like if we tried to repurpose the replenishment aspect for our current solution weâd run the risk of having it backfire in the future if we ever use this functionality properly, or if we do/add something that leverages a field weâve hijacked. "The Part and the BIN allow you to specify cubic volume values, which you could use to help calculate how much space X of part A takes up and how much space you have available in BIN B". This may be viable if we explicitly fudge the dimensions so it could calculate back to result in X number of parts being the full amount (regardless of actual measurements). It would make the calculation more complex each time to work out the simple answer to how many bins are needed when reporting production of X qty of parts, but might be manageable.
Hopefully thereâs a better solution to allow for a more direct check on âhow many of this part can go into a binâ but itâs worth a look if nothing better exists.
Thanks for the feedback. I donât know if this will give what we need as it defines the size of the bin itself and isnât tied to the size of each part. Potentially if we also define a size for each part then it would calculate how many of those parts could fit in each bin, but if we just wanted to check âhow many bins/labels do I need to report X quantity of this part?â it gets more complex to implement the calculation.
Ideally, if nothing natively exists, it would be good if I could just leverage an simple integer value that can be set up on each part (an attribute?) that specifies how many of that part should go in each standard bin.
Attribute might work, or maybe something with a UD table. We donât stock our warehouse with âmanaged capacityâ outside of its four walls. Everythingâs considered a bulk location and could have one or more parts in it.
Yeah, it is probably a bad idea for me to suggest using a field for a purpose other than what it is intended. If Replenishment Workbench doesnât do what you want, at that point you are probably better off adding a custom field to use in a custom solution.
Is this something that is intended for this purpose, or is the âPer Containerâ field meant more for shipping/packaging? I note the âReturnable Containerâ field that is next to this.
Either way it may work for us but it would be important to know if this would be us repurposing a field intended for something else, or if this is the intended usage.
AFAIK PartsPerContainer serves no function in the system. To me it reads like it is meant to signify how many parts go in a box. We use this field for our finished goods mostly, for that exact purpose.
Its not a huge leap to go from how many in a box to how many in a BIN, but it feels like you are starting down the ânot using the field how it is intendedâ road again.
