ExDestinationIDSource (FIX tag 1133)

charFIX 5.0 SP2

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

NewOrderSingle · FIX 5.0 SP2
TagFieldWire valueMeaning
8BeginStringFIXT.1.1
9BodyLength118
35MsgTypeDNewOrderSingle
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
1133ExDestinationIDSourceBBIC (Bank Identification Code) (ISO 9362)
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum141
Edit and decode it yourself

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.

Open in the full decoder →

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.

ValueMeaningSymbolic name
BBIC (Bank Identification Code) (ISO 9362)BIC
CGenerally accepted market participant identifier (e.g. NASD mnemonic)GENERALLY_ACCEPTED_MARKET_PARTICIPANT_IDENTIFIER
DProprietary / Custom codePROPRIETARY_CUSTOM_CODE
EISO Country CodeISO_COUNTRY_CODE
GMIC (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.

MessageMsgTypeRequirednessWhere in the message
CrossOrderCancelReplaceRequesttOptionaldirectly on the message body
MultilegOrderCancelReplaceACOptionaldirectly on the message body
NewOrderCrosssOptionaldirectly on the message body
NewOrderListEOptionalinside the ListOrdGrp component
NewOrderMultilegABOptionaldirectly on the message body
NewOrderSingleDOptionaldirectly on the message body
OrderCancelReplaceRequestGOptionaldirectly on the message body
QuoteSOptionaldirectly on the message body
QuoteResponseAJOptionaldirectly on the message body
QuoteStatusReportAIOptionaldirectly 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

decode.tsts
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

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