# E_0488 — Check request
Check request
| Attribute | Value |
|---|---|
| Designation | Check request |
| Market role | MSB |
| Regulatory determination / chapter | GPKE |
| Section | 6.12.2: AD: Interruption of grid connection use (disconnect) on the instruction of LF |
| Check identifiers | checked: [17116](/en/schnittstellen/202604/pruefi/ORDERS/PI_17116) · response: [19118](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19118), [19119](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19119) |
| EBD version | 4.2 |
| As at | 2026-06-23 |
## Decision tree
\nDecision tree E_0488: Anfrage prüfen\n\n\n\nE_0488\nAnfrage prüfen\nChecking role: MSB\n\nyes\n\nno\n\nyes\n\nno\n\nyes\n\nno\n\nyes\n\nno\n\n\n1\nHat der MSB die generelle\nZustimmung zur Durchführung\neiner Entsperrung/Sperrung dem\nNB erteilt?\n\n\nA01\nCluster: Consent\nGenerelle Zustimmung des MSB für\ndie Sperrung/Entsperrung liegt vor.\n\n\n2\nLiegt ein Verhinderungsgrund\neiner Sperrung an der\nMarktlokation vor?\n\n\nA02\nCluster: Rejection\nVerhinderungsgrund liegt vor.\nHinweis: Das identifizierte Problem\nist in der\nAntwort zu beschreiben/benennen.\n\n\n3\nLiegen dem MSB technische\nGründe für eine Ablehnung der\nSperrung vor?\n\n\nA03\nCluster: Rejection\nEs liegt ein technischer\nAblehnungsgrund vor.\nHinweis: Das identifizierte Problem\nist in der\nAntwort zu beschreiben/benennen.\n\n\n4\nIst eine Mitwirkung des MSB bei\nEntsperrung/Sperrung vor Ort\ngewünscht?\n\n\nA04\nCluster: Consent\nMSB hat Durchführung der Sperrung\nund Entsperrung unter Mitwirkung\ndes MSB zugestimmt.\n\n\nA05\nCluster: Consent\nMSB hat Durchführung der Sperrung\nund Entsperrung durch NB\nzugestimmt.\n"} kapitel={"GPKE · 6.12.2: AD: Unterbrechung der Anschlussnutzung (Sperren) auf Anweisung des LF"} name={"Anfrage prüfen"} bpmnFv="202604" bpmnCode="E_0488">
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 1 | Has the MSB granted the NB general consent to carry out a reconnection/disconnection? | yes | A01 | Cluster: Consent General consent of the MSB for the disconnection/reconnection is available. |
| — | — | no | → Step 2 | — |
| 2 | Is there a reason preventing a disconnection at the market location? | yes | A02 | Cluster: Rejection There is a reason for prevention. Note: The identified problem must be described/named in the response. |
| — | — | no | → Step 3 | — |
| 3 | Does MSB have technical reasons for a rejection of the disconnection? | yes | A03 | Cluster: Rejection There is a technical reason for rejection. Note: The identified problem must be described/named in the response. |
| — | — | no | → Step 4 | — |
| 4 | Is on-site participation by the MSB in the reconnection/disconnection requested? | yes | A04 | Cluster: consent MSB has consented to the disconnection and reconnection being carried out with the involvement of the MSB. |
| — | — | no | A05 | Cluster: consent MSB has consented to the disconnection and reconnection being carried out by NB. |
## Result codes
| Result code | Cluster | Meaning | Response check identifier |
|---|---|---|---|
| `A01` | Consent | General consent of the MSB for the disconnection/reconnection exists. | [19118](/schnittstellen/202604/pruefi/ORDRSP/PI_19118) |
| `A02` | Rejection | A reason for prevention exists. Note: The identified problem must be described/named in the response. | [19119](/schnittstellen/202604/pruefi/ORDRSP/PI_19119) |
| `A03` | Rejection | A technical reason for rejection exists. Note: The identified problem must be described/named in the response. | [19119](/schnittstellen/202604/pruefi/ORDRSP/PI_19119) |
| `A04` | Consent | MSB has consented to the disconnection and reconnection being carried out with the involvement of the MSB. | [19118](/schnittstellen/202604/pruefi/ORDRSP/PI_19118) |
| `A05` | Consent | MSB has consented to the disconnection and reconnection being carried out by NB. | [19118](/schnittstellen/202604/pruefi/ORDRSP/PI_19118) |
*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 202604); »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.*
:::tip{title="Consistent with the generated process"}
All 5 result codes of the decision tree are contained in the generated process `E_0488.bpmn`.
:::