FIX TAG 515
ExecValuationPoint
Definition
For CIV - a date and time stamp to indicate the fund valuation point with respect to which a order was priced by the fund manager.
Compare versions
Differences between the selected source snapshots, including wording and errata; not a migration guide.
FIX 4.4 FIX 5.0 SP2
Definition text changed
FIX 4.4
For CIV - a date and time stamp to indicate the fund valuation point with respect to which an order was priced by the fund manager.
FIX 5.0 SP2
For CIV - a date and time stamp to indicate the fund valuation point with respect to which a order was priced by the fund manager.
No enumerated values are defined for this field in this source.
About the UTCTimestamp data type
string field representing Time/date combination represented in UTC (Universal Time Coordinated, also known as "GMT") in either YYYYMMDD-HH:MM:SS (whole seconds) or YYYYMMDD-HH:MM:SS.sss (milliseconds) format, colons, dash, and period required. Valid values:
- YYYY = 0000-9999, MM = 01-12, DD = 01-31, HH = 00-23, MM = 00-59, SS = 00-60 (60 only if UTC leap second) (without milliseconds).
- YYYY = 0000-9999, MM = 01-12, DD = 01-31, HH = 00-23, MM = 00-59, SS = 00-60 (60 only if UTC leap second), sss=000-999 (indicating milliseconds).
Leap Seconds: Note that UTC includes corrections for leap seconds, which are inserted to account for slowing of the rotation of the earth. Leap second insertion is declared by the International Earth Rotation Service (IERS) and has, since 1972, only occurred on the night of Dec. 31 or Jun 30. The IERS considers March 31 and September 30 as secondary dates for leap second insertion, but has never utilized these dates. During a leap second insertion, a UTCTimestamp field may read "19981231-23:59:59", "19981231-23:59:60", "19990101-00:00:00". (see http://tycho.usno.navy.mil/leapsec.html)
Used in messages 1
Includes nested components and repeating groups. Open a location to see its surrounding requirements.
35=8ExecutionReportMessage body