Tag number, field name, MsgType, message or component name, or a value such as 39=1 or OrdStatus=2. Search runs in your browser.
BusinessRejectRefID <379>
- Tag
379- Type
- String
- Pedigree
- Added FIX 4.2
- Versions
- FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓
This page shows BusinessRejectRefID <379> as defined in FIX 4.2. For the current standard, see tag 379 BusinessRejectRefID in FIX Latest.
BusinessRejectRefID <379> in plain English
Summary by The MidPoint News, based on the description in the Orchestra file (quoted in full below).
BusinessRejectRefID carries the value of the business-level ID field, such as a ClOrdID, on the message being rejected by a BusinessMessageReject.
Where it is used
BusinessMessageReject (35=j) .
In all, 1 message in FIX 4.2 can carry it. Full list.
Example message
8=FIX.4.2|9=111|35=j|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|45=12|372=D|379=ORD-1001|380=2|58=Unknown security|10=017 Illustrative example, not real orders or market data. A BusinessMessageReject (35=j) in FIX 4.2, shown with BeginString FIX.4.2. 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 4.2 dictionary, but it is not a complete specification of the message.
Description (from the Orchestra file)
The value of the business-level "ID" field on the message being referenced.
Used in
Messages (1)
| Message | MsgType | Presence |
|---|---|---|
| BusinessMessageReject | j | Optional |