Why has the CpML UTI character format been increased to 100 characters?

Why has the CpML UTI character format been increased to 100 characters?

The CpML UTI character format has been increased from 52 to 100 characters as a result of a recent implementation by EPEX Spot.

However, the 100 character UTI format was actually in place from the launch of REMIT (TRUM Page 62) but at the time Equias took the decision to keep the CpML as a universal standard, 52 characters, as defined by ESMA for EMIR.

Following the recent Equias UAT and Production CMS release (February 2018), it is important that organisations that use eCM also apply the patch because if one of their counterparties applies the new patch and creates a UTI that is more than 52 characters and the other organisation does not, this will prevent the CMS sending successful box results.

As successfully sending the box result is part of the eCM process, the trade will then get stuck in RECEIVING and the match will not happen.
    • Related Articles

    • Is the UTI field case sensitive? And if so why?

      ESMA does not state if the UTI field is case sensitive while ACER explicitly say that it is case sensitive. Equias have implemented case sensitivity on the UTI field since that is the broadest definition and does not contravene any rule set out by ...
    • Why are all delivery points included in CpML enrichment?

      Users of the CMS have a few options when using the market in CpML: Include their own data in the FinancialDelvieryInformation section in the input CpML; or Omit this section from the input CpML file they send to eRR, in which case eRR will enrich the ...
    • If Submitting an ActionType Error in CpML why does the REMIT Transaction Screen show two lines?

      This is due to the process logic. If a CpML for REMIT T1 is sent, a T1 file is generated in a first step, mapped on the basis of the input CpML. If you have ActionType 'N'ew in the input CpML, only one record is created. But if you submit ActionType ...
    • What is a Document ID and how should we create it?

      Please refer to the eCM Standard located on the homepage of the Users Area, "6.1 Naming and Typing Conventions": 6.1.2 - Document IDs Often, documents are listed in reporting tools, as XSL stylesheets, etc. To provide a common syntax that is ...
    • My Uploaded T1 trade shows as Source as OMP but I'm an MP

      Trades uploaded in ACER Table1 Format (ACER.xml) format can only be uploaded as an OMP when an OMP is involved. To enable MP's to upload their data without involvement of an OMP we define MP's as Pseudo OMP's to allow ACER Table 1 uploads, e.g. if ...