Short Code and Algo ID Solution 2.0
Short Code and Algo ID Solution 2.0
The following enhancements will be introduced in Short Code and Algo ID Solution 2.0:
- First-In-First-Out (FIFO) principle and intraday processing, adapted upload files and T7 XML Member Reports (TR160-TR163)
- The Short Code and Algo ID upload GUI (Graphical User Interface) and Common Upload Engine (CUE) enhancements
- Facilitating a correction functionality for historical (older than the past trading day) Short Code data submissions of Trading Participants to the trading venue
Simulation start: 09 September 2024
Production start: 18 November 2024
Participants Requirements
Feature/Enhancement | Details | Action Item |
First-In-First-Out (FIFO) principle and intraday processing, adapted upload files and T7 XML Member Reports (TR160-TR163) | The data processing will be adapted from Last-in-first-out (LIFO) principle to the FIFO principle to allow for orderly intraday processing of Trading Participant´s uploads. The intraday processing enables Trading Participants to ensure that data submissions are processed during the day and feedback about the validation results is provided back in the Reports TR160-TR163 in due course. | Trading participants need to adjust to FIFO principle and perform sufficient testing. |
Introduction of new intraday version of T7 XML Member Reports (TR160-TR163) | There will be three new intraday versions of the reports that will be provided in addition to the existing end-of-day report versions. | Trading participants can make use of intraday versions of these reports to speed up the error handling on their side during the day. |
The Short Code and Algo ID upload and GUI (Graphical User Interface) enhancements | The Short Code and Algo ID upload GUI will provide the T7 XML Member Reports TR160-169 for download. | Trading participants who want to make use of this enhancement can download T7 XML Member Reports TR160-169. |
Common Upload Engine (CUE) enhancement | CUE will be enhanced with respect to the file name and processing. The file reject in case of erroneous data records is withdrawn, files will be transferred to the data warehouse and results are provided in the error reports, CUE will automatically apply the versioning and add a timestamp to the file name. | Trading participants are not required to correct erroneous records for a successful file submission. The CUE log file will still be provided but there is no immediate action required. Trading participants can wait for the full validation in the data warehouse and the final results in the XML reports. However, CUE rejects files with wrong file naming or structural errors. Trading participants also need to consider and adapt to the file name changes. Moreover, each trading participant can consider a timestamp in the file for the conciseness. |
Facilitating a correction functionality for ongoing and historical (older than the past trading day) Short Code data submissions of Trading Participants to the trading venue | Ongoing corrections: Historical corrections: | Trading participants that need to perform ongoing corrections must consume this report. |
Upload file changes | The structure of upload files for Short Codes and Algo IDs is changed to reflect the enhancements in the data processing. | Trading participants need to consider the structural changes while creating the upload file. |