cover image: Participant Build Pack 2 - Interface Definitions v 3.4 (Clean

20.500.12592/z08kw4n

Participant Build Pack 2 - Interface Definitions v 3.4 (Clean

24 Mar 2024

Transaction None acknowledgment specific event codes A Change Response is sent to the Market Participant who submitted the Initiate Transfer Request to indicate that the transfer request is in progress for the Supply Point. [...] Following the processing of the request, AEMO issues notifications to other Organisations assigned to a role for the Change Request and sends an update response to the Market Participant (New FRO) who issued the original Change Request. [...] RequestID M The unique ID assigned by AEMO to the Change Request ChangeStatusCode M The current status of the Change Request ChangeReasonCode M From change request ProposedDate M From change request NMI M From change request checksum M An attribute of NMI 4.1.11 Delivering Problem Notice The Problem Notice described in this section is responsible for conveying change information to the Market Part. [...] The sender of the Problem Notice may include whatever text they like in the Event associated with the notice and AEMO will pass the Event unaltered to the New FRO. [...] The reason AEMO issues a Problem Notice on receipt of a NAK generated against a CATSNotification is it is the only mechanism available to a Current FRO and Distributor AEMO | Doc Ref: 305183 | 1 May 2024 Page 61 of 158 Participant Build Pack 2 such that it can provide feedback about a problem to the New FRO without knowing the identity of the New FRO.

Authors

megan.torrens

Pages
158
Published in
Australia