Tag number, field name, MsgType, message or component name, or a value such as 39=1 or OrdStatus=2. Search runs in your browser.
OrdRejReason <103>
- Tag
103- Type
- int · also accepts Reserved100Plus · code set
OrdRejReasonCodeSet - FIXML name
RejRsn- Pedigree
- Added FIX 2.7
- Versions
- FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓
OrdRejReason <103> in plain English
Summary by The MidPoint News, based on the description in the Orchestra file (quoted in full below).
OrdRejReason gives the reason an order was rejected. The Orchestra file notes that values 3, 4 and 5 are used when rejecting an order because of errors in pre-allocation information.
Common values
| Value | Name |
|---|---|
103=0 | BrokerCredit |
103=1 | UnknownSymbol |
103=2 | ExchangeClosed |
103=3 | OrderExceedsLimit |
103=4 | TooLateToEnter |
103=5 | UnknownOrder |
103=6 | DuplicateOrder |
103=11 | UnsupportedOrderCharacteristic |
103=13 | IncorrectQuantity |
103=99 | Other |
A selection. The full list of values is in the table further down.
Where it is used
ExecutionReport (35=8), OrdListStatGrp (repeating group), OrderEntryAckGrp (repeating group) .
In all, 3 messages in FIX Latest can carry it. Full list.
Example message
8=FIXT.1.1|9=190|35=8|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|37=OID-5001|11=ORD-1001|17=EXEC-7001|150=8|39=8|55=AAPL|54=1|38=1000|40=2|44=190.50|151=0|14=0|6=0|60=20261116-08:30:00.000|103=1|10=163 Illustrative example, not real orders or market data. An ExecutionReport (35=8) in FIX Latest, shown with BeginString FIXT.1.1. Instrument identifiers (such as AAPL, ISIN US0378331005, ESZ6, XNAS, XCME) are real public codes used for illustration. Order and execution IDs, accounts, prices, quantities and times are made up. Fields are separated by | here; on the wire the separator is the SOH character (ASCII 1). BodyLength (9) and CheckSum (10) are calculated for this example. Every tag and value in it is checked against the FIX Latest dictionary, but it is not a complete specification of the message.
Description (from the Orchestra file)
Code to identify reason for order rejection. Note: Values 3, 4, and 5 will be used when rejecting an order due to pre-allocation information errors.
Values (35)
| Value | Name |
|---|---|
| 0 | BrokerCredit |
| 1 | UnknownSymbol |
| 2 | ExchangeClosed |
| 3 | OrderExceedsLimit |
| 4 | TooLateToEnter |
| 5 | UnknownOrder |
| 6 | DuplicateOrder |
| 7 | DuplicateOfAVerballyCommunicatedOrder |
| 8 | StaleOrder |
| 9 | TradeAlongRequired |
| 10 | InvalidInvestorID |
| 11 | UnsupportedOrderCharacteristic |
| 12 | SurveillanceOption |
| 13 | IncorrectQuantity |
| 14 | IncorrectAllocatedQuantity |
| 15 | UnknownAccount |
| 16 | PriceExceedsCurrentPriceBand |
| 18 | InvalidPriceIncrement |
| 19 | ReferencePriceNotAvailable |
| 20 | NotionalValueExceedsThreshold |
| 21 | AlgorithmRiskThresholdBreached |
| 22 | ShortSellNotPermitted |
| 23 | ShortSellSecurityPreBorrowRestriction |
| 24 | ShortSellAccountPreBorrowRestriction |
| 25 | InsufficientCreditLimit |
| 26 | ExceededClipSizeLimit |
| 27 | ExceededMaxNotionalOrderAmt |
| 28 | ExceededDV01PV01Limit |
| 29 | ExceededCS01Limit |
| 30 | LastLook |
| 31 | LastLookLatency |
| 32 | UnavailablePriceLiquidity |
| 33 | InvalidMissingEntitlements |
| 34 | MinMaxSizeExceeded |
| 99 | Other |
Used in
Messages (1)
| Message | MsgType | Presence |
|---|---|---|
| ExecutionReport | 8 | Optional |
Components and repeating groups (2)
| Name | Kind | Presence |
|---|---|---|
| OrdListStatGrp | Repeating group | Optional |
| OrderEntryAckGrp | Repeating group | Optional |