AllocPositionEffect (FIX tag 1047)

charFIX 5.0 SP2

AllocPositionEffect (tag 1047) is a char field defined in FIX 5.0 SP2. It appears in 5 message types, always optionally. It is an enumerated field with 4 defined values.

At a glance

Tag: 1047
Name: AllocPositionEffect
Datatype: char
Dialects: FIX 5.0 SP2
Messages: 5
Valid values: 4

What the specification says

Indicates whether the resulting position after a trade should be an opening position or closing position. Used for omnibus accounting - where accounts are held on a gross basis instead of being netted together.

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

A real message using tag 1047

AllocationInstruction · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	154
35	MsgType	J	AllocationInstruction
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
70	AllocID	EXAMPLE
71	AllocTransType	0	New
626	AllocType	1	Calculated (includes MiscFees and NetMoney)
54	Side	1	Buy
53	Quantity	1000000
75	TradeDate	20240101
78	NoAllocs2 entries	2	repeating group
79	AllocAccount	EXAMPLE
1047	AllocPositionEffect	O	Open
79	AllocAccount	EXAMPLE
1047	AllocPositionEffect	O	Open
10	CheckSum	227

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 5.0 SP2 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
O	Open	OPEN
C	Close	CLOSE
R	Rolled	ROLLED
F	FIFO	FIFO

Where tag 1047 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
AllocationInstruction	J	Optional	inside the AllocGrp component
AllocationInstructionAck	P	Optional	inside the AllocAckGrp component
AllocationInstructionAlert	BM	Optional	inside the AllocGrp component
AllocationReport	AS	Optional	inside the AllocGrp component
AllocationReportAck	AT	Optional	inside the AllocAckGrp 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 1047 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const allocPositionEffect = message.fields[1047]?.raw;// e.g. "O" — Open// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(1047)  ?.enumValues?.find((e) => e.value === allocPositionEffect)  ?.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-fix50sp2

Try the decoder Source on GitHub