MSB (55 / 54)
E_0250 — Check order issuance for metering location change
Check order issuance for metering location change
| Attribute | Value |
|---|---|
| Designation | Check order issuance for metering location change |
| Market role | MSB |
| Regulatory determination / chapter | MaBiS |
| Section | 7.76.1: AD: Metering location change from LF to MSB |
| Check identifiers | Response: 19005, 19006 |
| EBD version | 4.3 |
| As at | — |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 10 | Is the LF assigned to the market location of the specified location in the requested implementation period? | no | → Step 20 | — |
| — | — | yes | → Step 40 | — |
| 20 | Does MSB have a power of attorney from the final consumer or producer? | no | A03 | Cluster: Rejection No power of attorney from the final consumer or producer is available. |
| — | — | yes | → Step 30 | — |
| 30 | Is the power of attorney plausible and valid? | no | A04 | Cluster: Rejection Power of attorney is not plausible and valid. |
| — | — | yes | → Step 40 | — |
| 40 | Is the requested change date at least 20 WT after the message receipt date? | no | A01 | Cluster: Rejection Deadline not met |
| — | — | yes | A02 | Cluster: Consent The change can be carried out. |
Result codes
| Result code | Cluster | Meaning | Response check identifier |
|---|---|---|---|
A03 | Rejection | No power of attorney from the final consumer or producer is available. | 19006 |
A04 | Rejection | Power of attorney is not plausible and valid. | 19006 |
A01 | Rejection | Deadline not met | 19006 |
A02 | Consent | Change can be carried out. | 19005 |
Notes on this page
Role of the numbers: »response« are the check identifiers that list this tree in the ebd_code column of the check identifier table (knowledge-collection · FV 202610); »checked« is the difference set to it from the return path of the process steps. The »response check identifier« column of the result codes assigns a cluster only because this tree carries exactly one checked message and exactly one response per pole; their pole comes from the use case title of the response.
Not checked against a process
No consistency check was carried out for this decision tree — no generated BPMN found. Whether the MACO APP implements this tree completely is therefore not evidenced here.