ForexReq (FIX tag 121)

BooleanFIX 4.4FIX 4.2

ForexReq (tag 121) is a Boolean field defined in FIX 4.4 and FIX 4.2. It appears in 8 message types, always optionally. It is an enumerated field with 2 defined values.

At a glance

Tag: 121
Name: ForexReq
Datatype: Boolean (char)
Dialects: FIX 4.4 and FIX 4.2
Messages: 8
Valid values: 2

What the specification says

Indicates request for forex accommodation trade to be executed along with security transaction.

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

A real message using tag 121

NewOrderSingle · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	117
35	MsgType	D	Order – Single
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
11	ClOrdID	ORD-10042
54	Side	1	Buy
60	TransactTime	20240101-12:00:00.000
40	OrdType	1	Market
121	ForexReq	N	Do not execute Forex after security trade
10	CheckSum	022

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
Y	Execute Forex after security trade	YES / ExecuteForexAfterSecurityTrade
N	Do not execute Forex after security trade	NO / DoNotExecuteForexAfterSecurityTrade

Where tag 121 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	Where in the message
BidRequest	k	Optional	Optional	directly on the message body
CrossOrderCancelReplaceRequest	t	Optional	—	inside the SideCrossOrdModGrp component
MultilegOrderCancelReplace	AC	Optional	—	directly on the message body
NewOrderCross	s	Optional	—	inside the SideCrossOrdModGrp component
NewOrderList	E	Optional	Optional	inside the ListOrdGrp component
NewOrderMultileg	AB	Optional	—	directly on the message body
NewOrderSingle	D	Optional	Optional	directly on the message body
OrderCancelReplaceRequest	G	Optional	Optional	directly on the message body

Wire format

Y or N. Not 1/0, and not true/false. @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 121 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 forexReq = message.fields[121]?.raw;// e.g. "Y" — Execute Forex after security trade// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(121)  ?.enumValues?.find((e) => e.value === forexReq)  ?.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