ExDestinationIDSource (FIX tag 1133)
ExDestinationIDSource (tag 1133) is a char field defined in FIX 5.0 SP2. It appears in 10 message types, always optionally. It is an enumerated field with 5 defined values.
At a glance
- Tag
- 1133
- Name
- ExDestinationIDSource
- Datatype
- char
- Dialects
- FIX 5.0 SP2
- Messages
- 10
- Valid values
- 5
What the specification says
The ID source of ExDestination
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 1133
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIXT.1.1 | |
| 9 | BodyLength | 118 | |
| 35 | MsgType | D | NewOrderSingle |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 11 | ClOrdID | ORD-10042 | |
| 1133 | ExDestinationIDSource | B | BIC (Bank Identification Code) (ISO 9362) |
| 54 | Side | 1 | Buy |
| 60 | TransactTime | 20240101-12:00:00.000 | |
| 40 | OrdType | 1 | Market |
| 10 | CheckSum | 141 |
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 |
|---|---|---|
| B | BIC (Bank Identification Code) (ISO 9362) | BIC |
| C | Generally accepted market participant identifier (e.g. NASD mnemonic) | GENERALLY_ACCEPTED_MARKET_PARTICIPANT_IDENTIFIER |
| D | Proprietary / Custom code | PROPRIETARY_CUSTOM_CODE |
| E | ISO Country Code | ISO_COUNTRY_CODE |
| G | MIC (ISO 10383 - Market Identifier Code) | MIC |
Where tag 1133 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 |
|---|---|---|---|
| CrossOrderCancelReplaceRequest | t | Optional | directly on the message body |
| MultilegOrderCancelReplace | AC | Optional | directly on the message body |
| NewOrderCross | s | Optional | directly on the message body |
| NewOrderList | E | Optional | inside the ListOrdGrp component |
| NewOrderMultileg | AB | Optional | directly on the message body |
| NewOrderSingle | D | Optional | directly on the message body |
| OrderCancelReplaceRequest | G | Optional | directly on the message body |
| Quote | S | Optional | directly on the message body |
| QuoteResponse | AJ | Optional | directly on the message body |
| QuoteStatusReport | AI | 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 1133 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 exDestinationIDSource = message.fields[1133]?.raw;// e.g. "B" — BIC (Bank Identification Code) (ISO 9362)// The dictionary also carries the labels:const label = fix.dictionary .fieldByTag(1133) ?.enumValues?.find((e) => e.value === exDestinationIDSource) ?.description;Other char fields
- 1124OrigTradeHandlingInstr
- 1123TradeHandlingInstr
- 1118RootPartyIDSource
- 1115OrderCategory
- 1111TriggerOrderType
- 1109TriggerPriceDirection
- 1108TriggerPriceTypeScope
- 1107TriggerPriceType
- 1162SettlObligTransType
- 1164SettlObligSource
- 1101TriggerAction
- 1100TriggerType
- 1093LotType
- 1092PriceProtectionScope
- 1084DisplayMethod
- 1083DisplayWhen
- 1081RefOrderIDSource
- 1193SettlMethod
- 1060UnderlyingInstrumentPartyIDSource
- 1050InstrumentPartyIDSource
- 1049InstrmtAssignmentMethod
- 1048DealingCapacity
- 1047AllocPositionEffect
- 1046UnderlyingFXRateCalc
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