| ID | MsgType | Abbr | Flow |
|---|---|---|---|
| 18 | H | OrdStatReq |
| Added | EP | Updated | EP | Deprecated | EP |
|---|---|---|---|---|---|
| FIX.2.7 |
| ID | Name | Abbr | Presence | Description |
|---|---|---|---|---|
| 1024 | StandardHeader | Hdr | required | SYNOPSIS:
The standard FIX message header
ELABORATION: |
| 37 | OrderID | OrdID | optional | SYNOPSIS:
Unique identifier for Order as assigned by sell-side (broker, exchange, ECN). Uniqueness must be guaranteed within a single trading day. Firms which accept multi-day orders should consider embedding a date within the OrderID field to assure uniqueness across days.
|
| 11 | ClOrdID | ClOrdID | required | SYNOPSIS:
Unique identifier for Order as assigned by the buy-side (institution, broker, intermediary etc.) (identified by SenderCompID (49) or OnBehalfOfCompID (5) as appropriate). Uniqueness must be guaranteed within a single trading day. Firms, particularly those which electronically submit multi-day orders, trade globally or throughout market close periods, should ensure uniqueness across days, for example by embedding a date within the ClOrdID field.
|
| 526 | SecondaryClOrdID | ClOrdID2 | optional | SYNOPSIS:
Assigned by the party which originates the order. Can be used to provide the ClOrdID (11) used by an exchange or executing system.
|
| 583 | ClOrdLinkID | ClOrdLinkID | optional | SYNOPSIS:
Permits order originators to tie together groups of orders in which trades resulting from orders are associated for a specific purpose, for example the calculation of average execution price for a customer or to associate lists submitted to a broker as waves of a larger program trade.
|
| 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: |
| 790 | OrdStatusReqID | StatReqID | optional | SYNOPSIS:
Can be used to uniquely identify a specific Order Status Request message.
|
| 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.
|
| 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: |
| 1002 | FinancingDetails | FinDetls | optional | SYNOPSIS:
Component block is optionally used only for financing deals to identify the legal agreement under which the deal was made and other unique characteristics of the transaction. The AgreementDesc 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: |
| 54 | Side | Side | required | SYNOPSIS:
Side of order
|
| 1025 | StandardTrailer | Trlr | required | SYNOPSIS:
The standard FIX message trailer
ELABORATION: |