RootPartyIDSource (FIX tag 1118)

charFIX 5.0 SP2

RootPartyIDSource (tag 1118) is a char field defined in FIX 5.0 SP2. It appears in 8 message types, always optionally.

At a glance

Tag
1118
Name
RootPartyIDSource
Datatype
char
Dialects
FIX 5.0 SP2
Messages
8

What the specification says

PartyIDSource value within a root parties component. Same values as PartyIDSource (447)

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

A real message using tag 1118

QuoteRequest · FIX 5.0 SP2
TagFieldWire valueMeaning
8BeginStringFIXT.1.1
9BodyLength139
35MsgTypeRQuoteRequest
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
131QuoteReqIDEXAMPLE
1116NoRootPartyIDs2 entries2repeating group
1117RootPartyIDEXAMPLE
1118RootPartyIDSource1
1117RootPartyIDEXAMPLE
1118RootPartyIDSource1
146NoRelatedSym1 entry1repeating group
55SymbolEUR/USD
10CheckSum191
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 5.0 SP2 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Where tag 1118 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 RootParties component
CrossOrderCancelRequestuOptionalinside the RootParties component
NewOrderCrosssOptionalinside the RootParties component
NewOrderListEOptionalinside the RootParties component
QuoteRequestROptionalinside the RootParties component
QuoteRequestRejectAGOptionalinside the RootParties component
TradeCaptureReportAEOptionalinside the RootParties component
TradeCaptureReportAckAROptionalinside the RootParties component

Wire format

A single character. Most char fields are enumerated, so the value is one of a fixed set rather than arbitrary text. @boarteam/fix keeps the value as a string and, for enumerated fields, reports validate/value-not-in-enum when it is not a defined value.

Read tag 1118 in TypeScript

decode.tsts
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[1118];field?.name;   // "RootPartyIDSource"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

Other char 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-fix50sp2