OrderEffective (MEOE)
| ID | 9094 |
The Order Effective event is used to indicate that an order, or an underlying condition of an order, has become effective. This event is applicable to orders such as conditional (Refer to FAQ D26), Stop, Stop Limit, Trailing Stop, Trailing Stop Limit, Stop on Quote, and Stop Limit on Quote orders. This event is NOT applicable to Stop Stock transactions. The Order Effective event must be reported by the party that was holding the order at the time the order or condition became effective.
If the triggering event causing the order to become effective was a specific price, such as a stop price, the triggerPrice field must be populated in scenarios where the trigger price was not explicitly captured in the handlingInstructions field on the related new order (e.g., Stop Formula, Trailing Stop). In scenarios where the stop price was captured in prior CAT events associated with the order (e.g., as a name/value pair in handlingInstructions on MENO and/or MEOA events), then the information may be optionally restated in the triggerPrice field on the Order Effective event; however, it is not required to be reported again.
If a new order ID is generated when the order becomes effective, which replaces the prior order ID, the orderID field must capture the new order ID, and the priorOrderID field must reflect the order ID that is being replaced. If the orderID remains the same when the order becomes effective, the priorOrderID and priorOrderKeyDate must remain blank.
Field | Name | Type | Req'd | Comments | Pedigree |
|---|---|---|---|---|---|
2 | Y | Indicates whether the event is a new event, a firm initiated correction or a repair of a CAT error. | |||
38 | Required when actionType is ‘RPR’. Must be blank when actionType is ‘NEW’. | ||||
44 | Y | An identifier assigned to the record by the reporting firm. Formatted as Must be unique for the Event Date and CAT Reporter IMID. | |||
131 | Y | MEOE | |||
22 | The SRO-assigned identifier that an Industry Member uses to report to CAT. If populated, must equal the CATReporterIMID in the filename. | ||||
78 | Y | When a new Order Key is assigned, the date and time the orderID was assigned. When a new Order Key is not assigned, the orderKeyDate of the CAT event which is being modified. | |||
77 | Y | When a new Order Key is assigned, the internal order ID assigned to the order by the Industry Member. Must be unique within orderKeyDate, CATReporterIMID, and symbol combination. When a new Order Key is not assigned, the orderID of the Order Modified (Cancel/Replace) event which is being modified. | |||
123 | Y | The symbol of the stock in the symbology of the primary listing exchange or FINRA for OTC Equity Securities. | |||
92 | If a new Order Key has been assigned, this is the orderKeyDate of the event being modified. | ||||
91 | If a new Order Key has been assigned, this is the orderID of the event being modified. When populated, the priorOrderID must not be equal to the orderID within the record. | ||||
80 | An identifier used in instances of a merger or acquisition where the originating firm had open limit orders on its books that will be executed or otherwise resolved under the surviving firm. Must be provided to support linkage to an event that was reported with a different CATReporterIMID. | ||||
39 | Y | The date/time the order or underlying condition became effective. | |||
timeInForce | Y | The Time in Force for the order (e.g., DAY, IOC, GTC). | |||
129 | Y | The trading session(s) during which an order is eligible to trade. | |||
107 | Field is Reserved for Future Use and must remain blank. | ||||
120 | The side of the order. For this Reportable Event, only same-side adjustments are allowed (e.g., sell long to short sell). Required if the field changed when the order or underlying condition became effective. | ||||
84 | The limit price of the order. When provided, must be greater than or equal to zero. Required if the field changed when the order became effective. | ||||
96 | The order quantity. Required if the field changed when the order or underlying condition became effective. | ||||
60 | The minimum quantity of an order to be executed. Required if the field changed when the order or underlying condition became effective. Must be > 0. | ||||
79 | Y | The type of order being submitted (e.g., market, limit). Required if the field changed when the order became effective. | |||
117 | The sequence number assigned to the CAT event by the ATS’s matching engine. Any alphanumeric not containing a delimiter. | ||||
12 | Indicates if the order is displayed outside of the ATS to subscribers only, or via publicly disseminated quotation data. | ||||
32 | The displayed price of the order. When provided, must be greater than or equal to zero. Required when applicable and the field changed when the order or underlying condition became effective. | ||||
135 | The working price of the order. When provided, must be greater than or equal to zero. Required when applicable and the field changed when the order or underlying condition became effective. | ||||
33 | The displayed quantity for this order. Required when applicable and the field changed when the order or underlying condition became effective. | ||||
65 | The NBBO at the moment the order was originated or received. Prices are required, quantities are optional. When provided, must be greater than or equal to zero. If no price or quantity, fields must be populated with a value of ‘0’. | ||||
66 | The NBBO at the moment the order was originated or received. Prices are required, quantities are optional. When provided, must be greater than or equal to zero. If no price or quantity, fields must be populated with a value of ‘0’. | ||||
67 | The NBBO at the moment the order was originated or received. Prices are required, quantities are optional. When provided, must be greater than or equal to zero. If no price or quantity, fields must be populated with a value of ‘0’. | ||||
68 | The NBBO at the moment the order was originated or received. Prices are required, quantities are optional. When provided, must be greater than or equal to zero. If no price or quantity, fields must be populated with a value of ‘0’. | ||||
63 | Source of the NBBO data used. If nbboSource is ‘NA’, NBBO price and quantity fields must be populated with a value of ‘0’ and the nbboTimestamp must be blank. | ||||
64 | The date/time at which the NBBO was referenced upon the receipt of the order. Must be blank if nbboSource is ‘NA’. | ||||
130 | The price at which the order became effective. Required in scenarios where the trigger price was not explicitly captured in the handlingInstructions field on the related new order (e.g., Stop Formula, Trailing Stop) | ||||
70 | The net price of the order when tied to stock, tied to fixed income, tied to futures, tied to a non-CAT reportable product, or part of another trading strategy in which the order is traded at a net price. When netPrice is populated, the price field must be blank or populated with a value of zero. Refer to CAT FAQ B71 for additional information. |
Orchimate Copyright 2026 Atomic Wire Technology Limited
Orchestra Copyright 2026 FIX Protocol Ltd
Terms of Use|Privacy Policy