| ID |
Name |
Abbr |
Presence |
Description |
| 1000 | CommissionData | Comm | required | SYNOPSIS:
The CommissionData component block is used to carry commission information such as the type of commission and the rate. Use the CommissionDataGrp component as an alternative if multiple commissions or enhanced attributes are needed.
ELABORATION:
This component may be used to provide aggregated commission data of a given CommType(13) where the CommissionDataGrp maybe used to include the detail splits provided the commission is of the same commission basis type. For example, CommissionData may contain CommType(13) of 3 (Absolute) and a Commission(12) value of "15". CommissionDataGrp may be used to show how this Commission(12) value of "15" is split up as long as the CommissionBasis(2642) is also 3 (Absolute) for each of the instances added together. This method of aggregated commission data may also be applied to this component to provide a total when the instances of the detail splits in CommissionDataGrp contain leg level information (indicated by the usage of CommissionLegRefID(2649) in CommissionDataGrp). Note that it is only possible to aggregate values for a single commission basis type.
|
| 66 | ListID | ListID |
optional |
SYNOPSIS:
Unique identifier for list as assigned by institution, used to associate multiple individual orders. Uniqueness must be guaranteed within a single trading day. Firms which generate multi-day orders should consider embedding a date within the ListID field to assure uniqueness across days.
|
| 421 | Country | Ctry |
optional |
SYNOPSIS:
ISO Country Code in field
|
| 54 | Side | Side |
optional |
SYNOPSIS:
Side of order (see Volume : "Glossary" for value definitions)
|
| 44 | Price | Px |
optional |
SYNOPSIS:
Price per unit of quantity (e.g. per share)
|
| 423 | PriceType | PxTyp |
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.
|
| 406 | FairValue | FairValu |
optional |
SYNOPSIS:
Used in EFP trades
|
| 430 | NetGrossInd | NetGrossInd |
optional |
SYNOPSIS:
Code to represent whether value is net (inclusive of tax) or gross.
|
| 63 | SettlType | SettlTyp |
optional |
SYNOPSIS:
Indicates order settlement period. If present, SettlDate (64) overrides this field. If both SettlType (63) and SettDate (64) are omitted, the default for SettlType (63) is 0 (Regular)
Regular is defined as the default settlement period for the particular security on the exchange of execution.
In Fixed Income the contents of this field may influence the instrument definition if the SecurityID (48) is ambiguous. In the US an active Treasury offering may be re-opened, and for a time one CUSIP will apply to both the current and "when-issued" securities. Supplying a value of "7" clarifies the instrument description; any other value or the absence of this field should cause the respondent to default to the active issue.
Additionally the following patterns may be uses as well as enum values
Dx = FX tenor expression for "days", e.g. "D5", where "x" is any integer > 0
Mx = FX tenor expression for "months", e.g. "M3", where "x" is any integer > 0
Wx = FX tenor expression for "weeks", e.g. "W13", where "x" is any integer > 0
Yx = FX tenor expression for "years", e.g. "Y1", where "x" is any integer > 0
Noted that for FX the tenors expressed using Dx, Mx, Wx, and Yx values do not denote business days, but calendar days.
|
| 64 | SettlDate | SettlDt |
optional |
SYNOPSIS:
Specific date of trade settlement (SettlementDate) in YYYYMMDD format.
If present, this field overrides SettlType (63). This field is required if the value of SettlType (63) is 6 (Future) or 8 (Sellers Option). This field must be omitted if the value of SettlType (63) is 7 (When and If Issued)
(expressed in local time at place of settlement)
|
| 336 | TradingSessionID | SesID |
optional |
SYNOPSIS:
Identifier for a trading session.
A trading session spans an extended period of time that can also be expressed informally in terms of the trading day. Usage is determined by market or counterparties.
To specify good for session where session spans more than one calendar day, use TimeInForce = 0 (Day) in conjunction with TradingSessionID(336).
Bilaterally agreed values of data type "String" that start with a character can be used for backward compatibility.
|
| 625 | TradingSessionSubID | SesSub |
optional |
SYNOPSIS:
Optional market assigned sub identifier for a trading phase within a trading session. Usage is determined by market or counterparties. Used by US based futures markets to identify exchange specific execution time bracket codes as required by US market regulations. Bilaterally agreed values of data type "String" that start with a character can be used for backward compatibility
|
| 58 | Text | Txt |
optional |
SYNOPSIS:
Free format text string
(Note: this field does not have a specified maximum length)
|
| 354 | EncodedTextLen | EncTxtLen |
optional |
SYNOPSIS:
Byte length of encoded (non-ASCII characters) EncodedText (355) field.
|
| 355 | EncodedText | EncTxt |
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.
|