Market Message Generator

Test cases

MHHS end-to-end scenarios: pick one to build its steps and files.

Or pick a sample message or process from the list on the left.

Process Form

Form changed since this was generated

Settings

Defaults for new forms. Saved in this browser only.

Your Agents

The agents you test with, and their contract references. Message pick-lists take every participant (DIP ID, MPID, role) from the ISD tab. Add a row here for the Metering and Data Services you work with, giving the same role and DIP ID or MPID as in ISD, plus your contract reference.

How it's used: when you pick that participant in a message (e.g. incoming Metering Service), its contract reference is filled in along with its DIP ID and MPID. In ISD shows ✓ when a row matches an ISD participant, ✗ when it doesn't (then its contract reference isn't used).

Use Export / Import to share the list with colleagues.

DIP role	Name	DIP ID	MPID	Contract ref	In ISD

Master Roles ISD entity M18 — DIP Market Roles

The standard list of market roles used on the DIP — what each role code means (e.g. MSS = Metering Service Smart) and its one-letter Market Participant role code, the same code D-flows use (e.g. S for MSS). Taken from the MHHS Industry Standing Data (entity M18).

How it's used: each of Your Agents picks its role from this list. Group sorts roles into Advanced (MSA, ADS), SMART (MSS, SDS, MDR) and Supplier (SUP), so participants can be told apart and grouped. An empty role code means the role has none (N/A).

This is reference data — you rarely need to change it. If something gets edited by mistake, use “Reset to EDI021 master roles”.

DIP role	DIP role description	MP role code	Group

ISD Market participants — ISD entity M16 layout

The market participants in the industry — every company and the role it plays, with its MPID (4 letters, e.g. BGAS, GMTR), company name and DIP ID (10 digits). A company can appear once per role, and any Master Role can be used (Suppliers, Metering and Data Services, LDSOs, REGS …).

How it's used: this is the source for every DIP ID in the messages — Sender, recipients, Suppliers, Metering and Data Services, MDR, LDSO. Pick-lists offer the participants whose role fits the field; type an MPID or name to find one. This mirrors the DIP, which checks every DIP ID / role against ISD. Your Agents adds contract references to the participants you test with.

Real ISD data comes from Elexon as CSV files. Until then, add rows here. Import / Export use the ISD column names (Market Participant ID, DIP Participant ID, DIP Market Role, Company Name), comma- or pipe-separated.

Company name	MPID	DIP role	MP role code	DIP ID

Distributors MPAN distributor IDs — DNOs and IDNOs

Who distributes each MPAN: the first two digits of an MPAN core. A DNO serves one GSP group; an IDNO can operate in any GSP group. Test cases use this to label the GSP group pick-list and to check that an MPAN fits its GSP group and its LDSO.

On the DIP every distributor is an LDSO. Add LDSOs to ISD puts them in the ISD tab (MPID = MPAS ID) so they can be picked; fill in their DIP IDs there. In ISD shows ✓ when the LDSO has a DIP ID, "no DIP ID" when it's in ISD without one, ✗ when it isn't in ISD.

Seeded from your source tables. The current list is published in Market Domain Data (ISD under MHHS): edit rows or import a CSV (Distributor ID, MPAS Operator ID, Type, GSP Group, Region, Name, Licensee).

Distributor ID	MPAS ID	Type	GSP group	Region	Name	Licensee	In ISD

DIP sample messages

Values filled in on every new sample message, so you set them once here instead of in each message.

Environment tag — which DIP environment the message is meant for, e.g. DEV (development), SIT (system integration test), UIT, PRD (production). Schema version — the version of the message format; leave it at 011 unless you're told otherwise.

Environment tag S1.environmentTag

Schema version S0.schemaVersion

You can still change both on any individual message. A message whose format has its own version (IF-051 uses 001) keeps it.

D-flows

Test flag — written in every D-flow header (ZHV), e.g. OPER (operational) or a test flag such as TR06. Used by the Power processes, MCA Migration and the test cases' D-flows.

Test flag ZHV test flag

The Power forms still let you change it on any individual run.