Eurex
Dear customer,
With this Newsflash we would like to inform you about known limitations to the new Short Code and Algo ID solution 2.0 and implications for the RRS Release 1.4 ahead of the production start on Monday, 18 November 2024. More information about the implementation dates will be provided in due course.
A. Short Code and Algo ID solution 2.0
Non-uniqueness – warning in TR160 “Short Code ID – Error Report”
The error code 25 “ClientLongValue already registered”, will not be provided as a warning in TR160 “Short Code ID – Error Report” for a registration or a modification of a non-unique Short Code combination. The TR167 “Short Code ID – Non-Uniqueness Report“ is not affected. Trading Participants shall consult this report in order to assess whether a registration or modification led to a non-unique Short Code registration.
Common Upload Engine (CUE) – error message timestamp
Short Code file uploads (CUE service “EXTREFDA”) and Algo ID uploads (CUE service “EXTALGO1”), which will be rejected due to non-compliance with the file naming convention, i.e. a wrong upload date, will receive the CUE feedback “_WRONG_UPLOAD_DATE” as a file suffix without a timestamp. Other CUE error and success messages are not affected.
Please refer to the updated documentation “SCLC 2.0 - Reporting handbook for audit trail and other regulatory reporting under the MiFID II/MiFIR regime – Version 4.3” and the “SCLC 2.0 - CUE validation and file specification Short Code ID and Algo ID – Version 2.1” available on the Eurex website www.eurex.com under the following paths:
Rules & Regs > Regulations > MiFID II/MiFIR > Client & Member Reference Data
Support > Initiatives & Releases > Readiness for projects > Short Code and Algo ID Solution 2.0
B. RRS Release 1.4
In order to comply with the requirements of Transaction Reporting according to Art. 26 (5) MiFIR, Trading Participants not subject to MiFIR ("Non-MiFIR Trading Participants") are requested to undertake a detailed review of the RRS Trade Venue Extract File (TVEXT) in the Common Report Engine (CRE). The objective of this review is to ascertain whether the registered Short Code combinations, which were automatically incorporated are accurate and, if required, to submit any corrections via the upload functionality in the Common Upload Engine (CUE).
Further information about the RRS Release 1.4 can be found on the Eurex website under the following path:
Support > Initiatives & Releases > Readiness for projects > Regulatory Reporting Solution 1.4 for non-MiFIR firms
If you have any further questions or comments, please do not hesitate to contact your Key Account Manager or send an email to client.services@eurex.com.
Kind regards,
Your Client Services Team
Visit now Eurex Support Trading to access a wide array of support content!
Recipients: | All Trading Participants of Eurex Deutschland and Vendors | |
Target groups: | Front Office/Trading, Middle + Backoffice, IT/System Administration, Auditing/Security Coordination | |
Related circulars: | Eurex Circulars 054/24, 063/24, 084/24 | |
Related newsflashes: | Eurex Readiness Newsflashes from 14 October 2024, 16 October 2024 | |
Contact: | client.services@eurex.com | |
Web: | Support > Initiatives & Releases > Readiness for projects > Short Code and Algo ID Solution 2.0 Support > Initiatives & Releases > Readiness for projects > Regulatory Reporting Solution 1.4 for non-MiFIR firms Rules & Regs > Regulations > MiFID II/MiFIR > Client & Member Reference Data |
Market Status ⓘ
XEUR
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 Eurex webpage under Support --> Emergencies and safeguards. 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.
An instant update of the Market Status requires an enabled up-to date Java™ version within the browser.