The ‘Economic Activity Indicator’ codes currently defined in Ver 4.1 of Data Codes include a mixture of 2, 3 and 4 digit codes. While continuing to base the codes on the NACE standard it is proposed to make the following…
Read MoreVer 4.1 of the Message Data Structures defines ‘Title’ as a CHAR (4) field with no defined list of allowable codes. It is proposed to define the following set of allowable codes for the ‘Title ‘field. Click here to view…
Read MoreMPD 23 – Supplier Data Requests currently allows for the requesting and sending of refresh messages. These messages are also catered for in the Market Messages database V 4.1 and the XML schema. Following a review of the design ESB…
Read MoreIt is proposed to make Economic Activity Indicator mandatory on 010 message in defined circumstances (ie sites where MIC > 30kva). An invalid value or blank value (for sites where MIC > 30kva) on the 010 message will be rejected…
Read MoreSuppliers will be allowed to make appointments for the following Call Types • Re-Energise • Re-Energise NPA • Exch from D/T to S/T • Exch from ST to D/T • Remove NSH MT & T/S • Install Token Meter •…
Read MoreProposing to change the optionality of the Market Participant Business reference field on the 331 Message – QH Meter Technical Details message from mandatory to optional field Click here to view document.
Read MoreMM 111 Registration Cancellation confirms a cancellation on an MPRN to both the Old and New Suppliers . This DR proposes that the existing message with all the fields populated is sent to the New Supplier but the Old Supplier’s…
Read MoreDetail of Change Request This DR proposes to make fields on the 105 Change of Supplier Confirmation message optional so that the proposed existing version would go to the New Supplier , but that only the following fields are populated…
Read MoreEach of the market messages contains a field called Message Type in the header. Message 114 contains a second field called ‘Message Type’ (to indicate whether the message is a response or an advice). It is proposed to rename this…
Read MoreAggregation Messages – 501, 501S, 505, 505S The first Additional Aggregation segment in messages 501, 501S, 505 and 505S should be documented as level 4. second Additional Aggregation segment in messages 501, 501S, 505 and 505S should be documented as…
Read MoreAmend 501 message to include total EUF by profile and timeslot and the count of MPRNs used in Aggregation run Input file for aggregation run to be available on request. Format (probably CD) to be determined at later date Click…
Read MoreChanges to cardinality on 501 • Aggregation Consumption Level 4 should have cardinality of 1..N not 1 Changes to cardinality on 505 • Additional Aggregation Information Level 5 should have cardinality of 0..N not N0..N Click here to read the…
Read MoreNew code to be added to field ‘Rejection Reason’ for use on 101R New Registration Rejection and 102R: Change of Supplier – Registration Rejection messages • IGA: Invalid/Missing GUAC ‘Objection Reason’ code defined for use on Message 012: Notification of…
Read More