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

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 ESMA or ACER.

    • Related Articles

    • FixedOrFloating aggregation key field

      For FixedOrFloating aggregation key field to be ‘Fixed’ all elements of the trade need to be fixed. This can be categorized as below: • TransactionTypoe = “FOR” then use “Fixed” • TransactionTypoe = “PHYS_INX” then use “Float” • TransactionTypoe = ...

    • 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 ...

    • Is Total Contract Value a matching field?

      On 16 June 2014 Equias asked the eCM community for feedback regarding issues in matching the 'Total Contract Value' field. It was decided by democratic vote that it will be removed from the matching criteria and set to an information ONLY field The ...

    • What value should you use for the field "Contract Capacity"?

      The EFET eCM Standard states that the 'Contract capacity' field is Mandatory for all trades submitted with section TIME INTERVAL QUANTITIES (1-N). The 'Contract Capacity' is "the contract capacity of the commodity that has been negotiated". The field ...

    • Is the 'Order Number' a mandatory field in all XML trade confirmations?

      The eCM Standards 4.4 state: Order Number Conditional If ‘TransactionType’ is a ‘Financial Transaction’, or “PHYS_INX” or “OPT_PHYS_INX” then this field: a) is Mandatory and Key if the deal has an Order Number otherwise b) must be omitted This means, ...