7.4 Data fields for identification of location and market participant

This section includes the following fields:

_{M = mandatory; O = optional; - = does not apply; * = conditionally required; DV = default value specified in TRUM}

Data Field (22) Network point identification

This field identifies the network point to which the allocated capacity refers to. The identification of the network point occurs via the indication of the EIC code (type Y, Z or W). For the validity of the EIC code adopted, reporting parties are invited to refer to the identification code registry provided by ENTSO-E^[1]. In the schema, this field requires the indication of the coding scheme attribute as well. For EIC codes, the coding scheme attribute shall be equal to “305”.

The field is mandatory for primary and secondary allocations.

This field corresponds to the field PROCESS_TRANSACTION.CONNECTIONPOINT.IDENTIFICATION – CODINGSCHEME in the schema.

Data Field (23) Bundling

This field is represented in the EDIGAS schema as “CapacityType.CODE” and the code for “bundled” is “ZEO” and that for unbundled is “ZEP”.

This field is mandatory for allocations occurring via auctions (primary allocations and secondary if occurred via auctions).

This field corresponds to the field PROCESS_TRANSACTION.CAPACITYTYPE.CODE in the schema.

Data Field (24) Direction

This field specifies the direction of the transportation capacity in relation to the transmission system operated by the responsible TSO reported in Data Field (25). The TSO sells capacity with a direction in both bundled and unbundled capacity.

This field is mandatory for primary and secondary allocations.

This field corresponds to the field DIRECTION.CODE in the schema.

Data Field (25) TSO 1 identification

This field identifies the responsible TSO for the allocated capacity. In case of primary allocations, this field indicates the TSOs on whose behalf the data reporting is made.

The responsible TSO shall be identified by a unique identification code, either ACER code or EIC code.

In the schema, this field requires the indication of the coding scheme attribute as well. For EIC codes, the coding scheme attribute shall be equal to “305”. For ACER codes, it shall be equal to “ACE”.

The identifier reported in this field shall correspond to the relevant one listed in CEREMP.

The field is mandatory for primary and secondary allocations.

This field corresponds to the field PROCESS_TRANSACTION.RESPONSIBLETSO_MARKETPARTICIPANT.IDENTIFICATION – CODINGSCHEME in the schema

Data Field (26) TSO 2 identification

This field is mandatory for primary allocations if Data Field (23) is filled in with ZEO, i.e. only in case of allocation of bundled capacity. For secondary allocations of bundled capacity, this information shall be included if available to the reporting parties.

TSO 2 shall be identified by a unique identification code, either ACER code or EIC code.

In the schema, this field requires the indication of the coding scheme attribute as well. For EIC codes, the coding scheme attribute shall be equal to “305”. For ACER codes, it shall be equal to “ACE”.

This field corresponds to the field PROCESS_TRANSACTION.ADJACENTTSO_MARKETPARTICIPANT.IDENTIFICATION – CODINGSCHEME in the schema

Data Field (27) Market participant identification

This field identifies the market participant to which the capacity is assigned.

The identification code (i.e. ACER code or EIC X code) reported in this field shall correspond to the code assigned to or provided by the relevant Market Participant in CEREMP as part of its registration under Article 9 of Regulation (EU) No 1227/2011.

In case of primary allocations or allocations occurring via auctions, this field shall be populated also in case of unsuccessful market participants, i.e. those market participants that inserted a bid but did not succeed in getting an allocated capacity.

In case of secondary allocation occurring outside an organised market place, this field shall be populated with the market participant on whose behalf the report is sent. The two legs of those transactions are matched through Data Field (5), i.e. transportation transaction identification.

This field is mandatory for primary and secondary allocations.

In the schema, this field requires the indication of the coding scheme attribute as well. For EIC codes, the coding scheme attribute shall be equal to “305”. For ACER codes, it shall be equal to “ACE”.

This field corresponds to the field PRIMARY_MARKETPARTICIPANT.IDENTIFICATION – CODINGSCHEME in the schema.

Data Field (28) Balancing group or portfolio code

This field is mandatory for both primary and secondary allocations only where balancing group portfolio or accounts apply. Internal account (i.e. identification) of the shipper or the balancing group account (i.e. identification) assigned by the responsible TSO (identified in Data Field (25) TSO 1 Identification) needs to be reported in this field. 

In the schema, this field requires the indication of the coding scheme attribute as well. For a TSO managed code (IS-U code), the coding scheme attribute shall be equal to “ZSO”. For EIC codes, the coding scheme attribute shall be equal to “305”.

This field corresponds to the field PRIMARY_MARKETPARTICIPANT.ACCOUNT.INTERNALACCOUNT in the schema.

[1]https://www.entsoe.eu/data/energy-identification-codes-eic/eic-approved-codes/