DiscretionScope (FIX tag 846)

intFIX 4.4

DiscretionScope (tag 846) is an int field defined in FIX 4.4. It appears in 8 message types, always optionally. It is an enumerated field with 4 defined values.

At a glance

Tag
846
Name
DiscretionScope
Datatype
int
Dialects
FIX 4.4
Messages
8
Valid values
4

What the specification says

The scope of the discretion

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

A real message using tag 846

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength117
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
846DiscretionScope1Local (Exchange, ECN, ATS)
10CheckSum007
Edit and decode it yourself

Shown with | separators for readability. On the wire FIX uses SOH (0x01), an invisible control byte — and because BodyLength and CheckSum are computed over the actual bytes, the two forms have different checksums. Both are valid and both decode here.

Open in the full decoder →

Generated from the FIX 4.4 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

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.

ValueMeaningSymbolic name
1Local (Exchange, ECN, ATS)LOCAL
2NationalNATIONAL
3GlobalGLOBAL
4National excluding localNATIONAL_EXCLUDING_LOCAL

Where tag 846 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.

MessageMsgTypeRequirednessWhere in the message
CrossOrderCancelReplaceRequesttOptionalinside the DiscretionInstructions component
ExecutionReport8Optionalinside the DiscretionInstructions component
MultilegOrderCancelReplaceACOptionalinside the DiscretionInstructions component
NewOrderCrosssOptionalinside the DiscretionInstructions component
NewOrderListEOptionalinside ListOrdGrp › DiscretionInstructions
NewOrderMultilegABOptionalinside the DiscretionInstructions component
NewOrderSingleDOptionalinside the DiscretionInstructions component
OrderCancelReplaceRequestGOptionalinside the DiscretionInstructions component

Wire format

A whole number, optionally signed. Leading zeros are legal on the wire and are preserved in the raw value. @boarteam/fix parses the value as a number and reports parse/invalid-int when it does not lex as one; the raw string is kept either way.

Read tag 846 in TypeScript

decode.tsts
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const discretionScope = message.fields[846]?.raw;// e.g. "1" — Local (Exchange, ECN, ATS)// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(846)  ?.enumValues?.find((e) => e.value === discretionScope)  ?.description;

Other int fields

Decode this in your own code

The same engine that produced the decoded example above is an Apache-2.0 npm package with zero runtime dependencies. It runs in Node and in the browser, and parse() returns problems as data instead of throwing.

npm i @boarteam/fix @boarteam/fix-dict-fix44