UnitOfMeasure (FIX tag 996)

At a glance

Tag

996

Name

UnitOfMeasure

Datatype

String

Dialects

FIX 5.0 SP2

Messages

72

Valid values

13

What the specification says

The unit of measure of the underlying commodity upon which the contract is based. Two groups of units of measure enumerations are supported.

Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.

A real message using tag 996

Valid values

A value outside this list is not a parse error — the message still decodes — but validate() reports it as validate/value-not-in-enum.

Where tag 996 appears

Requiredness is a property of the message, not of the field: the same tag can be optional in one message and conditionally required in another.

Wire format

Free-form text. Any byte except the SOH separator is legal, so values are not trimmed or case-folded on the wire. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 996 in TypeScript

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";​const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);​const unitOfMeasure = message.fields[996]?.raw;// e.g. "Bbl" — Barrels​// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(996)  ?.enumValues?.find((e) => e.value === unitOfMeasure)  ?.description;

Other String fields

• 997TimeUnit
• 994TierCode
• 998UnderlyingUnitOfMeasure
• 993AllocCustomerCapacity
• 999LegUnitOfMeasure
• 1000UnderlyingTimeUnit
• 1001LegTimeUnit
• 990LegReportID
• 989SecondaryIndividualAllocID
• 1003TradeID
• 988UnderlyingSettlementStatus
• 1005SideTradeReportID
• 1006SideFillStationCd
• 1007SideReasonCd
• 1011MessageEventSource
• 979InputSource
• 1014SideTrdRegTimestampSrc
• 977ContIntRptID
• 974UnderlyingCashType
• 1019InstrumentPartyID
• 1022MDFeedType
• 966SettleOnOpenFlag
• 965SecurityStatus
• 1030ReceivedDeptID