FIX 4.2 Business Message Reject (35=j)
Rejects an application message that passed session-level checks but cannot be processed, for example an unsupported message type or a missing conditionally required field. It is not used when a specific reject exists, such as an Execution Report rejecting an order.
- MsgType (tag 35)
- j
- Name in FIX 4.2
- BusinessMessageReject
- Category
- Application
- Required body fields
- 2
Fields in FIX 4.2
Body fields in the order the FIX 4.2 definition lists them. A repeating group starts with its counter field (NoXxx), followed by the fields of each entry, indented. A field inside an optional component or group is required only when that component or group is present.
| Tag | Field | Required |
|---|---|---|
| 45 | RefSeqNum | Optional |
| 372 | RefMsgType | Required |
| 379 | BusinessRejectRefID | Optional |
| 380 | BusinessRejectReason | Required |
| 58 | Text | Optional |
| 354 | EncodedTextLen | Optional |
| 355 | EncodedText | Optional |
Every message also carries the FIX 4.2 standard header (BeginString, BodyLength, MsgType, SenderCompID, TargetCompID, MsgSeqNum, SendingTime and others) and ends with CheckSum (10).
Also in other versions
Business Message Reject across all FIX versions
Decode a Business Message Reject messageField and message data comes from the QuickFIX data dictionaries for FIX 4.0 to 5.0 SP2 and FIXT 1.1, used under the QuickFIX Software License. This product includes software developed by quickfixengine.org (http://www.quickfixengine.org/). Enumerated value names are converted to plain text for reading.