Message TradeCaptureReportRequestAck Scenario base

SYNOPSIS: The Trade Capture Request Ack message is used to: - Provide an acknowledgement to a Trade Capture Report Request in the case where the Trade Capture Report Request is used to specify a subscription or delivery of reports via an out-of-band ResponseTransmissionMethod. - Provide an acknowledgement to a Trade Capture Report Request in the case when the return of the Trade Capture Reports matching that request will be delayed or delivered asynchronously. This is useful in distributed trading system environments. - Indicate that no trades were found that matched the selection criteria specified on the Trade Capture Report Request or the Trade Capture Request was invalid for some business reason, such as request is not authorized, invalid or unknown instrument, party, trading session, etc.

ID MsgType Abbr Flow
76AQTrdCaptRptReqAck

Pedigree

Added EP Updated EP Deprecated EP
FIX.4.4FIX.5.0SP2192

Responses

None

Members

TradeCaptureReportRequestAck base members
ID Name Abbr Presence Description
1024StandardHeaderBaseHeaderrequiredSYNOPSIS: The standard FIX message header
ELABORATION:
568TradeRequestIDReqID required SYNOPSIS: Trade Capture Report Request ID
1003TradeIDTrdID optional SYNOPSIS: The unique ID assigned to the trade entity once it is received or matched by the exchange or central counterparty.
1040SecondaryTradeIDTrdID2 optional SYNOPSIS: Used to carry an internal trade entity ID which may or may not be reported to the firm
1041FirmTradeIDFirmTrdID optional SYNOPSIS: The ID assigned to a trade by the Firm to track a trade within the Firm system. This ID can be assigned either before or after submission to the exchange or central counterpary
1042SecondaryFirmTradeIDFirmTrdID2 optional SYNOPSIS: Used to carry an internal firm assigned ID which may or may not be reported to the exchange or central counterpary
569TradeRequestTypeReqTyp required SYNOPSIS: Type of Trade Capture Report.
263SubscriptionRequestTypeSubReqTyp optional SYNOPSIS: Subscription Request Type
748TotNumTradeReportsTotNumTrdRpts optional SYNOPSIS: Total number of trade reports returned.
749TradeRequestResultReqRslt required SYNOPSIS: Result of Trade Request
750TradeRequestStatusReqStat required SYNOPSIS: Status of Trade Request.
1003InstrumentInstrmtoptionalSYNOPSIS: The Instrument component block contains all the fields commonly used to describe a security or instrument. Typically the data elements in this component block are considered the static data of a security, data that may be commonly found in a security master database. The Instrument component block can be used to describe any asset type supported by FIX.
ELABORATION:
1004InstrumentExtensionInstrmtExtoptionalSYNOPSIS: The InstrumentExtension component block identifies additional security attributes that are more commonly found for Fixed Income securities.
ELABORATION:
2066UndInstrmtGrpUndlyoptionalSYNOPSIS:
ELABORATION:
2019InstrmtLegGrpLegoptionalSYNOPSIS:
ELABORATION:
442MultiLegReportingTypeMLegRptTyp optional SYNOPSIS: Used to indicate how the multi-legged security (e.g. option strategies, spreads, etc.) is being reported.
725ResponseTransportTypeRspTransportTyp optional SYNOPSIS: Identifies how the response to the request should be transmitted. Details specified via ResponseDestination (726).
726ResponseDestinationRspDest optional SYNOPSIS: URI (Uniform Resource Identifier) for details) or other pre-arranged value. Used in conjunction with ResponseTransportType (725) value of Out-of-Band to identify the out-of-band destination. See "Appendix 6-B FIX Fields Based Upon Other Standards"
58TextTxt optional SYNOPSIS: Free format text string (Note: this field does not have a specified maximum length)
354EncodedTextLenEncTxtLen optional SYNOPSIS: Byte length of encoded (non-ASCII characters) EncodedText (355) field.
355EncodedTextEncTxt optional SYNOPSIS: Encoded (non-ASCII characters) representation of the Text (58) field in the encoded format specified via the MessageEncoding (347) field. If used, the ASCII (English) representation should also be specified in the Text(58) field.
1011MessageEventSourceMsgEvtSrc optional SYNOPSIS: Used to identify the event or source which gave rise to a message. Valid values will be based on an exchange's implementation. Example values are: "MQM" (originated at Firm Back Office) "Clear" (originated in Clearing System) "Reg" (static data generated via Register request)
1025StandardTrailerTrlrrequiredSYNOPSIS: The standard FIX message trailer
ELABORATION: