Message IOI Scenario base

SYNOPSIS: Indication of interest messages are used to market merchandise which the broker is buying or selling in either a proprietary or agency capacity. The indications can be time bound with a specific expiration value. Indications are distributed with the understanding that other firms may react to the message first and that the merchandise may no longer be available due to prior trade. Indication messages can be transmitted in various transaction types; NEW, CANCEL, and REPLACE. All message types other than NEW modify the state of the message identified in IOIRefID.

ID MsgType Abbr Flow
76IOI

Pedigree

Added EP Updated EP Deprecated EP
FIX.2.7

Responses

None

Members

IOI base members
ID Name Abbr Presence Description
1024StandardHeaderBaseHeaderrequiredSYNOPSIS: The standard FIX message header
ELABORATION:
1057ApplicationSequenceControlApplSeqCtrloptionalSYNOPSIS: The ApplicationSequenceControl is used for application sequencing and recovery. Consisting of ApplSeqNum (1181), ApplID (1180), ApplLastSeqNum (1350), and ApplResendFlag (1352), FIX application messages that carries this component block will be able to use application level sequencing. ApplID, ApplSeqNum and ApplLastSeqNum fields identify the application id, application sequence number and the previous application sequence number (in case of intentional gaps) on each application message that carries this block.
ELABORATION:
23IOIIDIOIID required SYNOPSIS: Unique identifier of IOI message. (Prior to FIX 4.1 this field was of type int)
28IOITransTypeTransTyp required SYNOPSIS: Identifies IOI message transaction type
26IOIRefIDRefID optional SYNOPSIS: Reference identifier used with CANCEL and REPLACE, transaction types. (Prior to FIX 4.1 this field was of type int)
1003InstrumentInstrmtrequiredSYNOPSIS: The Instrument component block contains all the fields commonly used to describe a security or instrument. Typically the data elements in this component block are considered the static data of a security, data that may be commonly found in a security master database. The Instrument component block can be used to describe any asset type supported by FIX.
ELABORATION:
1004InstrumentExtensionInstrmtExtoptionalSYNOPSIS: The InstrumentExtension component block identifies additional security attributes that are more commonly found for Fixed Income securities.
ELABORATION:
1012PartiesPtyoptionalSYNOPSIS: The Parties component block is used to identify and convey information on the entities both central and peripheral to the financial transaction represented by the FIX message containing the Parties Block. The Parties block allows many different types of entites to be expressed through use of the PartyRole field and identifies the source of the PartyID through the the PartyIDSource.
ELABORATION:
1002FinancingDetailsFinDetlsoptionalSYNOPSIS: Component block is optionally used for financial transaction where legal contracts, master agreements or master confirmations is to be referenced. This component identifies the legal agreement under which the deal was made and other unique characteristics of the transaction. For example, the AgreementDesc(913) field refers to base standard documents such as MRA 1996 Repurchase Agreement, GMRA 2000 Bills Transaction (U.K.), MSLA 1993 Securities Loan – Amended 1998, for example.
ELABORATION:
2066UndInstrmtGrpUndlyoptionalSYNOPSIS:
ELABORATION:
1066RelatedInstrumentGrpReltdInstrmtoptionalSYNOPSIS: The RelatedInstrumentGrp is a repeating component at the same hierarchical level as the Instrument component, describing relationships and linkages between the Instrument, UnderlyingInstrument and InstrumentLeg entries. If all instances of the UnderlyingInstrument in the message are true underliers of the Instrument then the RelatedInstrumentGrp component is not needed. If any instance of the UnderlyingInstrument has a different relationship, e.g. underlier of an InstrumentLeg, stream, equity equivalent or nearest exchange-traded contract or there are multiple instances of InstrumentLeg, then an entry for every relationship should be included in this component. When the RelatedInstrumentGrp appears within a repeating group, each entry only apply to the Instrument component at the same hierarchical level. In messages, such as Email(35=C) and News(35=B), where Instrument and the InstrumentLeg are within their repeating groups, the RelatedInstrumentGrp component may be used to link legs and underliers to their appropriate base Instrument.
ELABORATION: For simple relationships such as identifying a "hedges for" security the entry simply defines the symbol or identifier of an externally known security. For relationships within strategies and swaps the entry refers up through one of the "related to" fields to the Instrument, InstrumentLeg, UnderlyingInstrument, stream or dividend period with which the related security has correlation. It then points down through RelatedSecurityID(1650) or RelatedSymbol(1649) to an UnderlyingInstrument instance in the current message defining the related security. The nature of the relationship is given in RelatedInstrumentType(1648).
54SideSide required SYNOPSIS: Side of order (see Volume : "Glossary" for value definitions)
854QtyTypeQtyTyp optional SYNOPSIS: Type of quantity specified in quantity field. ContractMultiplier (tag 231) is required when QtyType = 1 (Contracts). UnitOfMeasure (tag 996) and TimeUnit (tag 997) are required when QtyType = 2 (Units of Measure per Time Unit).
1011OrderQtyDataOrdQtyoptionalSYNOPSIS: The OrderQtyData component block contains the fields commonly used for indicating the amount or quantity of an order. Note that when this component block is marked as "required" in a message either one of these three fields must be used to identify the amount: OrderQty, CashOrderQty or OrderPercent (in the case of CIV).
ELABORATION:
27IOIQtyQty required SYNOPSIS: Quantity (e.g. number of shares) in numeric form or relative size.
15CurrencyCcy optional SYNOPSIS: Identifies currency used for price. Absence of this field is interpreted as the default for the security. It is recommended that systems provide the currency value whenever possible. See "Appendix 6-A: Valid Currency Codes" for information on obtaining valid values.
1019StipulationsStipoptionalSYNOPSIS: The Stipulations component block is used in Fixed Income to provide additional information on a given security. These additional information are usually not considered static data information.
ELABORATION:
2020InstrmtLegIOIGrpIOIoptionalSYNOPSIS:
ELABORATION:
423PriceTypePxTyp optional SYNOPSIS: Code to represent the price type.
ELABORATION: For Financing transactions PriceType(423) implies the "repo type" - Fixed or Floating - 9 (Yield) or 6 (Spread) respectively - and Price(44) gives the corresponding "repo rate". See Volume 1 "Glossary" for further value definitions.
1074PriceQualifierGrpPxQualoptionalSYNOPSIS: The PriceQualifierGrp component clarifies the composition of the price when standard market practice for the security calls for a price that is atypical when traded in other markets, or when a price can be expressed in more than one way.
ELABORATION:
44PricePx optional SYNOPSIS: Price per unit of quantity (e.g. per share)
62ValidUntilTimeValidUntilTm optional SYNOPSIS: Indicates expiration time of indication message (always expressed in UTC (Universal Time Coordinated, also known as "GMT")
25IOIQltyIndQltyInd optional SYNOPSIS: Relative quality of indication
130IOINaturalFlagNatFlag optional SYNOPSIS: Indicates that IOI is the result of an existing agency order or a facilitation position resulting from an agency order, not from principal trading or order solicitation activity.
2024IOIQualGrpQualoptionalSYNOPSIS:
ELABORATION:
58TextTxt optional SYNOPSIS: Free format text string (Note: this field does not have a specified maximum length)
354EncodedTextLenEncTxtLen optional SYNOPSIS: Byte length of encoded (non-ASCII characters) EncodedText (355) field.
355EncodedTextEncTxt optional SYNOPSIS: Encoded (non-ASCII characters) representation of the Text (58) field in the encoded format specified via the MessageEncoding (347) field. If used, the ASCII (English) representation should also be specified in the Text(58) field.
60TransactTimeTxnTm optional SYNOPSIS: Timestamp when the business transaction represented by the message occurred.
149URLLinkURL optional SYNOPSIS: A URI (Uniform Resource Identifier) or URL (Uniform Resource Locator) link to additional information (i.e. http://www.XYZ.com/research.html) See "Appendix 6-B FIX Fields Based Upon Other Standards"
2054RoutingGrpRtgoptionalSYNOPSIS: The RoutingGrp is used to allow the application message sender to instruct the intermediary distributing the message who to further send the application message to. The original sender may also instruct who is not allowed to receive the message. When provided, the routing instructions provided in this component are effective on a message by message basis.
ELABORATION:
1018SpreadOrBenchmarkCurveDataSprdBnchmkCurveoptionalSYNOPSIS: The SpreadOrBenchmarkCurveData component block is primarily used for Fixed Income to convey spread to a benchmark security or curve.
ELABORATION:
2252RelativeValueGrpReltvValoptionalSYNOPSIS: The RelativeValueGrp component is used to convey relative valuation metrics or analytics for a given instrument.
ELABORATION: Relative valuation metrics or analytics are commonly provided by the trading party providing pricing as part of fixed income cash bonds or OTC derivatives indication or quoting activities.
1022YieldDataYieldoptionalSYNOPSIS: The YieldData component block conveys yield information for a given Fixed Income security.
ELABORATION:
1025StandardTrailerTrlrrequiredSYNOPSIS: The standard FIX message trailer
ELABORATION: