ApplNewSeqNum (FIX tag 1399)
ApplNewSeqNum (tag 1399) is a SeqNum field defined in FIX 5.0 SP2. It appears in 1 message type, always optionally.
At a glance
- Tag
- 1399
- Name
- ApplNewSeqNum
- Datatype
- SeqNum (int)
- Dialects
- FIX 5.0 SP2
- Messages
- 1
What the specification says
Used to specify a new application sequence number.
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 1399
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIXT.1.1 | |
| 9 | BodyLength | 131 | |
| 35 | MsgType | BY | ApplicationMessageReport |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 1356 | ApplReportID | EXAMPLE | |
| 1426 | ApplReportType | 0 | Reset ApplSeqNum to new value specified in ApplNewSeqNum(1399) |
| 1351 | NoApplIDs2 entries | 2 | repeating group |
| 1355 | RefApplID | EXAMPLE | |
| 1399 | ApplNewSeqNum | 1 | |
| 1355 | RefApplID | EXAMPLE | |
| 1399 | ApplNewSeqNum | 1 | |
| 10 | CheckSum | 219 |
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 5.0 SP2 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.
Where tag 1399 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 |
|---|---|---|---|
| ApplicationMessageReport | BY | Optional | inside the ApplIDReportGrp component |
Wire format
A positive sequence number. Session-level, and monotonic within a session. @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 1399 in TypeScript
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[1399];field?.name; // "ApplNewSeqNum"field?.raw; // the verbatim wire stringfield?.value; // coerced to a numberOther SeqNum 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-fix50sp2