I have a requirement to store exactly the same product in two units of measure (bag, and pallet). The scenario is that I will need to Manufacture some in 'bag' quantities and more in 'pallet' quantities (a pallet is 12 bags).
I would like to keep the same Item number and they will be stored in the same Location, ultimately I need to be able to look at inventory and determine that I have 24 pallets and 15 bags (24 X 12 + 15 = 303 bags).
Simple is best - any suggestions?
*This post is locked for comments
If it does not fit, you have to making a customization :(
Thank you Aleksandar: I understand that I could use WMS and directed PICK/PUTAWAY to track the alternate units; however that would apply all Items (approx 5,000) in the Location and that is a discipline I was trying to avoid. They only have one Product Line (approx 20 Items) where this requirement exists.
Thank you for your interest and suggestion.
I have not received a response fromyou about Breakbulk functionality. This is standard WMS functionality in NAV and I think, this can sole your problem.
NAV help quote:
Allow Breakbulk Field on The Location Table
A check mark in this field indicates that the program will meet the order with items stored in other units of measure, if it cannot find an item stored in the unit of measure that is requested on an outbound order.
The program first breaks a larger unit of measure of the item into smaller units of measure to meet the order. Here you are breaking the bulk unit of measure that the item is stored in.
If a pick line still needs items, the program suggests that you gather items in smaller units of measure to meet the order. Here you are breaking the bulk unit of measure on the sales, transfer or production order. For example, when the order requests a pallet, and the warehouse has only pieces, the program creates a pick for the number of pieces that correspond to a pallet.
This field can only be used when the location is set up to use directed put-away and pick.
...
Did you try Breakbulk functionality? It is possible to make you fit.
Hi
I think you have a nestandar solution.
First créate your ítem in Unit as Unit of measure
Later, you must créate two variants, one for bag and one for palet.
If you want to see the sotck in each unit of measure, you just must see stock by variant.
Do you like this solution?
Regards
Thank you. I guess I am looking at a mod - will review your code and try to scrape some ideas. Was really hoping to find some standard stone un-turned.
I understand, we had similar issues. We sell items either in pieces or Boxes. The box Qty can vary from item to item. So we wanted to know how many boxes of merchandise do we have. Similar to you. Since we only have two UOM per item it was controllable with some mod. If we had many different UOM it would have been messier.
First we needed to get the UOM quanitities from the Item Unit Of Measure Table.
So I create three new fields on the item table. All Flowfields.
1) Base UOM Qty
Calcformula: Lookup("Item Unit of Measure"."Qty. per Unit of Measure" WHERE (Item No.=FIELD(No.),Code=FIELD(Base Unit of Measure)))
2)Sales UOM Qty
CalcFormula:Lookup("Item Unit of Measure"."Qty. per Unit of Measure" WHERE (Item No.=FIELD(No.),Code=FIELD(Sales Unit of Measure)))
3)Purch UOM Qty
Lookup("Item Unit of Measure"."Qty. per Unit of Measure" WHERE (Item No.=FIELD(No.),Code=FIELD(Purch. Unit of Measure)))
Now I have a number on the item table (don't Forget Your CALCFIELDS) that I can use to divide my Qty by to give me my qty by sales uom. Which is the one we use 99.99% of the time. When a picker goes to the shelf he doesn;t need to know we have 144 pieces. He needs to know we have 12 boxes of 12 since we sell them in boxes only. So I created a "Warehouse" form that shows the qty's in the values they need to see. I calc'd the Qty
CALCFIELDS("Sales UOM Qty");
IF "Sales UOM Qty" = 0
THEN MESSAGE('Error On Item %1',"No.")
ELSE VisualQOH := Quantity / "Sales UOM Qty"; with Visual QOH as the SourceExp of my field.
Now if you wanted to make a field on the item card to calc this you will need a developers license. We use these UOM Qty's mostly on reports and it's a bit easier because we don't have to bring that info in from another table.
I don;t know if I really answered your question, but it sounds like you will need a mod. and for that you should contact your NAv partner for a quote. they know your needs better than us. Perhaps an addition to the "item statistics" that can show the breakdown you are looking for.
Thank you for the response!
I understand the alternate units of measure for selling and buying functionality; however, my issue is that the Item is stocked in both pallets and eaches – physically. I want to know what is in ‘pallets’ and what is ‘not on pallets’ loose – it means that if I get an order for 5 pallets – I can PICK from the pallet quantity without having to assemble a new pallet.
There is some functionality in Advance Warehouse and directed PICK/PUTAWAY for 'putaway unit of measure, but that is a discipline that would apply to all my Items and I am not ready to go there (yet). I was hoping for something with Variants or ??.
an item can have many units of measure.
It's best to set he base unit of measure as the smallest possible qty.
So I would ask is BAG the smallest it can be?
If yes then create a unit of measure "BAG" = 1
make that the "base uom"
then add another unit of measure "pallet" = 12
now depending on how it's usually sold & bought you can default the "sales uom" & "purchase uom" fields to the proper uom code
calculate all your costs & prices based on the "base uom"
so now when you enter a sales order for this item you can change the base uom to whichever you need and it will calculate correctly.
example/ if you enter that item as 12 bags and enter it again as 1 pallet - it should all calculate the same.
if someone wants a pallet and a half you can enter 1 line of 18 bags or 2 lines - 1 pallet & 6 bags
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,253 Super User 2024 Season 2
Martin Dráb 230,188 Most Valuable Professional
nmaenpaa 101,156