AllocCancReplaceReason (FIX tag 796)

intFIX 4.4

AllocCancReplaceReason (tag 796) is an int field defined in FIX 4.4. It appears in 2 message types, always optionally. It is an enumerated field with 3 defined values.

At a glance

Tag: 796
Name: AllocCancReplaceReason
Datatype: int
Dialects: FIX 4.4
Messages: 2
Valid values: 3

What the specification says

Reason for cancelling or replacing an Allocation Instruction or Allocation Report message

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

A real message using tag 796

AllocationInstruction · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	135
35	MsgType	J	Allocation Instruction
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)
796	AllocCancReplaceReason	1	Original details incomplete/incorrect
857	AllocNoOrdersType	0	Not specified
54	Side	1	Buy
53	Quantity	1000000
6	AvgPx	1.09215
75	TradeDate	20240101
10	CheckSum	138

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
1	Original details incomplete/incorrect	ORIGINAL_DETAILS_INCOMPLETE_INCORRECT
2	Change in underlying order details	CHANGE_IN_UNDERLYING_ORDER_DETAILS
99	Other	OTHER

Where tag 796 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	Conditional	directly on the message body
AllocationReport	AS	Conditional	directly on the message body

Wire format

A whole number, optionally signed. Leading zeros are legal on the wire and are preserved in the raw value. @boarteam/fix parses the value as a number and reports parse/invalid-int when it does not lex as one; the raw string is kept either way.

Read tag 796 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 allocCancReplaceReason = message.fields[796]?.raw;// e.g. "1" — Original details incomplete/incorrect// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(796)  ?.enumValues?.find((e) => e.value === allocCancReplaceReason)  ?.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