Tag number, field name, MsgType, message or component name, or a value such as 39=1 or OrdStatus=2. Search runs in your browser.
TradeCondition <277>
- Tag
277- Type
- MultipleValueString (base String) · code set
TradeConditionCodeSet - Pedigree
- Added FIX 4.2
- Versions
- FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓
This page shows TradeCondition <277> as defined in FIX 4.2. For the current standard, see tag 277 TradeCondition in FIX Latest.
TradeCondition <277> in plain English
Summary by The MidPoint News, based on the FIX Latest description in the Orchestra file. The FIX 4.2 description is quoted in full below and may differ.
TradeCondition carries one or more condition codes for a trade in market data, separated by spaces, such as opening or cash trade.
Where it is used
MDFullGrp (repeating group), MDIncGrp (repeating group) . In all, 2 messages in FIX 4.2 can carry it. Full list.
Example message
8=FIX.4.2|9=121|35=X|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|262=MDR-1|268=1|279=0|269=2|55=AAPL|270=190.46|271=200|277=E|10=138 Illustrative example, not real orders or market data. A MarketDataIncrementalRefresh (35=X) 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)
Space-delimited list of conditions describing a trade