Yes, that is the way the system is designed.
You just have to make sure it physically makes sense.
Generally you should store in the smallest unit you issue. If you batch /serial control then a unit like piece or case makes more sense than kg or m.
AX offers three different conversions:
Standard Conversions – Define the conversion between two units, applicable against all products. Such conversion can be defined only within the units belong to same Unit class. e.g. hour to minutes, kg to gm or sqfeet to sqinches, even ton to kg or m to in - they are the same physical dimension of length and the conversion value does not change
Intra and Inter offer product specific Unit conversions, and that’s what it makes those more special.
Intra-Class Conversions – Here we can define product specific conversion. Once conversion defined here between two units, it is applicable only to that product. Like standard conversion, units should belong to same Unit class for conversion. E.g. Case to boxes and boxes to EA (the number of boxes will be item specific
Inter-Class Conversions – Conversion can be defined between two units belong to different Unit class. Once conversion defined here between two units, it is applicable only to that product. e.g. Litre to kg here we are crossing physical (class) dimensions and there re product specific differences e.g. density
To define unit conversion, navigate to Organization administration –> Setup –> Units
Use the Unit creation wizard to create standard units quickly.
Choose appropriate decimal precision.
AX only requires that a conversion exist in one direction. In other words, the user can define the conversion from SqFt to ea OR ea to SqFt. Ax odes not enforce this. The problem with setting up the conversion in both directions is more than just the redundancy of the input—the user opens up the risk that the conversions won’t be consistent. If the conversions are inconsistent, it will affect that way AX rounds in that AX will first look for the directly applicable conversion, before then going to the inverse conversion
Lachlan has some videos that may help https://organicax.com/2016/04/29/basic-inventory-unit-setup-for-an-item/
When you have no UoM conversions yet defined then OK to add, but if you have transactions, and then alter the conversion logic then you risk problems.
Be aware of this hotfix re production bom reset and uom kb.3095935
