Form: INVSDUOM.fmb
Table: MTL_UNITS_OF_MEASURE
MTL_UNITS_OF_MEASURE is the definition table for both the 25-character and the 3-character units of measure.
The base_uom_flag indicates if the unit of measure is the primary unit of measure for the uom_class.
Oracle Inventory uses this table keep track of the units of measure than can be used to transact an item. This table is also used by Oracle Purchasing, and Oracle Order Entry/Shipping.
Each Transaction involves three units of measure -
§ Transaction UOM
§ Primary UOM
§ Secondary UOM
It should be clarified that although there could be three units of measures on a transaction, the onhand quantity is always stored in the primary UoM.
o The simplest case of UOM Conversion in Transactions is - All the Three UOMs belong to the same UOM Class (assume that none of them are base UOM). This case requires three conversions -
1. Convert Transaction UOM to Base UOM
2. Convert Base UOM to Primary UOM
3. Convert Base UOM to Secondary UOM
o Most Complex Case of UOM Conversion in Transactions is- Each of the Three UOMs belong to different UOM Classes –
For such a case, it requires five conversions -
1. Convert Transaction UOM in Class T to Base UOMin Class T
2. Convert Base UOM in Class T to Base UOM in ClassP
3. Convert Base UOM in Class P to Primary UOM inClass P (this gives Primary UOM)
4. Convert Base UOM in Class P to Base UOM in Base UOM in Class S
5. ConvertBase UOM in Class S to Secondary UOM inClass S (this gives Secondary UOM)
From the Two cases, it is evident that a conversion from Transaction UOM to Secondary UOM requires a minimum of two conversions (in simplest case)to a maximum of 4 conversions (in complex case) and after each conversion, the result might potentially be rounded to inventory rounding (5 digits).