FAQs on transaction reporting – Question III.4.2.3

According to Edig@s MIG for the approved by ACER schema for gas transportation transactions reporting: urn-easee-gas-eu-edigas-remit-gascapacityallocationsdocument-5-1.xsd, the field “PROCESS_TRANSACTION.ACTION_STATUS.CODE”  accepts the following values:

62G = Active.

63G = Cancelled.

66G = Changed.

Definition of element:

Status code of the report to be reported in accordance with current applicable industry standards as specified in gas network code on Interoperability and data exchange.

According to TRUM field (14) Action type, the following codes are permitted:

62G = Active

63G = Cancelled

66G = Changed

Which status is provided to define the field – the status of the reported transaction or the status of the XML file?


Answer:

The element “PROCESS_TRANSACTION.ACTION_STATUS.CODE” is dedicated to define the status of the reported transactions.

RSS_Icon Last update: 26/03/2016  

FAQs on transaction reporting – Question III.4.2.4

Which value should be send to ARIS in case of primary transactions for TRUM field 41 – Bid quantity, if during an auction a minimum value and a maximum value were given by the bidder?


Answer:

The maximum value should be reported for bid quantity.

RSS_Icon Last update: 26/03/2016  

FAQs on transaction reporting – Question III.4.2.5

Price in the secondary Market:

Regarding TRUM v. 2.0 field 35 – Data Field – Price, it is foreseen to include the price concluded in transactions on the secondary market.

TSOs do not have this kind of information as the price is determined in agreements that take place strictly between shippers.

It is important for the TSOs to inform ACER also about these kind of transactions directly to ARIS and not only via booking platforms because these kind of transactions entail changes in contracts which need to be updated?


Answer:

The field 35 is mandatory for secondary market allocations. The reporting obligation for secondary market lies with the market participants. Therefore there should be no problem for the TSOs in case they lack the specific information on the price. In case the TSO acts as the third-party RRM it is the responsibility of the market participant(s) to provide the necessary information to the TSO as the RRM for complete and successful data reporting.

RSS_Icon Last update: 26/03/2016  

RSS_Icon Subscribe to this Category’s RSS