Multiple UOM Setup

Daniel,
Here is how we would set it up in our build...

Stock UOM: EA (EACH)
UOM Conv Factor Alt UOM Tracked Trans Sell Sell Price Buy
EA(EACH) 1.0000 X 1 2 2 1
CA(CASE) 36.0000 X 2 1 1 2

Not terribly difficult. One difference between builds would be whether or not you want to use the "2" values or just leave them blank. The "2" allows the activity in that UOM, while I believe a blank precludes it altogether. Also, I am not sure if you are using the PO Module, as the Vendor Agreement Line (PO25.6) can be used to default the Buy UOM.

Good luck,
Red

(Sorry, the formatting is not allowing the text above to replicate the UOM Tab of the IC11.  If you need a little clarification, let me know)

Red,
Thanks for the info, have not been able to configure the UOM yet as IC11 keeps giving the message that "quantities exist at location(s)", we only have one location which is our warehouse. We adjusted stock on hand to zero, now I think it is the quantitiy on order that is preventing us from testing the solution. I also had to remove the UOM from IC12 before I could make any changes to IC11. We are working on  canceling the items on order and then will try again.

Thanks for the info

Red, the set-up you suggested did not work exactly how we wanted, when the warehouse did a receipt of an order of 72 lightbulbs the on-hand stock still shows 72, this is where the warehouse wants it to show 2 cases on-hand not 72. While you conversion set-up did prevent the on-hand amount from being mulitplied out it did not convert the on-hand as cases. Maybe the UOM on the item should be "Case"  instead of each?

thanks for the help.

Daniel,

If you only issue the lightbulbs by the CASE, then, yes, I would suggest you build the item with CASE as the sole UOM.  However, if you issue the lightbulbs out to departments, I do not think they wuold want a CASE at a time; in which case you will need to build the lower UOM.

Sorry I was not clear about that before,
Red

Red, these are school buildings ordering from our warehouse so they order by the case for the whole building. I think if I set the stock UOM on the item to Case and leave the conversions you gave me in place that it might work then, I will give that a try.

Thanks

FYI. The UOM routine for IC is the token ICI1
You can run scenarios in ICI1 to see how they play out.

Daniel,
Red is correct in that when setting up an item you need only go to the lowest logical UOM.  In your example, since the vendor will only transact in EA, you are pretty much forced to setup eaches.  When building the conversion factor the system will only accept the lowest UOM as the Stock UOM.  You may have to consider a process/cultural change for your distribution folks.  You can setup the items in question in IC12 Item Location to only issue out in Cases of 36.  I would also suggest setting up your replenishments to also only purchase in increments of 36 so that you don't end up with partial cases on your shelves.
I hope this helps,
Ed

We are set up as a low unit area...we recieve by the each and can transact by the box, case whatever. Do you use PAR locations (stock rooms) You could set up the pars in IC82 by the box unit as long as it is a recongnized uom. You can also set up IC12 under the reorder tab to reflect the uom that you want to have as a transaction default. Agree also with EdB, educate staff to order in multiples of 36

Red,

I have a follow-up question in regards to the UOM conversions.
Can the UOM "levels" be set up at the "each" level for all items, even if we do not ever purchase or issue at the each level?  We would like to have all the items set up that way to be able to leverage the conversion factors in the Lawson tables in order to obtain costs at the each level.

Please let me know your thoughts.  Thanks

If you are ever to do any interfacing with a Cerner system, setting up at "the lowest possible UOM" is required. So, yes, you can set it up even if you never purchase or issue at that level.

Bman, the answer is "yes." Going back to the lightbulb example above... In our build, we would build the Each (EA) and the Case (CA) of 36, setting the EA as the "Stock UOM." Even if you buy by the CA and issue/distribute by the CA, the SOH quantities are displayed in the EA amounts when you drill into the item location. I cannot see that I said it above, but when I was explaining the UOM build at the begining of an implementation I would say that the Stock UOM is the UOM Lawson is always thinking in, regardless of the UOM you (as the human user) are thinking in. Lawson is happy to issue a CA of 36 for you, but it is moving 36 EA in the background. Additionally, some transactions and activities require that you shift to the Stock UOM, at least initially (i.e., performing cycle counts and physical inventories and adjustments).

Going to what Greg M. was stating, we have seen a lot of other applications (Picis, Pyxis, OmniCell) require lower UOMs than we would normally have built, primarily based on the "issue" or "use" UOM. So, we have built Each (EA) Band-Aid (tm) because that is what they issue to the patient. That gets filed under "necessary evil".

Good luck,
Red

I'm sure this is an old trail and you've figured this out by now...but for others that may find this useful:

In order to change the UOM on a IC11.1 file, the UOM will need to be removed from the IC12 Default UOM field, Any IC82 records, PO45 Records, PO20, PO25.6 or IC trans documents.  Basically there needs to be no trail of the UOM that is being modified.  These changes are most difficult when the item was built without the lowest UOM...but now needs to be added. 

If this will be a mass change to multiple IC11.1 files,  it may be a good idea to create a crystal report to pull all these fields in that relate to this master file item so that the user modifying the file knows where the items reside rather then accessing all of the screens above to be sure the change will be completed.