LastRptRequested (FIX tag 912)

BooleanFIX 4.4FIX 5.0 SP2

LastRptRequested (tag 912) is a Boolean field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 4 message types, always optionally.

At a glance

Tag: 912
Name: LastRptRequested
Datatype: Boolean (char)
Dialects: FIX 4.4 and FIX 5.0 SP2
Messages: 4

What the specification says

FIX 4.4

Indicates whether this message is that last report message in response to a request, such as Order Mass Status Request.

FIX 5.0 SP2

Indicates whether this message is the last report message in response to a request message, e.g. OrderMassStatusRequest(35=AF), TradeCaptureReportRequest(35=AD).

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

A real message using tag 912

ExecutionReport · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	139
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
912	LastRptRequested	N
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	071

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 912 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 5.0 SP2	Where in the message
AssignmentReport	AW	Optional	Optional	directly on the message body
CollateralReport	BA	Optional	Optional	directly on the message body
ExecutionReport	8	Optional	Optional	directly on the message body
TradeCaptureReport	AE	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 912 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[912];field?.name;   // "LastRptRequested"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a boolean

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