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:
for incurred final missings, which are identified in T7 XML Report TR166 (starting from 18 November 2024 in production), the Trading Participants are required to deliver those Short Code registrations in due course. The overview of those final missings will be provided daily in the new T7 XML Report TR169. 

Historical corrections:
There will be the new reports TR170 and TR171. The content in these reports will be provided with the start of the correction exercise in February 2025. Dedicated publications will follow in due course.

Trading participants that need to perform ongoing corrections must consume this report.
For the correction exercise starting in February 2025, Trading participants can already implement the report structures.
 

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.

Market Status

XETR

-

-

Parts of the trading system are currently experiencing technical issues

The trading system is currently experiencing technical issues

Xetra newsboard

The market status window is an indication regarding the current technical availability of the trading system. It indicates whether news board messages regarding current technical issues of the trading system have been published or will be published shortly.

Please find further information about incident handling in the Emergency Playbook published on the Xetra webpage under Technology --> T7 trading architecture --> Emergency procedures. Detailed information about incident communication, market re-opening procedures and best practices for order and trade reconciliation can be found in the chapters 4.2, 4.3 and 4.5, respectively. Concrete information for the respective incident will be published during the incident via newsboard message

We strongly recommend not to take any decisions based on the indications in the market status window but to always check the production news board for comprehensive information on an incident.


Emergency procedures


An instant update of the Market Status requires an enabled up-to date Java™ version within the browser.