Hello all,
I have a scenario where the end user procures fabric rolls in tonnes. The usual width of the roll is 10 meters however sometimes it comes to be around 9 meters or 11 meters. So even if they’re procuring in tonnes, how can we handle the variance in the dimension?
Since the fabric is to be used into production, how to account for the same.
Acumatica has no native catch-weight, so you can't model "1 tonne = X metres" when X changes with every roll. UOM conversions are fixed per item.
There’s two ways of handling this that I can think of. Not sure which way would make more sense for you and your setup.
If width affects yield (I imagine it does?), stock the item in the unit production actually consumes - linear metres or m², and NOT weight. Make the base/inventory UOM metres (or m²), keep Tonne as the purchasing UOM with a nominal conversion just so the PO reads sensibly, and then correct the received quantity to the measured actuals at goods receipt. A 9 m vs 11 m roll simply lands as a different m² figure, so the dimension variance becomes a quantity variance, which is exactly what your BOM and production order care about. Costing then values per metre/m². The trade-off is the AP bill comes in tonnes, so you accept a nominal conversion on the PO line and let the receipt carry the real number.
The second way I can think of is if you just need traceability of which roll had which dimensions. You’d just keep weight as the base UOM, and turn on lot tracking, and capture the actual width and length against the lot. Lots can have attributes in later editions of Acumatica so you might be able to do something with this?
For fabric going into production I'd lean towards the first option as modelling it by area is more honest about how much material you've actually got, and it stops a heavy-but-narrow roll from looking like more fabric than it is.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
