The New Order Cross message submits a Cross on CME Globex, a two-sided order submitted by a single party/broker at the same price and quantity.
The → symbol indicates a repeating tag.
|548||CrossID||uInt64||8||Y||Identifier for a cross order. Must be unique during a given trading day.|
|2422||OrderRequestID||uInt64||8||Y||Use OrderRequestID to identify a request to enter a cross order. Echoed back on the Execution Report.|
|Indicates if the message was initially received manually.|
|9726||SeqNum||uInt32||4||Y||Sequence number assigned to this message.|
For futures and options markets:
Should be unique per Firm ID.
Assigned value used to identify specific message originator.
Represents last individual or team responsible for the system that modifies the order prior to submission to CME Globex.
For fixed income markets: represents the Entering Trader.
Only ‘2’ (limit order) supported.
A cross order which is executed on one side with any unfilled quantity remaining active.
Indicates if one side of the cross order should be prioritized.
|44||Price||PRICE9||8||Y||Conditionally required when tag 40-OrdType=2 (Limit).|
|483||TransBkdTime||uInt64||8||Y||For derivatives, a timestamp to indicate when this order was booked with the agent prior to submission to the exchange. Indicates the time at which the order was finalized between the buyer and seller prior to submission. 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.|
|9537||Location||String5Req||5||Y||Text describing sender's location (i.e. geographic location and/or desk).|
Security ID as defined in the market data Security Definition message.
Number of Side repeating group instances.
Unique identifier for Order as assigned by the buy side (institution, broker, intermediary, etc.). 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.
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:
Order quantity. Must be the same for both sides.
|→54||Side||SideReq||1||Y||Side of order.|
|→962||SideTimeInForce||SideTimeInForce||1||Y||Indicates how long the order as specified in the side stays in effect. SideTimeInForce allows a two-sided cross order to specify order behavior separately for each side.|