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.|
Unique identifier of Execution Report message assigned by exchange. Uniqueness is guaranteed within a single trading day or the life of a multi-day order.
For futures and options markets: represents Operator ID.
For EBS and fixed income markets: represents the Entering Trader.
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.pdfIn FirmSoft and Global Command Center queries for order status and cancellations, this value must be exact.
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.
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:
- Unique ID from Party Details Definition Request Acknowledgment message
For on-demand messages:
- If not registered beforehand through iLink then Party Details Definition Request message will be sent along with the business message and will immediately precede it
|37||OrderID||uInt64||8||Y||Unique identifier for order assigned by the exchange. Uniqueness is guaranteed within a single trading day across all instruments.|
|44||Price||PRICE9||8||Y||Price per share or contract.|
|99||StopPx||PRICENULL9||8||N||The stop price of a stop limit or stop protect order (conditionally required if tag 40-OrdType=3 or 4).|
|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.|
OrderRequestID used to identify a request to enter, modify, or delete an order. Echoed back on the Execution Report.
For the unsolicited events (e.g. fills and end of day eliminations), echo the value on the ExecutionReport representing the last accepted OrderRequestID on the corresponding order.
|548||CrossID||uInt64NULL||8||N||Identifier for a cross order. Will be present if Execution Report is in response to a cross order.|
Host-assigned entity ID used to reference all components of a Cross: sides + strategy + legs.
The HostCrossID also links components of the Cross order. For example, each individual Execution Report associated with the order will contain HostCrossID to tie them to the original Cross order.
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 ftp.cmegroup.com/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.
Note: this field is optional for EBS Market and eFIX Matching Service instruments.
|48||SecurityID||Int32||4||Y||Security ID as defined in the market data Security Definition message.|
Number of shares or contracts ordered.
Total quantity filled.
This tag gets reset back to 0 with cancel, elimination, and non- IFM modification.
Minimum quantity of an order for immediate execution.
The value of MinQty must be between 1 and the value in tag 38-OrderQty.
If set to 0 or default null value then it means that minimum quantity is n.
If the quantity present in tag 110 cannot be immediately executed, the entire order is eliminated.
The quantity to be displayed. Required for display quantity orders.
Note: on orders, this value specifies the qty to be displayed; on Execution Reports this value indicates the currently displayed quantity.
Date of order expiration (last day the order can trade), always expressed in terms of the local market date.
Sent in number of days since Unix epoch.
Not currently being used.
Identifies status of order as Cancelled.
Describes the specific Execution Report as cancelled.
- OrdType=1 (Market order with protection)
- OrdType=2 (Limit order)
- OrdType=4 (Stop limit order)
- OrdType=K (Market limit order)
- Side=1 (Buy)
- Side=2 (Sell)
|Side of order.|
- TimeInForce=0 (Day)
- TimeInForce=1 (GTC)
- TimeInForce=3 (FAK)
- TimeInForce=4 (FOK)
- TimeInForce=6 (GTD)
- TimeInForce=99 (GFS)
Specifies how long the order remains in effect
FOK is supported only for BrokerTec and EBS
GFS is supported only for EBS
Indicates if order was sent 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.
Note: this tag will contain the resting value attached with the order regardless of how the cancel itself was submitted.
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
- 0=Split Msg Delayed
- 1=Out of Order Msg Delayed
- 2=Complete Msg Delayed
Indicates if a message was delayed as a result of:
- being split among multiple packets (0)
- TCP re-transmission (1)
- due to a previously submitted split or out of order message (2).
If absent then the message was not delayed, split, or received out of order.
- ExecRestatementReason=8 (Exchange)
- ExecRestatementReason=9 (Cancelled Not Best)
- ExecRestatementReason=100 (Cancel on Disconnect)
- ExecRestatementReason=103 (Cancel Resting due to Self Match Prevention)
- ExecRestatementReason=104 (Cancel from CME Globex Credit Controls violation)
- ExecRestatementReason=105 (Cancel from CME One)
- ExecRestatementReason=106 (Cancel from Risk Management API)
- ExecRestatementReason=107 (Cancel Aggressing due to Self Match Prevention)
- ExecRestatementReason=108 (Cancel due to volatility quote option less than min order size)
Used to communicate unsolicited cancels.
- ExecRestatementReason=9 (Cancelled Not Best) for fixed income markets only
Type of cross being submitted to a market (if in response to a Cross order).
- Bit 0=AON
- Bit 1=Only Best
- Bit 2=Not Held
Instructions for order handling for fixed income markets.
Only Best may be applied to resting and aggressing orders and:
- Prevents submission of an order if the order’s price is not equal to or better than the best price on the book.
- Cancels an order from the book if a new order with a better price enters the queue.
- This order condition permits the order to be alone at the best price level or join other orders at the best price level.
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.
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.
Indicates if an order was submitted for market making obligation as required for MIFID.
Applicable only for EU BrokerTec and EBS MiFID.
Boolean: flags a managed order.
Applicable only to Repo fixed income markets.
- 0=Long Sell
- 1=Short Sale With No Exemption (SESH)
- 2=Short Sale With Exemption (SSEX)
- 3=Undisclosed Sell (Information not available – UNDI)
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.
|The 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. |
Indicates the amount of time in nanoseconds that a message was subject to additional processing as a result of being:
- split among multiple packets (tag 9553=0)
- out-of-order (tag 9553=1)
- a previously submitted split message (tag 9553=2)
Subtracting this number from tag 60-TransactTime will represent original received time of in-flight message.
The presence of DiscretionPrice on an order indicates that the trader wishes to display one price but will accept trades at another price
Note - DiscretionPrice must be greater than zero
Applicable only for EBS