| ID | MsgType | Abbr | Flow |
|---|---|---|---|
| 34 | a | QuotStatReq |
| Added | EP | Updated | EP | Deprecated | EP |
|---|---|---|---|---|---|
| FIX.4.2 |
| ID | Name | Abbr | Presence | Description |
|---|---|---|---|---|
| 1024 | StandardHeader | BaseHeader | required | SYNOPSIS:
The standard FIX message header
ELABORATION: |
| 649 | QuoteStatusReqID | StatReqID | optional | SYNOPSIS:
Unique identifier for Quote Status Request.
|
| 117 | QuoteID | QID | optional | SYNOPSIS:
Unique identifier for quote
|
| 1003 | Instrument | Instrmt | optional | 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: |
| 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: |
| 2066 | UndInstrmtGrp | Undly | optional | SYNOPSIS: ELABORATION: |
| 2019 | InstrmtLegGrp | Leg | optional | SYNOPSIS: ELABORATION: |
| 1012 | Parties | Pty | optional | SYNOPSIS:
The Parties component block is used to identify and convey information on the entities both central and peripheral to the financial transaction represented by the FIX message containing the Parties Block. The Parties block allows many different types of entites to be expressed through use of the PartyRole field and identifies the source of the PartyID through the the PartyIDSource.
ELABORATION: |
| 1063 | TargetParties | TgtPty | optional | SYNOPSIS: ELABORATION: |
| 1 | Account | Acct | optional | SYNOPSIS:
Account mnemonic as agreed between buy and sell sides, e.g. broker and institution or investor/intermediary and fund manager.
|
| 660 | AcctIDSource | AcctIDSrc | optional | SYNOPSIS:
Used to identify the source of the Account (1) code. This is especially useful if the account is a new account that the Respondent may not have setup yet in their system.
|
| 581 | AccountType | AcctTyp | optional | SYNOPSIS:
Type of account associated with an order
|
| 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
|
| 263 | SubscriptionRequestType | SubReqTyp | optional | SYNOPSIS:
Subscription Request Type
|
| 1025 | StandardTrailer | Trlr | required | SYNOPSIS:
The standard FIX message trailer
ELABORATION: |