Branch Code/Sequence Number FIX Field?

, ,
1

Imported from previous forum

2

I would like to know if there is a FIX field name for the SIAC Order Message format fields known as "branch code" and "sequence number."

These fields combine to form a unique identifier for a given exchange; it does not need to unique within a firm.

Thank you.

3

[ original email was from Ryan Pierce - rpierce@taltrade.com ]
> I would like to know if there is a FIX field name for the SIAC Order Message format fields known as "branch code" and "sequence number."

In case where one firm acts as a service bureau, accepts FIX orders and routes them to SIAC via CMS, that service bureau can report the branch code and sequence number in the OrderID field, or the service bureau can assign its own unique OrderID and populate SecondaryOrderID (introduced in FIX 4.1) with the branch code and sequence number.

4

> I would like to know if there is a FIX field name for the SIAC Order Message format fields known as "branch code" and "sequence number."
>
> These fields combine to form a unique identifier for a given exchange; it does not need to unique within a firm.
>
> Thank you.
>
>

Indeed when communicating with CMS via the FIX protocol, the ClOrdID(FIX Tag 11) will be required to consist of:
Branch, Sequence and date. This information is currently in the CMS order line 1 with the addition of order date to support
uniqueness over multiple days. Sender must assure that the same Branch and Sequence combination is
not used more than once per day, otherwise a timestamp must also be added.

Avner…