Message OrderList Scenario base

SYNOPSIS: The NewOrderList Message can be used in one of two ways depending on which market conventions are being followed.

ID MsgType Abbr Flow
15E

Pedigree

Added EP Updated EP Deprecated EP
FIX.2.7

Responses

None

Members

OrderList base members
ID Name Abbr Presence Description
1001StandardHeaderrequiredSYNOPSIS: The standard FIX message header
ELABORATION:
66ListID required SYNOPSIS: Unique identifier for list as assigned by institution, used to associate multiple individual orders. Uniqueness must be guaranteed within a single trading day. Firms which generate multi-day orders should consider embedding a date within the ListID field to assure uniqueness across days.
390BidID optional SYNOPSIS: Unique identifier for Bid Response as assigned by broker. Uniqueness must be guaranteed within a single trading day.
391ClientBidID optional SYNOPSIS: Unique identifier for a Bid Request as assigned by institution. Uniqueness must be guaranteed within a single trading day.
414ProgRptReqs optional SYNOPSIS: Code to identify the desired frequency of progress reports.
394BidType required SYNOPSIS: Code to identify the type of Bid Request.
415ProgPeriodInterval optional SYNOPSIS: Time in minutes between each ListStatus report sent by SellSide. Zero means don’t send status.
433ListExecInstType optional SYNOPSIS: Identifies the type of ListExecInst.
69ListExecInst optional SYNOPSIS: Free format text message containing list handling and execution instructions.
352EncodedListExecInstLen optional SYNOPSIS: Byte length of encoded (non-ASCII characters) EncodedListExecInst field.
353EncodedListExecInst optional SYNOPSIS: Encoded (non-ASCII characters) representation of the ListExecInst field in the encoded format specified via the MessageEncoding field. If used, the ASCII (English) representation should also be specified in the ListExecInst field.
68TotNoOrders required SYNOPSIS: Total number of list order entries across all messages. Should be the sum of all NoOrders in each message that has repeating list order entries related to the same ListID. Used to support fragmentation. (Prior to FIX 4.2 this field was named "ListNoOrds")
2030ListOrdGrprequired Number of orders in this message (number of repeating groups to follow)
1002StandardTrailerrequiredSYNOPSIS: The standard FIX message trailer
ELABORATION: