Tag number, field name, MsgType, message or component name, or a value such as 39=1 or OrdStatus=2. Search runs in your browser.
MaturityMonthYear <200>
- Tag
200- Type
- MonthYear (base String)
- FIXML name
MMY- Pedigree
- Added FIX 4.1 · Updated FIX Latest EP282
- Versions
- FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓
This page shows MaturityMonthYear <200> as defined in FIX 4.4. For the current standard, see tag 200 MaturityMonthYear in FIX Latest.
MaturityMonthYear <200> in plain English
Summary by The MidPoint News, based on the FIX Latest description in the Orchestra file. The FIX 4.4 description is quoted in full below and may differ.
MaturityMonthYear gives the month and year of maturity for standardised futures and options, as an alternative to MaturityDate (541). The common format is YYYYMM, and a day or week code can be added.
Where it is used
Instrument (component) . In all, 59 messages in FIX 4.4 can carry it. Full list.
Example message
8=FIX.4.4|9=121|35=d|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|320=SDR-1|322=SD-1|323=1|55=ESZ6|167=FUT|200=202612|207=XCME|10=122 Illustrative example, not real orders or market data. A SecurityDefinition (35=d) in FIX 4.4, shown with BeginString FIX.4.4. 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.4 dictionary, but it is not a complete specification of the message.
Related tags: MaturityDate <541>
Description (from the Orchestra file)
Can be used with standardized derivatives vs. the MaturityDate (541) field. Month and Year of the maturity (used for standardized futures and options). Format: YYYYMM (i.e. 199903) YYYYMMDD (20030323) YYYYMMwN (200303w) for week A specific date or can be appended to the MaturityMonthYear. For instance, if multiple standard products exist that mature in the same Year and Month, but actually mature at a different time, a value can be appended, such as "w" or "w2" to indicate week as opposed to week 2 expiration. Likewise, the date (0-3) can be appended to indicate a specific expiration (maturity date).
Used in
Components and repeating groups (1)
| Name | Kind | Presence |
|---|---|---|
| Instrument | Component | Optional |
All 59 messages that can carry MaturityMonthYear, including through components and groups
- Advertisement
- AllocationInstruction
- AllocationReport
- AssignmentReport
- CollateralAssignment
- CollateralInquiry
- CollateralInquiryAck
- CollateralReport
- CollateralRequest
- CollateralResponse
- Confirmation
- CrossOrderCancelReplaceRequest
- CrossOrderCancelRequest
- DerivativeSecurityList
- DontKnowTrade
- ExecutionReport
- IOI
- ListStrikePrice
- MarketDataIncrementalRefresh
- MarketDataRequest
- MarketDataSnapshotFullRefresh
- MassQuote
- MassQuoteAcknowledgement
- MultilegOrderCancelReplace
- NewOrderCross
- NewOrderList
- NewOrderMultileg
- NewOrderSingle
- News
- OrderCancelReplaceRequest
- OrderCancelRequest
- OrderMassCancelReport
- OrderMassCancelRequest
- OrderMassStatusRequest
- OrderStatusRequest
- PositionMaintenanceReport
- PositionMaintenanceRequest
- PositionReport
- Quote
- QuoteCancel
- QuoteRequest
- QuoteRequestReject
- QuoteResponse
- QuoteStatusReport
- QuoteStatusRequest
- RFQRequest
- RequestForPositions
- RequestForPositionsAck
- SecurityDefinition
- SecurityDefinitionRequest
- SecurityList
- SecurityListRequest
- SecurityStatus
- SecurityStatusRequest
- TradeCaptureReport
- TradeCaptureReportAck
- TradeCaptureReportRequest
- TradeCaptureReportRequestAck