Solved

Base UOM needs to be smallest UOM?

L
Rank

We recently found a variance between the LOT numbers  that our material transactions were set to consume vs the LOT number our issue transaction were consuming. The quantity of each product deducted was the same, but the LOT it was using was different between the two transactions.

We escalated this issue to Acumatica and they came back and told us that we needed to switch our base UOM to the smallest unit of measure that we use. Currently our base unit is in LBS and we have a UOM conversion into grams and into kilograms.

Moving all of our inventory from being stocked in LBS to being stocked in grams is going to be a major change to our processes and take a lot of time to fix a problem that was working fine for us for over 6 months. Does anyone have any ideas in how to fix this issue with changing the UOM’s?

icon

Best answer by bryanb39 9 July 2022, 01:21

View original

3 replies

bryanb39
Rank
Userlevel 6
Badge +5

That sounds like a weird response.  Not using the smallest unit of measure can result in variances in quantity you expected to consume vs what was issued, but using a different lot because of the UOM doesn’t make much sense.  Could there have been a miscommunication with the ticket escalation?

I’d for you to undertake that process and then find out it doesn’t fix it. I’ve mapped that specific process out for someone, Lbs to Grams, it’s a pain.  

https://www.fiverr.com/acudatica
R
Rank
Userlevel 6
Badge +5

It may make sense if the system is rounding automatically as part of the issue transaction. If the error due to the tablemaker’s dilemma is high, then the system may take more or less product than predicted if the rounding only occurs on issue (and therefore overflows into a different lot). You can reduce rounding effects in some cases by increasing the decimal precision of the quantity and UOM fields for the company I think (don’t just do this though… it needs testing).

It’s also possible you could compensate for the problem with customization.

The fundamental issue is the “tablemakers dilemma”.

https://en.m.wikipedia.org/wiki/Rounding#Table-maker's_dilemma

This is why the base UOM should be the lowest common divisor. It reduces the error from the effects  of division because in most cases the lowest common UOM will divide into an integer value, and where it doesn’t the effects of rounding will be minimized.

Kerp in mind…. You need the lowest common UOM on a per product basis. So depending on the conversions, it may not always be the same UOM.

 

 

Chris Hackett
Rank
Userlevel 7
Badge

Hi @lpenrod  - were you able to find a solution for your issue? Thank you!

Chris ~ Let us know how we're doing: https://forms.office.com/r/xmJUdZ1QE5 - A member helped you, please *Like* their post. A member provided an answer to your question, please mark it as *Best Answer*.

Reply


Terms & ConditionsCookie settings
About Acumatica ERP system
Acumatica Cloud ERP provides the best business management solution for transforming your company to thrive in the new digital economy. Built on a future-proof platform with open architecture for rapid integrations, scalability, and ease of use, Acumatica delivers unparalleled value to small and midmarket organizations. Connected Business. Delivered.
© 2008 — 2024  Acumatica, Inc. All rights reserved