CollAsgnRejectReason (FIX tag 906)
CollAsgnRejectReason (tag 906) is an int field defined in FIX 4.4. It appears in 1 message type, always optionally. It is an enumerated field with 7 defined values.
At a glance
- Tag
- 906
- Name
- CollAsgnRejectReason
- Datatype
- int
- Dialects
- FIX 4.4
- Messages
- 1
- Valid values
- 7
What the specification says
Collateral Assignment Reject Reason
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 906
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 131 | |
| 35 | MsgType | AZ | Collateral Response |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 904 | CollRespID | EXAMPLE | |
| 902 | CollAsgnID | EXAMPLE | |
| 895 | CollAsgnReason | 0 | Initial |
| 905 | CollAsgnRespType | 0 | Received |
| 906 | CollAsgnRejectReason | 0 | Unknown deal (order / trade) |
| 60 | TransactTime | 20240101-12:00:00.000 | |
| 10 | CheckSum | 238 |
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.
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.
| Value | Meaning | Symbolic name |
|---|---|---|
| 0 | Unknown deal (order / trade) | UNKNOWN_DEAL |
| 1 | Unknown or invalid instrument | UNKNOWN_OR_INVALID_INSTRUMENT |
| 2 | Unauthorized transaction | UNAUTHORIZED_TRANSACTION |
| 3 | Insufficient collateral | INSUFFICIENT_COLLATERAL |
| 4 | Invalid type of collateral | INVALID_TYPE_OF_COLLATERAL |
| 5 | Excessive substitution | EXCESSIVE_SUBSTITUTION |
| 99 | Other | OTHER |
Where tag 906 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.
| Message | MsgType | Requiredness | Where in the message |
|---|---|---|---|
| CollateralResponse | AZ | Optional | directly on the message body |
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 906 in TypeScript
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const collAsgnRejectReason = message.fields[906]?.raw;// e.g. "0" — Unknown deal (order / trade)// The dictionary also carries the labels:const label = fix.dictionary .fieldByTag(906) ?.enumValues?.find((e) => e.value === collAsgnRejectReason) ?.description;Other int fields
- 905CollAsgnRespType
- 903CollAsgnTransType
- 910CollStatus
- 911TotNumReports
- 896CollInquiryQualifier
- 895CollAsgnReason
- 919DeliveryType
- 892TotNoAllocs
- 891MiscFeeBasis
- 924UserRequestType
- 926UserStatus
- 928StatusValue
- 935NetworkRequestType
- 875CPProgram
- 937NetworkStatusResponseType
- 939TrdRptStatus
- 940AffirmStatus
- 871InstrAttribType
- 944CollAction
- 945CollInquiryStatus
- 946CollInquiryResult
- 865EventType
- 951Nested3PartyRole
- 954Nested3PartySubIDType
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