SecondaryClOrdID (526)

, ,
1

Imported from previous forum

2

[ original email was from ron newell - rnewell@cme.com ]
A SecondaryClOrdID was introduced but appears inconsistently applied.

Currently appears in Execution Report and Order Cancel Reject message types.

Should also appear in New Order-Single, Order Cancel/Replace Request, Order Cancel Request, Order Status Request, Order Mass Cancel Request, Order Mass Cancel Report, New Order-Cross, Cross Order Cancel/Replace Request, Cross Order Cancel Request, New Order-Multileg, and Multileg Order Cancel/Replace Request message types.

Also, SecondaryClOrdID is improperly defined in Data Dictionary. Should read "Unique secondary identifier for Order as assigned by the buy-side (trader, desk, broker, institution) as identified by SenderSubID (50) or SenderCompID (49). Uniqueness must be guaranteed within a single trading day. Firms should ensure uniqueness across days (eg: embedding a date within the SecondaryClOrdID) if electronically submitting multi-day orders, trading globally or through-out market close periods."

3

This has been addressed for the final release of FIX 4.3 (post-Draft #3). Thank you.

[PC20010822_2] Address post-Draft #3 documentation/consistency issues with SecondaryClOrdID, SecondaryOrderID, and SecondaryExecID field

Rationale:

  • SecondaryClOrdID should appear in exactly every message where a new ClOrdID is specified (buy-side). In addition, it should be allowed for in sell-side messages where the sell-side echoes back a ClOrdID
  • SecondaryExecID should appear in exactly every message containing an ExecID originated by the sell-side
  • SecondaryOrderID should be in exactly every message where a new OrderID is specified (sell-side)

Changes associated with this item:

  • SecondaryClOrdID should appear in exactly every message where a new ClOrdID is specified (buy-side). In addition, it should be allowed for in sell-side messages where the sell-side echoes back a ClOrdID

  • Added SecondaryClOrdID (to all messages with ClOrdID) to the New Order – Single, Order Cancel/Replace Request, Order Cancel Request, Order Status Request, Order Mass Cancel Request, Order Mass Cancel Report, New Order – Cross, Cross Order Cancel/Replace Request, Cross Order Cancel Request, New Order – Multileg, Multileg Order Cancel/Replace Request, New Order – List, List Strike Price, List Status messages.

  • Corrected SecondaryClOdID definition in Field Reference changing “which accepts” to “which originates”.

> A SecondaryClOrdID was introduced but appears inconsistently applied.
>
> Currently appears in Execution Report and Order Cancel Reject message types.
>
> Should also appear in New Order-Single, Order Cancel/Replace Request, Order Cancel Request, Order Status Request, Order Mass Cancel Request, Order Mass Cancel Report, New Order-Cross, Cross Order Cancel/Replace Request, Cross Order Cancel Request, New Order-Multileg, and Multileg Order Cancel/Replace Request message types.
>
> Also, SecondaryClOrdID is improperly defined in Data Dictionary. Should read "Unique secondary identifier for Order as assigned by the buy-side (trader, desk, broker, institution) as identified by SenderSubID (50) or SenderCompID (49). Uniqueness must be guaranteed within a single trading day. Firms should ensure uniqueness across days (eg: embedding a date within the SecondaryClOrdID) if electronically submitting multi-day orders, trading globally or through-out market close periods."
>
>