A member of
Eurex
1. Introduction
Following feedback from Trading Participants, the Management Board of Eurex Deutschland has decided to continue to allow the modification of validly registered short code-long code mappings where the ValidFromDate is in the past or is the trading date of upload.
This reverses the decision communicated in Eurex Circular 082/22 to technically disable the processing of short code-long code mappings where the StatusIndicator is M (“Modification”) and the ValidFromDate is “T-1” or “T,” with T being the trading date of the upload.
All other changes to the short code-long code processing described in Eurex Circular 082/22 will be implemented in production as announced.
Simulation start: In approximately 10 business days from the date of publication of this Eurex Circular; Simulation availability will be announced via Newsboard message.
Production start: 21 November 2022
2. Required action
Please retrieve your functional and technical documentation from the Eurex website www.eurex.com.
Functional documentation is available in the updated reporting handbook “Information handbook for audit trail, transaction and other regulatory reporting under the MiFID II/MiFIR regime” available under:
Rules and Regs > MiFID II/MiFIR > Reporting
Technical documentation is available under:
Support > Initiatives & Releases > T7 Release 11.0
Trading Participants are asked to change their processing logic accordingly and to test their implementation in Simulation.
3. Details of the initiative
With T7 Release 11.0, uploads of short code-long code mappings with StatusIndicator M and ValidFromDates T-1 or T will be accepted.
This means that the accepted ValidFromDates for each StatusIndicator will be as follows:
ValidFromDate, T = trading date of upload | ||||||
StatusIndicator | T-2 or further in the | T-1 | T | T+1 | T+2 or further in the future | |
N | New Registration | X | Accepted | Accepted | Accepted | X* |
M | Modification | X | Accepted | Accepted | Accepted | X* |
D | Deletion | X | X* | X* | Accepted | X* |
X = rejection of mapping; * = changes with T7 Release 11.0
For clarity, the deletion of short code-long code mappings retroactively or intraday will still be technically disabled with T7 Release 11.0. This means that all uploads of short code-long code mappings with StatusIndicator D (“Deletion”) where the ValidFromDate is set to T-1 or T, with T being the trading date of the upload, will be rejected in report TR160 with Error Code 27 “Retroactive or intraday changes are not permitted.”
Further information
Recipients: | All Trading Participants of Eurex Deutschland and Vendors | |
Target groups: | Front Office/Trading, Middle + Backoffice, IT/System Administration, Auditing/Security Coordination | |
Contact: | Your Key Account Manager or client.services@eurex.com; for regulatory questions eurex.reg.reporting@eurex.com; for technical questions your Technical Key Account Manager or cts@deutsche-boerse.com | |
Related Eurex Circular: | Eurex Circular 082/22 | |
Web: | www.eurex.com | |
Authorized by: | Michael Peters |
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.