|9726||SeqNum||uInt32||4||Y||Sequence number assigned to this message.|
|39001||UUID||uInt64||8||Y||Matches Establish.UUID used to establish the connection.|
Used by submitting firm to group trades being allocated into an average price group.
The trades in average price group will be used to calculate an average price for the group.
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:
- Unique ID from Party Details Definition Request Acknowledgment message
For on-demand messages:
- If not registered beforehand through iLink then Party Details Definition Request Ack message will be sent along with the business message and will immediately precede it
|1510||PartyDetailsListReportID||uInt64||8||Y||Refers to the unique identifier of the Party Details List Request (35=CF) message used to request this Party Details List Report.|
|5297||SendingTimeEpoch||uInt64||8||Y||Time when the message is sent. 64-bit integer expressing the number of nano seconds since midnight January 1, 1970.|
|2362||SelfMatchPreventionID||uInt64NULL||8||N||Identifies an order or trade that should not be matched to an opposite order or trade if both buy and sell orders for the same asset contain the same tag 2362-SelfMatchPreventionID and submitted by the same firm.|
|1512||TotNumParties||uInt16||2||Y||Indicates total number of Party Details List Reports being returned in response to Party Details List Request.|
2=No Data Found That Matched Selection Criteria
3=Not Authorized to Retrieve Data
4=Data Temporarily Unavailable
|Status of party details list request.|
|Indicates whether this message is the last Party Details List Report in response to Party Details List Request.|
1=Member trading for their own account
2=Clearing firm trading for its proprietary account
3=Member trading for another member
Capacity of customer placing the order.
Used by futures exchanges to indicate the CTICode (customer type indicator) as required by the US CFTC (Commodity Futures Trading Commission).
|Designates the account type to be used for the order when submitted to clearing.|
Used to act upon the outcome when a self-match is detected and an order is prevented from trading against another order with the same SelfMatchPreventionID (tag 2362).
N=Cancel newest signifies that incoming order is cancelled
O=Cancel Oldest signifies that the resting order is cancelled
Absence of this field (with Tag 2362) is interpreted as cancel oldest.
0=No average pricing
1=Trade is part of an average price group identified by the AvgPxGroupID(1731)
3=Trade is part of a notional value average price group
A notional value average price (NVAP) group is effectively closed and available for allocation as long as the NVAP of the group is non-zero
|Average pricing indicator.|
0=Trade clearing at execution price
1=Trade clearing at alternate clearing price
|Indicates to recipient whether trade is clearing at execution prices tag 31-LastPx or alternate clearing price (prior day settlement price).|
|Indicates if the order is a give-up or SGX offset|
- C = FCM-provided screen
- D = Other provided screen
- G = FCM API or FIX
- H = Algo Engine
- W = Desk – Electronic
- Y = Client – Electronic
Codes that apply special information that the Broker / Dealer needs to report, as specified by the customer.
Defines source of the order.
Will be populated with the MIFID short code for the person or algo identified in FIX tag 5392 which will be mapped to National ID or Algo at reporting time.
Applicable for EU fixed income markets only.
Represents the MIFID Short Code of the Investment Decision Maker Short Code.
Applicable for EU fixed income markets only.
Flags message as possible retransmission.
This will convey whether a message is an original transmission or duplicate in response to Retransmission Request.
Used when original messages are interleaved with Retransmission responses.
- 0=Split Msg Delayed
- 1=Out of Order Msg Delayed
- 2=Complete Msg Delayed
Indicates if a message was delayed as a result of:
- being split among multiple packets (0)
- TCP re-transmission (1)
- due to a previously submitted split or out of order message (2).
If absent, the message was not delayed and was neither split nor received out of order.
Number of party details.
More than one occurrence of the same party role will be rejected.
|→1691||PartyDetailID||String20Req||20||Y||The identification of the party. Required when NoPartyDetails (tag 1671) > 0|
|→1692||PartyDetailIDSource||PartyIDSource||0||Y||Always “C” – Generally accepted market participant identifier|
Used to identify source of PartyDetailID value. Required when NoPartyDetails (tag 1671) > 0
- PartyRole=96 (take up firm)
- PartyRole=1000 (take up account)
- PartyRole=1 (executing firm)
- PartyRole=118 (operator)
- PartyRole=24 (customer account)
Identifies the type of PartyDetailID. Required when NoPartyDetails (tag 1671) > 0.
PartyDetailRole=24 is required for futures and options markets.
PartyDetailRole=1 is required for futures, options and fixed income markets.
PartyDetailRole=118 represents investment decision maker and is applicable for futures and options markets. This operator may be the same as that identified in tag 5392-SenderID.
PartyDetailRole=96 and 1000 are applicable only for futures and options markets.
Number of regulatory publication rules in repeating group for MIFID reporting
Used to indicate that an ESCB customer can exempt from disclosure any activity that is related to central banking activity
Should always be '1' if used otherwise set to '0'
2=Exempt from Publication
Specifies the type of regulatory trade publication
Additional reasons for the publication type will be specified in tag 2670-TrdRegPublicationReason
Represents allowable exemptions for the post-trade publication of trade transactions
Should always be "2"
12=Exempted due to European System of Central Banks (ESCB) policy transaction
Additional reason for trade publication type specified in tag 2669-TrdRegPublicationType (2669)
Reasons may be specific to regulatory trade publication rules
Should always be "12"