LastFragment (FIX tag 893)

BooleanFIX 4.4FIX 5.0 SP2

LastFragment (tag 893) is a Boolean field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 10 message types, always optionally. It is an enumerated field with 2 defined values.

At a glance

Tag: 893
Name: LastFragment
Datatype: Boolean (char)
Dialects: FIX 4.4 and FIX 5.0 SP2
Messages: 10
Valid values: 2

What the specification says

Indicates whether this message is the last in a sequence of messages for those messages that support fragmentation, such as Allocation Instruction, Mass Quote, Security List, Derivative Security List

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

A real message using tag 893

NewOrderList · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	119
35	MsgType	E	Order – List
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
66	ListID	EXAMPLE
394	BidType	1	"Non Disclosed" Style (e.g. US/European)
68	TotNoOrders	1
893	LastFragment	N	Not last message
73	NoOrders1 entry	1	repeating group
11	ClOrdID	ORD-10042
67	ListSeqNo	1
54	Side	1	Buy
10	CheckSum	253

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	Last message	YES / LAST_MESSAGE
N	Not last message	NO / NOT_LAST_MESSAGE

Where tag 893 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
AllocationInstruction	J	Optional	Optional	directly on the message body
AllocationInstructionAlert	BM	—	Optional	directly on the message body
AllocationReport	AS	Optional	Optional	directly on the message body
DerivativeSecurityList	AA	Optional	Optional	directly on the message body
DerivativeSecurityListUpdateReport	BR	—	Optional	directly on the message body
ExecutionReport	8	—	Optional	directly on the message body
ListStatus	N	Optional	Optional	directly on the message body
ListStrikePrice	m	Optional	Optional	directly on the message body
MassQuote	i	Optional	Optional	inside the QuotSetGrp component
MassQuoteAcknowledgement	b	Optional	Optional	inside the QuotSetAckGrp component
NewOrderList	E	Optional	Optional	directly on the message body
SecurityList	y	Optional	Optional	directly on the message body
SecurityListUpdateReport	BK	—	Optional	directly on the message body
SecurityTypes	w	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 893 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 lastFragment = message.fields[893]?.raw;// e.g. "Y" — Last message// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(893)  ?.enumValues?.find((e) => e.value === lastFragment)  ?.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