AsOfIndicator (FIX tag 1015)
AsOfIndicator (tag 1015) is a char field defined in FIX 5.0 SP2. It appears in 2 message types, always optionally. It is an enumerated field with 2 defined values.
At a glance
- Tag
- 1015
- Name
- AsOfIndicator
- Datatype
- char
- Dialects
- FIX 5.0 SP2
- Messages
- 2
- Valid values
- 2
What the specification says
A trade that is being submitted for a trade date prior to the current trade or clearing date, e.g. in an open outcry market an out trade being submitted for the previous trading session or trading day.
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 1015
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIXT.1.1 | |
| 9 | BodyLength | 104 | |
| 35 | MsgType | AE | TradeCaptureReport |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 1015 | AsOfIndicator | 0 | false - trade is not an AsOf trade |
| 32 | LastQty | 1000000 | |
| 31 | LastPx | 1.09210 | |
| 552 | NoSides1 entry | 1 | repeating group |
| 54 | Side | 1 | Buy |
| 10 | CheckSum | 135 |
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.
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 | false - trade is not an AsOf trade | FALSE_TRADE_IS_NOT_AN_ASOF_TRADE |
| 1 | true - trade is an AsOf trade | TRUE_TRADE_IS_AN_ASOF_TRADE |
Where tag 1015 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 |
|---|---|---|---|
| TradeCaptureReport | AE | Optional | directly on the message body |
| TradeCaptureReportAck | AR | Optional | directly on the message body |
Wire format
A single character. Most char fields are enumerated, so the value is one of a fixed set rather than arbitrary text. @boarteam/fix keeps the value as a string and, for enumerated fields, reports validate/value-not-in-enum when it is not a defined value.
Read tag 1015 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 asOfIndicator = message.fields[1015]?.raw;// e.g. "0" — false - trade is not an AsOf trade// The dictionary also carries the labels:const label = fix.dictionary .fieldByTag(1015) ?.enumValues?.find((e) => e.value === asOfIndicator) ?.description;Other char fields
- 1036ExecAckStatus
- 1046UnderlyingFXRateCalc
- 1047AllocPositionEffect
- 1048DealingCapacity
- 1049InstrmtAssignmentMethod
- 980SecurityUpdateAction
- 1050InstrumentPartyIDSource
- 1060UnderlyingInstrumentPartyIDSource
- 950Nested3PartyIDSource
- 1081RefOrderIDSource
- 1083DisplayWhen
- 1084DisplayMethod
- 1092PriceProtectionScope
- 1093LotType
- 1100TriggerType
- 1101TriggerAction
- 1107TriggerPriceType
- 1108TriggerPriceTypeScope
- 1109TriggerPriceDirection
- 1111TriggerOrderType
- 1115OrderCategory
- 1118RootPartyIDSource
- 1123TradeHandlingInstr
- 1124OrigTradeHandlingInstr
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