iLink 3 Execution Report - Trade Addendum Outright
The Execution Report - Trade Addendum Outright message notifies client systems of trade cancellation or correction for outrights.
Bolded red text indicates support for EBS Market.
35=8, 39=H,G
Tag | Name | Binary Type | Binary Length | Req | Enumeration | Description |
---|---|---|---|---|---|---|
9726 | SeqNum | uInt32 | 4 | Y | Sequence number assigned to this message. The max value is 999999999 which is 1 short of 1 billion. | |
39001 | UUID | uInt64 | 8 | Y | Matches Establish.UUID used to establish the connection. | |
17 | ExecID | String40 | 40 | Y | Globally unique identifier for each Execution Report message assigned by exchange. | |
5392 | SenderID | String20Req | 20 | Y | For futures and options markets: represents Operator ID. This value represents the individual or team submitting the message and is subject to registration requirements and character limits as required by Rule 576 and the Advisory below: https://www.cmegroup.com/rulebook/files/cme-group-Rule-576.pdf In FirmSoft and Global Command Center queries for order status and cancellations, this value must be exact. This tag value is always uppercase, regardless of the case in the inbound message tag. Client systems are not required to submit capitalized identifier to CME Globex. | |
11 | CIOrdID | String20Req | 20 | Y | Unique identifier for Order as assigned by client system. 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. | |
1505 | PartyDetailsListReqID | uInt64 | 8 | Y | The unique identifier of the Party Details Definition Request Acknowledgment associated with this message; this is the value submitted on the inbound message. For pre-registered messages:
For on-demand messages:
| |
31 | LastPx | PRICE9 | 8 | Y | Price of this (last) fill. | |
37 | OrderID | uInt64 | 8 | Y | Globally unique identifier for each order assigned by the exchange. | |
60 | TransactTime | uInt64 | 8 | Y | Time the transaction represented by this Execution Report (35=8) occurred. Expressed as nanoseconds since epoch time. | |
5297 | SendingTimeEpoch | uInt64 | 8 | Y | Time when the message is sent. 64-bit integer expressing the number of nanoseconds since midnight January 1, 1970. | |
527 | SecExecID | uInt64 | 8 | Y | Unique identifier linking spread summary fill notice with leg fill notice and trade cancel messages. To uniquely identify each fill, Client System can concatenate: OrderID (37) + TradeDate (75) + SecExecID (527) | |
9703 | OrigSecondaryExecutionID | uInt64NULL | 8 | N | Unique identifier of the corrected fill. | |
9537 | Location | String5Req | 5 | Y | ISO identifier of the physical location of the individual or team head trader identified by the tag 5392 (SenderID) in the message. The first two bytes as per ISO 3166-1, identify the country (e.g., JP = Japan, CN = China). The next three bytes indicate a comma-delimited state or province code (e.g., CA = California, QC = Quebec). For valid values, refer to https://www.cmegroup.com/ftp/fix/coo/. Market Regulation requires only the submission of the two first characters of tag 9537-Location for all countries with the exception of Canada. For Canada, the 5 bytes including the province code must be submitted. | |
48 | SecurityID | Int32 | 4 | Y | Security ID as defined in the market data Security Definition message. | |
32 | LastQty | uInt32 | 4 | Y | Quantity bought/sold on this (last) fill. | |
1506 | SideTradeID | uInt32 | 4 | Y | Trade ID assigned to the trade once it is received or matched by the exchange. | |
1507 | OrigSideTradeID | uInt32NULL | 4 | N | Refers to the unique ID assigned to the corrected trade. | |
75 | TradeDate | LocalMktDate | 2 | Y | Indicates date of trading day (expressed in local time at place of trade). Sent in number of days since Unix epoch. | |
39 | OrdStatus | OrdStatusTrdCxl | 1 | Y |
| Identifies status of order as trade cancellation or correction. |
150 | ExecType | ExecTypTrdCxl | 1 | Y |
| Describes the specific Execution Report as trade cancellation or correction. |
54 | Side | SideReq | 1 | Y |
| Order side. |
1028 | ManualOrderIndicator | ManualOrdIndReq | 1 | Y |
| Indicates if the message was initially received manually. '0' indicates the message was generated by automated trading logic. iLink messages containing a value other than '0' or '1' in this tag will be rejected. This tag is subject to Rule 536.B.2 Electronic Audit Trail Requirements for Electronic Order Routing/Front-End Systems. https://www.cmegroup.com/rulebook/files/cme-group-Rule-536-B-Tag1028.pdf |
9765 | PossRetransFlag | BooleanFlag | 1 | Y |
| Flags message as possible retransmission or duplicate. Indicates if message is an original transmission or duplicate in response to Retransmission Request or possible duplicate. Used when original messages are interleaved with Retransmission responses. Possible duplicate means the same message may have been sent again with different sequence number. |
18 | ExecInst | ExecInst | 1 | N |
| Instructions for order handling for fixed income markets. Only Best may be applied to resting and aggressing orders and:
Not Held (applies only to US Repo) eliminates quantity remaining from an FaKi order (tag 59=3) and ensures it will it not be included in a work-up session; however, the order can still trigger a work-up session. AONs will have a separate book with a separate ISIN. The AON orders that cannot trade immediately can rest in the AON book. They can only trade with AON orders on the other side of the AON book that have the SAME PRICE and SAME QUANTITY. Applicable only for BrokerTec Markets; should not be used for future and options markets. |
5906 | ExecutionMode | ExecMode | 1 | N |
| Instruction for whether the order should rest on the book upon entry or match as an aggressor. A Passive Order will rest in the market without executing unless matched with an Aggressive Order on the other side. An Aggressive Order will match against any other order on the opposite side. Applicable for US & EU Repos. |
9373 | LiquidityFlag | BooleanNULL | 1 | N |
| Indicates if an order was submitted for market making obligation as required for MIFID. Applicable only for EU BrokerTec MiFID. |
6881 | ManagedOrder | BooleanNULL | 1 | N |
| Boolean: flags a managed order. Applicable only to Repo fixed income markets. |
5409 | ShortSaleType | ShortSaleType | 1 | N |
| Indicates the type of short sale on Sell orders only as required for MiFID. Should not be used for Buy orders. Applicable only for EU fixed income markets. NoteThe Short-Selling Field is only required from Participants when BrokerTec EU has a regulatory obligation (pursuant to Article 26(5) of MiFIR) to conduct transaction reporting on behalf of the Participant. This obligation only applies to BrokerTec EU when the relevant participant is exempt from MiFIR (typically non-EEA (European Economic Area) firms, corporate entities or certain asset managers). Please reach out to TradingVenueCompliance@cmegroup.com for guidance. |
845 | DiscretionPrice | PRICENULL9 | 8 | N | The discretion price of an order. Conditionally required if the trader wishes to display one price but will accept trades at another price).
Applicable only for EBS. | |
828 | TradeType | uInt16NULL | 2 | N |
| Represents a trade at fixing price. |
378 | ExecRestatementReason | ExecReason | 1 | N |
| Will be present when trade at fixing is assigned fixing price. |
64 | SettlDate | LocalMktDate | 2 | N | Specific date of trade settlement. | |
541 | MaturityDate | LocalMktDate | 2 |