How to track a message through the KOR SDR service?
In order to ensure timely processing and reporting of KOR SDR processing & compliance functions, the system captures and uses a number of timestamps & indicators.
Note on formats:
- All KOR Timestamps use ISO 8601 YYYY-MM-DDThh:mm:ssZ, based on UTC.
- Time duration fields use ISO 8601 P1Y1M1DT1H1M1.1S.
- Indicators use boolean True/False.
Please see below for format details.
Fields listed below can be accessed through message details and on message reports. Below are a summary of relevant processing timestamps and indicators:
| Timestamp / Indicator | Category | Source | Definition | |||
| Tracking submissions | ||||||
| Execution Timestamp | Transaction Related | Supplied in client's message. | Supplied in client's message. Date and time a transaction was originally executed, resulting in the generation of a new UTI. This data element remains unchanged throughout the life of the UTI and is used in a number of required timestamp calculations. | |||
| Message Required Submission Calculation | Compliance | KOR derived |
Calculated time duration of how long KOR identified as time to report. Transactions Message values
Public Message values
Valuation Message values
|
|||
| Message Required Submission Timestamp (link) | Compliance | KOR calculated | KOR SDRs calculation of when the message is required to be reported. This is [Execution Timestamp] plus [Message Required Submission Calculation] | |||
| Message Submitted Timestamp | Compliance | KOR derived | Actual date and time of the submission of the report to the trade repository. | |||
| Message Submission Late Indicator (link) | Compliance | KOR calculated |
Based on KOR's value in the field: Message Required Submission Timestamp, once the submission passes all validations, then KOR shall evaluate if the message was submitted late or not. If [Message Submitted TS]<[Message Required Submission TS] then False, else True |
|||
| Message Submission Late Duration (link) | Compliance | KOR calculated | When [Message Submission Late Indicator] is True, then calculate duration of [Message Submitted TS] - [Message Required Submission TS] | |||
| Tracking dissemination | ||||||
| Scheduled Dissemination Timestamp | Dissemination Related | KOR calculated | Date and time, to the nearest second, that an SDR plans to publicly disseminates, as defined in § 43.2. This is calculation uses [Execution Timestamp] and ..... | |||
| Dissemination Timestamp | Dissemination Related | KOR derived | Date and time, to the nearest second, that an SDR actually publicly disseminates, as defined in § 43.2. | |||
| KOR Disseminated Timely Indicator | Compliance | KOR calculated | If KOR disseminated the message in accordance with regulations. Set to True if [Dissemination TS] is within 1 min of [Scheduled Dissemination TS], else False | |||
| Tracking processing | ||||||
| Message Processed Timestamp | TR | KOR derived | Date and time KOR SDR completed processing of the submission. Stamped when KOR stops processing so it does vary depending on whether a message is validated, rejected and/or disseminated. | |||
| Message Processing Duration | Compliance | KOR calculated | How long KOR took to fully process a message: [Message Processed TS]-[Message Submitted TS] | |||
Timestamp format
In alignment with the CDE, KOR only accepts timestamps in the format of YYYY-MM-DDThh:mm:ssZ, based on UTC.
ISO 8601 is an international standard covering the worldwide exchange and communication of date and time-related data. It is maintained by the Geneva-based International Organization for Standardization (ISO)
- YYYY-MM-DDThh:mm:ssZ, based on UTC
- YYYY = four-digit year
- MM = two-digit month (01=January, etc.)
- DD = two-digit day of month (01 through 31)
- hh = two digits of hour (00 through 23) (am/pm NOT allowed)
- mm = two digits of minute (00 through 59)
- ss = two digits of second (00 through 59)
- Times are expressed in UTC (Coordinated Universal Time), with a special UTC designator ("Z").
Duration format
Durations define the amount of intervening time in a time interval and are represented by the format P[n]Y[n]M[n]DT[n]H[n]M[n]S or P[n]W as shown on the aside. In these representations, the [n] is replaced by the value for each of the date and time elements that follow the [n]. Leading zeros are not required, but the maximum number of digits for each element should be agreed to by the communicating parties. The capital letters P, Y, M, W, D, T, H, M, and S are designators for each of the date and time elements and are not replaced.
- P is the duration designator (for period) placed at the start of the duration representation.
- Y is the year designator that follows the value for the number of calendar years.
- M is the month designator that follows the value for the number of calendar months.
- W is the week designator that follows the value for the number of weeks.
- D is the day designator that follows the value for the number of calendar days.
- T is the time designator that precedes the time components of the representation.
- H is the hour designator that follows the value for the number of hours.
- M is the minute designator that follows the value for the number of minutes.
- S is the second designator that follows the value for the number of seconds.
For example, "P3Y6M4DT12H30M5S" represents a duration of "three years, six months, four days, twelve hours, thirty minutes, and five seconds".
Date and time elements including their designator may be omitted if their value is zero, and lower-order elements may also be omitted for reduced precision. For example, "P23DT23H" and "P4Y" are both acceptable duration representations. However, at least one element must be present, thus "P" is not a valid representation for a duration of 0 seconds. "PT0S" or "P0D", however, are both valid and represent the same duration.