7.5 Data fields applicable only for secondary allocations

This section includes the following fields:

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

  Data Field (29) Procedure applicable

This field identifies the specific secondary allocation procedure, and is thus mandatory only in the case of secondary market allocations.

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

Data Field (30) Maximum bid amount

This field indicates the maximum price the transferee is willing to pay when participating to a call for orders procedure. This field is thus mandatory only for “Call for orders” procedure, i.e. when Data Field (29) is populated with A01.

The value reported in this field shall be expressed in the currency reported in Data Field (17) per capacity unit as expressed in data Field (16).

The maximum length of this information is 17 numeric characters (decimal mark included). All leading zeros are to be suppressed.

This field corresponds to the field MAXIMUMBID_PRICE.AMOUNT in the schema.

Data Field (31) Minimum bid amount

This field indicates the minimum price the transferor is willing to accept within a call for orders procedure. This field is thus mandatory only for “Call for orders” procedure, i.e. when Data Field (29) is populated with A01.

The value reported in this field shall be expressed in the currency reported in Data Field (17) per capacity unit as expressed in data Field (16).

The maximum length of this information is 17 numeric characters (decimal mark included). All leading zeros are to be suppressed.

This field corresponds to the field MINIMUMBID_PRICE.AMOUNT in the schema.

Data Field (32) Maximum quantity

This field represents the maximum quantity the transferee/transferor would be willing to acquire/sell when creating the trade proposal within a call for orders procedure. The field is thus mandatory only for “Call for orders”, i.e. when Data Field (29) is populated with A01.

The maximum length of this information is 17 numeric characters (decimal mark included). All leading zeros are to be suppressed. The decimal mark that separates the digits forming the integral part of a number from those forming the fractional part (ISO 6093) shall always be a period (“.”).

All quantities are unsigned values. The value reported in this field shall be expressed in the capacity unit as reported in data Field (16).

This field corresponds to the field MAXIMUMBID_QUANTITY.AMOUNT in the schema.

Data Field (33) Minimum quantity

This field represents the minimum quantity the transferee/transferor would be willing to acquire/sell when creating the trade proposal within a call for orders procedure. The field is thus mandatory for “Call for orders”, i.e. when Data Field (29) is populated with A01. Furthermore, this field it is expected to be populated in the reports for primary capacity allocations occurring via Uniform Price Auction.

This attribute may be used in the case of a secondary market transaction but also in case of primary allocations with uniform price auctions, i.e. when Data Field (9) is populated with “ZSX”.

The maximum length of this information is 17 numeric characters (decimal mark included). All leading zeros are to be suppressed. The decimal mark that separates the digits forming the integral part of a number from those forming the fractional part (ISO 6093) shall always be a period (“.”).

All quantities are unsigned values. The value reported in this field shall be expressed in the capacity unit as reported in data Field (16).

This field corresponds to the field MINIMUMBID_QUANTITY.AMOUNT in the schema.

Data Field (34) Price paid to TSO (Underlying Price)

This field indicates the price paid to the TSO and should be populated only when there is an underlying price to be paid to the TSO in the secondary allocation, e.g. if the Shipper has to pay to the TSO a price in first instance for capacity booking.

The price in this field shall be reported in price per kWh/h expressed in the currency as reported in Data Field (17) Currency.

This field is mandatory if the secondary market procedure is Call for orders, first come first serve, or over the counter, i.e. if Data Field (29) is populated with “A01”, “A02” or “A03”.

The maximum length of this information is 17 numeric characters (decimal mark included). All leading zeros are to be suppressed.

This field corresponds to the field UNDERLYINGTSO_PRICE.AMOUNT in the schema.

Data Field (35) Price the transferee pays to the transferor

This field represents the price the transferee pays to the transferor in the secondary allocation, thus representing the price per unit of measure of the transaction.

This field corresponds to the field transfer_Price.amount in the schema. The price in this field shall be reported in price per kWh/h expressed in the currency as reported in Data Field (17) Currency.

The maximum length of this information is 17 numeric characters (decimal mark included). All leading zeros are to be suppressed.

In addition, the price the transferee pays to the transferor can also be expressed and reported using a price formula or a fixing index. For this purpose, schema element Transfer_PriceFormula shall be used.

This field is mandatory for secondary allocations.

Data Field (36) Transferor identification

This field identifies the market participant that is selling the capacity in the secondary allocation (transferor). The transferor shall be identified by reporting the ACER code or the EIC code (X-type) registered in CEREMP.

This field is mandatory only in the case of secondary allocation.

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 TRANSFEROR_MARKETPARTICIPANT.IDENTIFICATION – CODINGSCHEME in the schema.

Data Field (37) Transferee identification

This field identifies the market participant that is buying the capacity in the secondary allocation (transferee). The transferee shall be identified by reporting the ACER code or the EIC code (X-type) registered in CEREMP.

This field is mandatory only in case of secondary allocation.

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 TRANSFEREE_MARKETPARTICIPANT.IDENTIFICATION – CODINGSCHEME in the schema.