TradeReportRejectReason

Tag 751

TradeReportRejectReason

Abbreviation: RejRsn
Typeint
Tag751
AddedFIX.4.4
Used in1 messages

Description

Reason Trade Capture Request was rejected. 100+ Reserved and available for bi-laterally agreed upon user-defined values

Wire Format & Usage Example

Single field (key=value)
751=0 (Successful)
In a FIX message (TradeCaptureReportAck)
8=FIX.4.4 | 9=... | 35=AR | 49=SENDER | 56=TARGET | 34=1 | 52=20240101-09:30:00.000 |  | 751=0 (Successful) |  | 10=...

Fields are delimited by SOH (ASCII 0x01), shown here as " | ". The highlighted field 751=0 (Successful) is this field's position in the message.

All valid values
WireNameDescription
751=0SuccessfulSuccessful (default)
751=1InvalidPartyOnformationInvalid party onformation
751=2UnknownInstrumentUnknown instrument
751=3UnauthorizedToReportTradesUnauthorized to report trades
751=4InvalidTradeTypeInvalid trade type
751=99OtherOther

Enumerated Values

6
ValueSymbolic NameDescriptionAdded
0SuccessfulSuccessful (default)FIX.4.4
1InvalidPartyOnformationInvalid party onformationFIX.4.4
2UnknownInstrumentUnknown instrumentFIX.4.4
3UnauthorizedToReportTradesUnauthorized to report tradesFIX.4.4
4InvalidTradeTypeInvalid trade typeFIX.4.4
99OtherOtherFIX.4.4

Used in Messages

1