At present, the rejection reason IID (invalid/incomplete data) is widely used throughout the Retail Electricity Market. This covers a range of processes including: • New Connections • Change of Supplier • CoLE • Change of Customer Details • Meter Works…
Read MoreRevert to SOLR” MPD 4 covers SPU but not Grouped Unmetered. The SOLR process in Supply depends on receiving MM 105 to trigger the CoS Gain workflow. As there is no such message associated with Grouped Unmetered, because it is…
Read MoreIn scenarios where the COS process for a QH customers is delayed because of an outstanding connection agreement, the effective from date gets pushed back until the connection agreement is resolved. Click here to read the document.
Read MoreThe transaction charge for a job should only become eligible for inclusion in the next Networks Transaction Charges Invoice after the job completion market message, or e-mail, has issued to the Supplier. At present the charge is created in Networks…
Read MoreSuppliers to receive communication advice from DSO where DSO have special needs details on record which the supplier may not have any record of e.g special needs field on MM010 is blank however DSO has a record of special needs…
Read MoreChange of usage details to be included in Message 114 rather than just a flag. This change should be made for market opening. Click here to read the document.
Read MoreThe due date of the aggregated invoice should be included in the header of the detailed flat file Click here to read the document.
Read MoreProfile should be added to Market Message 114 Click here to read the document.
Read MoreWe request clarification on MARKET MESSAGE 105 optionality for issue to the new supplier regarding Medical needs and specials needs. At present in the market message it is described as ‘’see description’’ We seek this information to be automatically provided…
Read MoreAdd new field with associated data codes to the 332 & 331 messages to flag the reason why the message is being sent. Click here to read the document.
Read MoreSuppliers wishing to notify ESB Networks of a potential problem at an unmetered site should use the market messages and processes as defined to support metered sites i.e. MPD 12. Section 3.1 of this MPD should be updated as follows:…
Read MoreAt present the Market Messages Database (ver 4.1) contains the contents of Message 506 (DUoS Charges per MPRN). As this is no longer proposed to be a Market Message sent in XML format the structure will be removed from the…
Read More