FIX TAG 103
OrdRejReason
Definition
Code to identify reason for order rejection.
Compare versions
Differences between the selected source snapshots, including wording and errata; not a migration guide.
FIX 4.2 FIX 4.4
Values only in FIX 4.4 8
9Trade Along required10Invalid Investor ID11Unsupported order characteristic12Surveillance Option13Incorrect quantity14Incorrect allocated quantity15Unknown account(s)99Other
Value text or deprecation changed 2
| Value | FIX 4.2 | FIX 4.4 |
|---|---|---|
0 | Broker option | Broker / Exchange option |
6 | Duplicate Order (e.g. dupe ClOrdID) | Duplicate Order (e.g. dupe ClOrdID (11)) |
Values 17
| Value | Meaning |
|---|---|
0 | Broker / Exchange option |
1 | Unknown symbol |
2 | Exchange closed |
3 | Order exceeds limit |
4 | Too late to enter |
5 | Unknown Order |
6 | Duplicate Order (e.g. dupe ClOrdID (11)) |
7 | Duplicate of a verbally communicated order |
8 | Stale Order |
9 | Trade Along required |
10 | Invalid Investor ID |
11 | Unsupported order characteristic |
12 | Surveillance Option |
13 | Incorrect quantity |
14 | Incorrect allocated quantity |
15 | Unknown account(s) |
99 | Other |
About the int data type
Sequence of digits without commas or decimals and optional sign character (ASCII characters "-" and "0" - "9" ). The sign character utilizes one byte (i.e. positive int is "99999" while negative int is "-99999"). Note that int values may contain leading zeros (e.g. "00023" = "23"). Examples: 723 in field 21 would be mapped int as |21=723|. -723 in field 12 would be mapped int as |12=-723| The following data types are based on int.
Used in messages 2
Includes nested components and repeating groups. Open a location to see its surrounding requirements.
35=8ExecutionReportMessage body35=NListStatusOrdListStatGrp