PosMaintAction (FIX tag 712)

intFIX 4.4FIX 5.0 SP2

PosMaintAction (tag 712) is an int field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 2 message types and is required in 2 of them. It is an enumerated field with 3 defined values.

At a glance

Tag
712
Name
PosMaintAction
Datatype
int
Dialects
FIX 4.4 and FIX 5.0 SP2
Messages
2
Valid values
3

What the specification says

FIX 4.4

Maintenance Action to be performed

FIX 5.0 SP2

Maintenance Action to be performed.

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

A real message using tag 712

PositionMaintenanceReport · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength163
35MsgTypeAMPosition Maintenance Report
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
721PosMaintRptIDEXAMPLE
709PosTransType1Exercise
712PosMaintAction1New: used to increment the overall transaction quantity
713OrigPosReqRefIDEXAMPLE
722PosMaintStatus0Accepted
715ClearingBusinessDate20240101
1AccountACCT-11223
581AccountType1Account is carried on customer Side of Books
60TransactTime20240101-12:00:00.000
10CheckSum249
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.

ValueMeaningSymbolic nameDialects
1New: used to increment the overall transaction quantityNEW_USED_TO_INCREMENT_THE_OVERALL_TRANSACTION_QUANTITYFIX 4.4, FIX 5.0 SP2
2Replace: used to override the overall transaction quantity or specific add messages based on the reference idREPLACE_USED_TO_OVERRIDE_THE_OVERALL_TRANSACTION_QUANTITY_OR_SPECIFIC_ADD_MESSAGES_BASED_ON_THE_REFERENCE_ID / REPLACE_USED_TO_OVERRIDE_THE_OVERALL_TRANSACTION_QUANTITY_OR_SPECIFI_ADD_MESSAGES_BASED_ON_THE_REFERENCE_IDFIX 4.4, FIX 5.0 SP2
3Cancel: used to remove the overall transaction or specific add messages based on reference idCANCEL_USED_TO_REMOVE_THE_OVERALL_TRANSACTION_OR_SPECIFIC_ADD_MESSAGES_BASED_ON_REFERENCE_IDFIX 4.4, FIX 5.0 SP2
4ReverseREVERSE_USED_TO_COMPLETELLY_BACK_OUT_THE_TRANSACTION_SUCH_THAT_THE_TRANSACTION_NEVER_EXISTEDFIX 5.0 SP2

Where tag 712 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.

MessageMsgTypeFIX 4.4FIX 5.0 SP2Where in the message
PositionMaintenanceReportAMRequiredRequireddirectly on the message body
PositionMaintenanceRequestALRequiredRequireddirectly 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 712 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 posMaintAction = message.fields[712]?.raw;// e.g. "1" — New: used to increment the overall transaction quantity// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(712)  ?.enumValues?.find((e) => e.value === posMaintAction)  ?.description;

Other int fields

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