PosMaintResult (FIX tag 723)
PosMaintResult (tag 723) is an int field defined in FIX 4.4. It appears in 1 message type, always optionally. It is an enumerated field with 3 defined values.
At a glance
- Tag
- 723
- Name
- PosMaintResult
- Datatype
- int
- Dialects
- FIX 4.4
- Messages
- 1
- Valid values
- 3
What the specification says
Result of Position Maintenance Request.
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 723
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 169 | |
| 35 | MsgType | AM | Position Maintenance Report |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 721 | PosMaintRptID | EXAMPLE | |
| 709 | PosTransType | 1 | Exercise |
| 712 | PosMaintAction | 1 | New: used to increment the overall transaction quantity |
| 713 | OrigPosReqRefID | EXAMPLE | |
| 722 | PosMaintStatus | 0 | Accepted |
| 723 | PosMaintResult | 0 | Successful completion - no warnings or errors |
| 715 | ClearingBusinessDate | 20240101 | |
| 1 | Account | ACCT-11223 | |
| 581 | AccountType | 1 | Account is carried on customer Side of Books |
| 60 | TransactTime | 20240101-12:00:00.000 | |
| 10 | CheckSum | 009 |
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.
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 |
|---|---|---|
| 0 | Successful completion - no warnings or errors | SUCCESSFUL_COMPLETION |
| 1 | Rejected | REJECTED |
| 99 | Other | OTHER |
Where tag 723 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 |
|---|---|---|---|
| PositionMaintenanceReport | AM | Optional | 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 723 in TypeScript
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const posMaintResult = message.fields[723]?.raw;// e.g. "0" — Successful completion - no warnings or errors// The dictionary also carries the labels:const label = fix.dictionary .fieldByTag(723) ?.enumValues?.find((e) => e.value === posMaintResult) ?.description;Other int fields
- 722PosMaintStatus
- 724PosReqType
- 725ResponseTransportType
- 727TotalNumPosReports
- 718AdjustmentType
- 728PosReqResult
- 729PosReqStatus
- 731SettlPriceType
- 733UnderlyingSettlPriceType
- 712PosMaintAction
- 709PosTransType
- 706PosQtyStatus
- 698YieldRedemptionPriceType
- 748TotNumTradeReports
- 749TradeRequestResult
- 750TradeRequestStatus
- 751TradeReportRejectReason
- 694QuoteRespType
- 752SideMultiLegReportingType
- 692QuotePriceType
- 690LegSwapType
- 759Nested2PartyRole
- 686LegPriceType
- 680LegBenchmarkPriceType
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