Question 2.1.52 Extra field in the schema

Sections

Question 2.1.52 Extra field in the schema

MPs are required to bid the capacity based on the units (unit based bidding) in specific auction and continuous markets in the European Union. Could the Agency provide guidance on reporting of potentially useful information in particular unit information related to unit based bidding records of transactions including orders to trade?


Answer

In the Agency’s view, the reporting parties shall use the “Extra” field in schema REMITTable1_V1.xsd or REMITTable1_V2.xsd and report the local unit ID codes in case of unit based bidding in both trade and order reports in applicable continuous (Contract type = CO) and auction markets (Contract type = AU).

In order to correctly map the information, the type of data to be reported is: ASSETIDSTRING

 

Example of Spanish auction and continuous markets: Unit ID code (Spain) - >ABESC01->

BidUnitID=ABESC01

Schema Table 1_V1:

            <Extra>BidUnitIDABESC01Yes</Extra>

 

             Schema Table 1_V2:

          <Extra>BidUnitIDABESC01==Yes;BidUnitIDABESC01==Yes</Extra>

 

Example of Portuguese auction and continuous markets: Unit ID code (Portugal)- >EGPPCX2 -> BidUnitID=EGPPCX2

 

             Schema Table 1_V1:

            <Extra>BidUnitIDEGPPCX2Yes</Extra>

 

             Schema Table 1_V2:

            <Extra>BidUnitIDEGPPCX2==Yes;BidUnitIDEGPPCX2==Yes</Extra>

 

Example of Irish auction and continuous markets: Unit ID code (Ireland) -> GU_400930-> BidUnitID=GU400930

             Schema Table 1_V1:

             <Extra>BidUnitIDGU400930Yes</Extra>

 

             Schema Table 1_V2:

             <Extra>BidUnitIDGU400930==Yes;BidUnitIDGU400930==Yes</Extra>

 

Example of Italian auction and continuous markets: Unit ID code (Italy) -> UP_VALMALENCO_1-> BidUnitID=UPVALMALENCO1

              Schema Table 1_V1:

               <Extra>BidUnitIDUPVALMALENCO1Yes</Extra>

 

              Schema Table 1_V2:

               <Extra>BidUnitIDUPVALMALENCO1==Yes;BidUnitIDUPVALMALENCO1==Yes</Extra>

Note: Unit ID code should respect XSD constraints in regard to the character set allowed and should not contain particular prefix and suffix strings mentioned in the examples above (such as “BidUnitID”, “Yes “ and “==Yes “) nor separator (“-“,”_”, “ “..) or special characters (@, *,…).

In case additional tags, proposed by the Agency (such as “FullSet” tag), are reported in the Extra field they should be combined respecting XSD constraints.

Updated: 
30/06/2020