Resources in Microsoft Dynamics NAV have one Base Unit of Measure. But we can post resources usage in more different Unit of Measures, the similar as Item posting. This is often necessary when we have complex projects and e.g. sometimes make usage for the same resource in HOURS and sometimes in M3 or KILOMETERS… Unlike Items must to have number of units the Code represents compared to the unit of measure code we have entered in the Base Unit of Measure field, for Resources this relationship between different Unit of Measure is not necessary.
If we want set different Unit of Measure codes for resources, that we can do using Resource Unit of Measure card. We can set Unit of Measures as much as we want. If we have relation between Base Unit of Measures and additional, we need to mark field ‘Related to Base Unit of Meas.’ and fill field ‘Qty. per Unit of Measure’. This field contains the number of units the Code represents compared to the unit of measure code we have entered in the ‘Base Unit of Measure’ field on the resource card. We can enter a decimal number greater than or smaller than 1.
If, for example, the base unit of measure is HOUR, and the code is DAY, we need to enter 8 in this field. However, if the base unit is DAY and we want to be able to sell a single hour, we need to enter 1/8 in this field. (NAV will automatically converts this to 0.125). When we set up in this way, we can post resources usage in different Unit of Measures, but we will have a small problem. Cost and price for this resources will be the same as for the Base Unit of Measures.
We can use more Unit of Measure on Resource Journal or Job Journal with specific cost and price per each Unit of Measure if we fill Work Type Code. This code enable us to use different cost and/or price per each Unit of Measure.
We can set Work Type Codes in different Unit of Measure as much as we want. We can set up resources Costs and Prices per each Work Type from resource card using command Prices->Cost (for costs) and Prices->Prices (for prices). For each Work Type Code (with different UOM), we can set adequate cost and price.
When we fill data for posting in Resource Journal or Job Journal, when we choose Work Type Codes (if we previously configure desired UOM from Work Type Codes on UOM card on Resource card), NAV will fill Unit Cost and Unit Price from these setups.
When we post these journals, we will correctly Quantity, Total Cost and Total Price. But, we will get calculated quantity in Base Unit of Measure, if we use Work Type with relationship between base and additional UOM. If we do not use relationship between base and additional UOM, this filed will be represent 0 value. This enable us to make complex analysis about resource usage.
