SecondaryOrderID (FIX tag 198)

StringFIX 4.4FIX 4.2FIX 5.0 SP2

SecondaryOrderID (tag 198) is a String field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. It appears in 15 message types, always optionally.

At a glance

Tag: 198
Name: SecondaryOrderID
Datatype: String
Dialects: FIX 4.4, FIX 4.2 and FIX 5.0 SP2
Messages: 15

What the specification says

FIX 4.4

Assigned by the party which accepts the order. Can be used to provide the OrderID (37) used by an exchange or executing system.

FIX 4.2

Assigned by the party which accepts the order. Can be used to provide the OrderID used by an exchange or executing system.

FIX 5.0 SP2

Assigned by the party which accepts the order. Can be used to provide the OrderID (37) used by an exchange or executing system.

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

A real message using tag 198

ExecutionReport · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	145
35	MsgType	8	Execution Report
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
37	OrderID	ORD-10042
198	SecondaryOrderID	EXAMPLE
17	ExecID	EXEC-88117
150	ExecType	0	New
39	OrdStatus	0	New
54	Side	1	Buy
151	LeavesQty	0
14	CumQty	1000000
6	AvgPx	1.09215
10	CheckSum	008

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.

Where tag 198 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	FIX 4.4	FIX 4.2	FIX 5.0 SP2	Where in the message
AllocationInstruction	J	Optional	Optional	Optional	inside the OrdAllocGrp component
AllocationInstructionAlert	BM	—	—	Optional	inside the OrdAllocGrp component
AllocationReport	AS	Optional	—	Optional	inside the OrdAllocGrp component
CollateralAssignment	AY	Optional	—	Optional	directly on the message body
CollateralInquiry	BB	Optional	—	Optional	directly on the message body
CollateralInquiryAck	BG	Optional	—	Optional	directly on the message body
CollateralReport	BA	Optional	—	Optional	directly on the message body
CollateralRequest	AX	Optional	—	Optional	directly on the message body
CollateralResponse	AZ	Optional	—	Optional	directly on the message body
Confirmation	AK	Optional	—	Optional	inside the OrdAllocGrp component
ConfirmationRequest	BH	Optional	—	Optional	inside the OrdAllocGrp component
DontKnowTrade	Q	Optional	—	Optional	directly on the message body
ExecutionAcknowledgement	BN	—	—	Optional	directly on the message body
ExecutionReport	8	Optional	Optional	Optional	directly on the message body
MarketDataIncrementalRefresh	X	—	—	Optional	inside the MDIncGrp component
MarketDataSnapshotFullRefresh	W	—	—	Optional	inside the MDFullGrp component
OrderCancelReject	9	Optional	Optional	Optional	directly on the message body
OrderMassCancelReport	r	Optional	—	Optional	directly on the message body
TradeCaptureReport	AE	Optional	—	Optional	inside the TrdCapRptSideGrp component
TradeCaptureReportAck	AR	—	—	Optional	inside TrdCapRptAckSideGrp › TradeReportOrderDetail

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 198 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 field = message.fields[198];field?.name;   // "SecondaryOrderID"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

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