CollInquiryResult (FIX tag 946)

intFIX 4.4

CollInquiryResult (tag 946) is an int field defined in FIX 4.4. It appears in 1 message type, always optionally. It is an enumerated field with 11 defined values.

At a glance

Tag: 946
Name: CollInquiryResult
Datatype: int
Dialects: FIX 4.4
Messages: 1
Valid values: 11

What the specification says

Result returned in response to Collateral Inquiry 4000+ Reserved and available for bi-laterally agreed upon user-defined values

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

A real message using tag 946

CollateralInquiryAck · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	88
35	MsgType	BG	Collateral Inquiry Ack
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
909	CollInquiryID	EXAMPLE
945	CollInquiryStatus	0	Accepted
946	CollInquiryResult	0	Successful (Default)
10	CheckSum	027

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.

Value	Meaning	Symbolic name
0	Successful (Default)	SUCCESSFUL
1	Invalid or unknown instrument	INVALID_OR_UNKNOWN_INSTRUMENT
2	Invalid or unknown collateral type	INVALID_OR_UNKNOWN_COLLATERAL_TYPE
3	Invalid parties	INVALID_PARTIES
4	Invalid Transport Type requested	INVALID_TRANSPORT_TYPE_REQUESTED
5	Invalid Destination requested	INVALID_DESTINATION_REQUESTED
6	No collateral found for the trade specified	NO_COLLATERAL_FOUND_FOR_THE_TRADE_SPECIFIED
7	No collateral found for the order specified	NO_COLLATERAL_FOUND_FOR_THE_ORDER_SPECIFIED
8	Collateral Inquiry type not supported	COLLATERAL_INQUIRY_TYPE_NOT_SUPPORTED
9	Unauthorized for collateral inquiry	UNAUTHORIZED_FOR_COLLATERAL_INQUIRY
99	Other (further information in Text (58) field)	OTHER

Where tag 946 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
CollateralInquiryAck	BG	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 946 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 collInquiryResult = message.fields[946]?.raw;// e.g. "0" — Successful (Default)// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(946)  ?.enumValues?.find((e) => e.value === collInquiryResult)  ?.description;

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

Try the decoder Source on GitHub