LegPositionEffect (FIX tag 564)

charFIX 4.4

LegPositionEffect (tag 564) is a char field defined in FIX 4.4. It appears in 5 message types, always optionally.

At a glance

Tag: 564
Name: LegPositionEffect
Datatype: char
Dialects: FIX 4.4
Messages: 5

What the specification says

PositionEffect for leg of a multileg See PositionEffect (77) field for description

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

A real message using tag 564

ExecutionReport · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	175
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
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
555	NoLegs2 entries	2	repeating group
600	LegSymbol	EXAMPLE
564	LegPositionEffect	1
600	LegSymbol	EXAMPLE
564	LegPositionEffect	1
10	CheckSum	010

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 564 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	Requiredness	Where in the message
ExecutionReport	8	Optional	inside the InstrmtLegExecGrp component
MultilegOrderCancelReplace	AC	Optional	inside the LegOrdGrp component
NewOrderMultileg	AB	Optional	inside the LegOrdGrp component
TradeCaptureReport	AE	Optional	inside the TrdInstrmtLegGrp component
TradeCaptureReportAck	AR	Optional	inside the TrdInstrmtLegGrp 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 564 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[564];field?.name;   // "LegPositionEffect"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