DerivativeEventDate (FIX tag 1288)
DerivativeEventDate (tag 1288) is a LocalMktDate field defined in FIX 5.0 SP2. It appears in 3 message types, always optionally.
At a glance
- Tag
- 1288
- Name
- DerivativeEventDate
- Datatype
- LocalMktDate (String)
- Format
- YYYYMMDD
- Dialects
- FIX 5.0 SP2
- Messages
- 3
What the specification says
Date of event.
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 1288
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIXT.1.1 | |
| 9 | BodyLength | 130 | |
| 35 | MsgType | z | DerivativeSecurityListRequest |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 320 | SecurityReqID | EXAMPLE | |
| 559 | SecurityListRequestType | 0 | Symbol |
| 1286 | NoDerivativeEvents2 entries | 2 | repeating group |
| 1287 | DerivativeEventType | 1 | |
| 1288 | DerivativeEventDate | 20240101 | |
| 1287 | DerivativeEventType | 1 | |
| 1288 | DerivativeEventDate | 20240101 | |
| 10 | CheckSum | 090 |
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 1288 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 |
|---|---|---|---|
| DerivativeSecurityList | AA | Optional | inside DerivativeSecurityDefinition › DerivativeInstrument › DerivativeEventsGrp |
| DerivativeSecurityListRequest | z | Optional | inside DerivativeInstrument › DerivativeEventsGrp |
| DerivativeSecurityListUpdateReport | BR | Optional | inside DerivativeSecurityDefinition › DerivativeInstrument › DerivativeEventsGrp |
Wire format
A calendar date in the market's local timezone, with no time component and no offset. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.
Read tag 1288 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[1288];field?.name; // "DerivativeEventDate"field?.raw; // the verbatim wire stringfield?.value; // coerced to a stringOther LocalMktDate fields
- 1276DerivativeIssueDate
- 1252DerivativeMaturityDate
- 1345UnderlyingLegMaturityDate
- 1125OrigTradeDate
- 987UnderlyingSettlementDate
- 976QuantityDate
- 956LegInterestAccrualDate
- 917EndDate
- 916StartDate
- 915AgreementDate
- 874InterestAccrualDate
- 873DatedDate
- 866EventDate
- 743DeliveryDate
- 739LegDatedDate
- 715ClearingBusinessDate
- 701YieldCalcDate
- 696YieldRedemptionDate
- 611LegMaturityDate
- 588LegSettlDate
- 542UnderlyingMaturityDate
- 541MaturityDate
- 504PaymentDate
- 503CardStartDate
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