Resources & Cost
Units of Measure Label Material, Not Labor Time
UMEASURE labels material; labor/nonlabor units are time
What a planner means
A unit of measure is the label on a material resource (tons, m³, EA, box). Oracle API: labor and nonlabor units are time. Material units come from the UnitOfMeasure dictionary.
Professional: a unit of measure “describes the quantity of a particular resource.” Labor is hours or days; materials can be cubic/linear feet, tons, kilos; each-items can be EA, box, case, pallet. Money is a currency, not this dictionary.
EPPM: create Unit Abbreviation + Unit Name under Enterprise Data / Resources / Units of Measure, then assign the unit to a material resource (RSRC.unit_id).
Help also says you can change units in a project to change how graphs and spreadsheets depict materials, and that abbreviations are used for conversions. Do not invent a conversion table; Oracle does not publish the formula on the cited pages.
PROJCOST.qty_name is labeled Unit of Measure on an expense. That is a string on the expense row, not UMEASURE.unit_id.
XER
UMEASURE (Units of Measure):
| Column | Oracle label |
|---|---|
unit_id | Unique ID |
unit_name | Unit Name |
unit_abbrev | Unit Abbreviation |
seq_num | Sort Order |
RSRC.unit_id is Unit of Measure. No TASK unit-of-measure column on the project map.
Microsoft Project
MSP material resources have a Material Label (yards, tons). That is a string on the resource, not a shared UMEASURE dictionary. Do not map unit_id to Work or to Duration.
Don't
- Treat UMEASURE as labor/nonlabor time or as a currency.
- Put
unit_idon TASK. - Treat
PROJCOST.qty_nameasUMEASURE.unit_id. - Invent abbreviation conversion math.
- Map UMEASURE to MSP Work.