| ID | MsgType | Abbr | Flow |
|---|---|---|---|
| 8 | 7 | Adv |
| Added | EP | Updated | EP | Deprecated | EP |
|---|---|---|---|---|---|
| FIX.2.7 |
| ID | Name | Abbr | Presence | Description |
|---|---|---|---|---|
| 1024 | StandardHeader | BaseHeader | required | SYNOPSIS:
The standard FIX message header
ELABORATION: |
| 2 | AdvId | AdvId | required | SYNOPSIS:
Unique identifier of advertisement message.
(Prior to FIX 4.1 this field was of type int)
|
| 5 | AdvTransType | AdvTransTyp | required | SYNOPSIS:
Identifies advertisement message transaction type
|
| 3 | AdvRefID | AdvRefID | optional | SYNOPSIS:
Reference identifier used with CANCEL and REPLACE transaction types.
(Prior to FIX 4.1 this field was of type int)
|
| 1003 | Instrument | Instrmt | required | SYNOPSIS:
The Instrument component block contains all the fields commonly used to describe a security or instrument. Typically the data elements in this component block are considered the static data of a security, data that may be commonly found in a security master database. The Instrument component block can be used to describe any asset type supported by FIX.
ELABORATION: |
| 1004 | InstrumentExtension | InstrmtExt | optional | SYNOPSIS:
The InstrumentExtension component block identifies additional security attributes that are more commonly found for Fixed Income securities.
ELABORATION: |
| 1002 | FinancingDetails | FinDetls | optional | SYNOPSIS:
Component block is optionally used for financial transaction where legal contracts, master agreements or master confirmations is to be referenced. This component identifies the legal agreement under which the deal was made and other unique characteristics of the transaction. For example, the AgreementDesc(913) field refers to base standard documents such as MRA 1996 Repurchase Agreement, GMRA 2000 Bills Transaction (U.K.), MSLA 1993 Securities Loan – Amended 1998, for example.
ELABORATION: |
| 2019 | InstrmtLegGrp | Leg | optional | SYNOPSIS: ELABORATION: |
| 2066 | UndInstrmtGrp | Undly | optional | SYNOPSIS: ELABORATION: |
| 1066 | RelatedInstrumentGrp | ReltdInstrmt | optional | SYNOPSIS:
The RelatedInstrumentGrp is a repeating component at the same hierarchical level as the Instrument component, describing relationships and linkages between the Instrument, UnderlyingInstrument and InstrumentLeg entries. If all instances of the UnderlyingInstrument in the message are true underliers of the Instrument then the RelatedInstrumentGrp component is not needed. If any instance of the UnderlyingInstrument has a different relationship, e.g. underlier of an InstrumentLeg, stream, equity equivalent or nearest exchange-traded contract or there are multiple instances of InstrumentLeg, then an entry for every relationship should be included in this component. When the RelatedInstrumentGrp appears within a repeating group, each entry only apply to the Instrument component at the same hierarchical level.
In messages, such as Email(35=C) and News(35=B), where Instrument and the InstrumentLeg are within their repeating groups, the RelatedInstrumentGrp component may be used to link legs and underliers to their appropriate base Instrument.
ELABORATION: For simple relationships such as identifying a "hedges for" security the entry simply defines the symbol or identifier of an externally known security. For relationships within strategies and swaps the entry refers up through one of the "related to" fields to the Instrument, InstrumentLeg, UnderlyingInstrument, stream or dividend period with which the related security has correlation. It then points down through RelatedSecurityID(1650) or RelatedSymbol(1649) to an UnderlyingInstrument instance in the current message defining the related security. The nature of the relationship is given in RelatedInstrumentType(1648). |
| 4 | AdvSide | AdvSide | required | SYNOPSIS:
Broker's side of advertised trade
|
| 53 | Quantity | Qty | required | SYNOPSIS:
Overall/total quantity (e.g. number of shares)
(Prior to FIX 4.2 this field was of type int)
|
| 854 | QtyType | QtyTyp | optional | SYNOPSIS:
Type of quantity specified in quantity field. ContractMultiplier (tag 231) is required when QtyType = 1 (Contracts). UnitOfMeasure (tag 996) and TimeUnit (tag 997) are required when QtyType = 2 (Units of Measure per Time Unit).
|
| 44 | Price | Px | optional | SYNOPSIS:
Price per unit of quantity (e.g. per share)
|
| 15 | Currency | Ccy | optional | SYNOPSIS:
Identifies currency used for price. Absence of this field is interpreted as the default for the security. It is recommended that systems provide the currency value whenever possible. See "Appendix 6-A: Valid Currency Codes" for information on obtaining valid values.
|
| 75 | TradeDate | TrdDt | optional | SYNOPSIS:
Indicates date of trading day. Absence of this field indicates current day (expressed in local time at place of trade).
|
| 60 | TransactTime | TxnTm | optional | SYNOPSIS:
Timestamp when the business transaction represented by the message occurred.
|
| 58 | Text | Txt | optional | SYNOPSIS:
Free format text string
(Note: this field does not have a specified maximum length)
|
| 354 | EncodedTextLen | EncTxtLen | optional | SYNOPSIS:
Byte length of encoded (non-ASCII characters) EncodedText (355) field.
|
| 355 | EncodedText | EncTxt | optional | SYNOPSIS:
Encoded (non-ASCII characters) representation of the Text (58) field in the encoded format specified via the MessageEncoding (347) field. If used, the ASCII (English) representation should also be specified in the Text(58) field.
|
| 149 | URLLink | URL | optional | SYNOPSIS:
A URI (Uniform Resource Identifier) or URL (Uniform Resource Locator) link to additional information (i.e. http://www.XYZ.com/research.html)
See "Appendix 6-B FIX Fields Based Upon Other Standards"
|
| 30 | LastMkt | LastMkt | optional | SYNOPSIS:
Market of execution for last fill, or an indication of the market where an order was routed
Valid values:
See "Appendix 6-C"
ELABORATION: In the context of ESMA RTS 1 Annex I, Table 3, Field 6 "Venue of Execution" it is required that the "venue where the transaction was executed" be identified using ISO 10383 (MIC). Additionally, ESMA requires the use of "MIC code 'XOFF' for financial instruments admitted to trading or traded on a trading venue, where the transaction on that financial instrument is not executed on a trading venue, systematic internaliser or organized trading platform outside of the Union. Use 'SINT' for financial instruments admitted to trading or traded on a trading venue, where the transaction is executed on a systematic internaliser." |
| 336 | TradingSessionID | SesID | optional | SYNOPSIS:
Identifier for a trading session.
A trading session spans an extended period of time that can also be expressed informally in terms of the trading day. Usage is determined by market or counterparties.
To specify good for session where session spans more than one calendar day, use TimeInForce = 0 (Day) in conjunction with TradingSessionID(336).
Bilaterally agreed values of data type "String" that start with a character can be used for backward compatibility.
|
| 625 | TradingSessionSubID | SesSub | optional | SYNOPSIS:
Optional market assigned sub identifier for a trading phase within a trading session. Usage is determined by market or counterparties. Used by US based futures markets to identify exchange specific execution time bracket codes as required by US market regulations. Bilaterally agreed values of data type "String" that start with a character can be used for backward compatibility
|
| 2054 | RoutingGrp | Rtg | optional | SYNOPSIS:
The RoutingGrp is used to allow the application message sender to instruct the intermediary distributing the message who to further send the application message to. The original sender may also instruct who is not allowed to receive the message. When provided, the routing instructions provided in this component are effective on a message by message basis.
ELABORATION: |
| 1025 | StandardTrailer | Trlr | required | SYNOPSIS:
The standard FIX message trailer
ELABORATION: |