# E_0470 — Check disconnection order
Check disconnection order
| Attribute | Value |
|---|---|
| Designation | Check disconnection order |
| Market role | NB |
| Regulatory determination / chapter | GPKE |
| Section | 6.12.1: AD: Interruption of grid connection use (disconnect) on the instruction of LF |
| Check identifiers | checked: [17115](/en/schnittstellen/202604/pruefi/ORDERS/PI_17115) · response: [19116](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19116), [19117](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19117) |
| EBD version | 4.2 |
| As at | 2026-06-23 |
## Decision tree
\nDecision tree E_0470: Sperrauftrag prüfen\n\n\n\nE_0470\nSperrauftrag prüfen\nChecking role: NB\n\nyes\n\nno\n\nyes\n\nno\n\nno\n\nyes\n\nno\n\nyes\n\nno\n\nyes\n\nyes\n\nno\n\nno\n\nyes\n\nyes\n\nno\n\nyes\n\nno\n\nyes\n\nno\n\nno\n\nyes\n\nno\n\nyes\n\nyes\n\nno\n\nyes\n\nno\n\n\n10\nIst die Marktlokation bereits\ngesperrt?\n\n\nA01\nCluster: Rejection\nMarktlokation ist bereits gesperrt.\n\n\n20\nLiegt für die Marktlokation im\nZeitraum von 6 WT ab dem\nfrühestmöglichen Sperrtermin\nbereits ein Sperrauftrag vor?\n\n\nA10\nCluster: Rejection\nSperrauftrag für Marktlokation liegt\nbereits vor.\n\n\n30\nIst im gesamten\nAusführungszeitraum des\nSperrauftrags (= frühestmöglicher\nSperrtermin bis frühestmöglicher\nSperrtermin + 6 WT) der die\nSperrung beauftragende LF der zu\nsperrenden Marktlokation\nzugeordnet?\n\n\nA11\nCluster: Rejection\nZukünftiger bestätigter Lieferbeginn\nliegt gegenüber anderem Lieferanten\nbereits vor.\nDie Ausführungsfrist der 6 WT ab\ndem frühestmöglichen Sperrtermin\nberührt das bestätigte\nLieferbeginndatum gegenüber\nanderem Lieferanten.\n\n\n40\nIst im Zeitraum von 6 WT ab dem\nfrühestmöglichen Sperrtermin an\nallen Messlokationen, welche der\nMarktlokation zugeordnet sind,\nder identische MSB zugeordnet,\nwie an der zu sperrenden\nMarktlokation?\n\n\nA02\nCluster: Rejection\nAn mindestens einer Messlokation ist\nein anderer MSB zugeordnet als an\nder Marktlokation.\nHinweis: Stromspezifische Frage\n\n\n50\nLiegt die zu sperrende\nMarktlokation in der\nNiederspannung?\n\n\nA03\nCluster: Rejection\nMarktlokation ist nicht in der\nNiederspannung.\nHinweis: Stromspezifische Frage\n\n\n60\nSind weitere Marktlokationen von\nder Sperrung betroffen, für die\ndieser Sperrauftrag keine Wirkung\nentfalten darf? Hinweis: „Ruhende\nMarktlokationen“ sind bei der\nBeantwortung der Frage nicht zu\nberücksichtigen.\n\n\n65\nHandelt es sich bei der bzw. den\nweiteren Marktlokationen\nausschließlich um erzeugende\nMarktlokation(en)?\n\n\nA04\nCluster: Rejection\nMindestens eine weitere\nverbrauchende Marktlokation ist von\nder Sperrung betroffen.\nHinweis: Stromspezifische Frage\n\n\n70\nLiegt im gesamten\nAusführungszeitraum ein\nbestätigter Lieferbeginn\ngegenüber dem beauftragenden\nLF vor?\n\n\nA12\nCluster: Rejection\nIm Ausführungszeitraum liegt bereits\nein bestätigter Lieferbeginn\ngegenüber dem beauftragenden LF\nvor.\n\n\n80\nLiegt ein Verhinderungsgrund\neiner Sperrung an der\nMarktlokation vor?\n\n\nA05\nCluster: Rejection\nVerhinderungsgrund liegt vor.\nHinweis: Das identifizierte Problem\nist in der\nAntwort zu beschreiben/benennen.\n\n\n90\nIst der Sperrauftrag\ntermingebunden?\n\n\n100\nLiegt der übermittelte\nSperrtermin mindestens 12 WT\nnach dem Eingangsdatum der\nNachricht des Sperrauftrags?\n\n\nA06\nCluster: Rejection\nFristverletzung bei einem\ntermingebundenen Sperrauftrag.\n\n\n110\nLiegt der übermittelte\nfrühestmögliche Sperrtermin\nmindestens 6 WT nach dem\nEingangsdatum der Nachricht des\nSperrauftrags?\n\n\nA07\nCluster: Rejection\nFristverletzung bei einem nicht\ntermingebundenen Sperrauftrag.\n\n\n120\nIst ein zuvor nicht spezifizierter\nFehler aufgetreten?\n\n\nA99\nCluster: Rejection\nSonstiges\nHinweis: Das identifizierte Problem\nist in der\nAntwort zu beschreiben/benennen.\nNutzungsmöglichkeit Ende:\n01.10.2026 00:00 Uhr\n\n\n130\nKann der Sperrauftrag pauschal\nüber das elektronische Preisblatt\nabgebildet werden?\n\n\nA08\nCluster: Consent\nSperrung wird über das elektronische\nPreisblatt abgebildet.\n\n\nA09\nCluster: Consent\nDie individuellen Sperrkosten werden\nin der Nachricht ausgetauscht.\n"} kapitel={"GPKE · 6.12.1: AD: Unterbrechung der Anschlussnutzung (Sperren) auf Anweisung des LF"} name={"Sperrauftrag prüfen"} bpmnFv="202604" bpmnCode="E_0470">
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 10 | Is the market location already disconnected? | yes | A01 | Cluster: Rejection The market location is already disconnected. |
| — | — | no | → Step 20 | — |
| 20 | Does a disconnection order already exist for the market location within the period of 6 WT from the earliest possible disconnection date? | yes | A10 | Cluster: Rejection A disconnection order for the market location already exists. |
| — | — | no | → Step 30 | — |
| 30 | Is the LF ordering the disconnection assigned to the market location to be disconnected throughout the entire execution period of the disconnection order (= earliest possible disconnection date until earliest possible disconnection date + 6 WT)? | no | A11 | Cluster: Rejection A future confirmed start of supply towards another supplier already exists. The execution deadline of 6 WT from the earliest possible disconnection date affects the confirmed start of supply date towards the other supplier. |
| — | — | yes | → Step 40 | — |
| 40 | In the period of 6 WT from the earliest possible disconnection date, is the identical MSB assigned at all metering locations assigned to the market location as at the market location to be disconnected? | no | A02 | Cluster: Rejection At least one metering location has a different MSB assigned than the market location. Note: electricity-specific question |
| — | — | yes | → Step 50 | — |
| 50 | Is the market location to be disconnected at low voltage? | no | A03 | Cluster: Rejection The market location is not in the low voltage grid. Note: Electricity-specific question |
| — | — | yes | → Step 60 | — |
| 60 | Are further market locations affected by the disconnection for which this disconnection order must not take effect? Note: “Dormant market locations” are not to be taken into account when answering the question. | yes | → Step 65 | — |
| — | — | no | → Step 70 | — |
| 65 | Are the further market location(s) exclusively generating market location(s)? | no | A04 | Cluster: Rejection At least one further consuming market location is affected by the disconnection. Note: Electricity-specific question |
| — | — | yes | → Step 70 | — |
| 70 | Is there a confirmed start of supply towards the commissioning LF for the entire execution period? | yes | A12 | Cluster: Rejection A confirmed start of supply towards the ordering LF already exists within the execution period. |
| — | — | no | → Step 80 | — |
| 80 | Is there a reason preventing a disconnection at the market location? | yes | A05 | Cluster: Rejection There is a reason for prevention. Note: The identified problem must be described/named in the response. |
| — | — | no | → step 90 | — |
| 90 | Is the disconnection order date-bound? | yes | → Step 100 | — |
| — | — | no | → Step 110 | — |
| 100 | Is the transmitted disconnection date at least 12 WT after the receipt date of the message of the disconnection order? | no | A06 | Cluster: Rejection Deadline violation for a date-bound disconnection order. |
| — | — | yes | → Step 120 | — |
| 110 | Is the transmitted earliest possible disconnection date at least 6 WT after the receipt date of the message of the disconnection order? | no | A07 | Cluster: Rejection Deadline violation for a disconnection order that is not date-bound. |
| — | — | yes | → Step 120 | — |
| 120 | Has a previously unspecified error occurred? | yes | A99 | Cluster: Rejection Other Note: The identified problem must be described/named in the response. End of usability: 01.10.2026 00:00 |
| — | — | no | → Step 130 | — |
| 130 | Can the disconnection order be mapped as a flat rate via the electronic price sheet? | yes | A08 | Cluster: Consent Disconnection is mapped via the electronic price sheet. |
| — | — | no | A09 | Cluster: Consent The individual disconnection costs are exchanged in the message. |
## Result codes
| Result code | Cluster | Meaning | Response check identifier |
|---|---|---|---|
| `A01` | Rejection | The market location is already disconnected. | [19117](/schnittstellen/202604/pruefi/ORDRSP/PI_19117) |
| `A10` | Rejection | A disconnection order for the market location already exists. | [19117](/schnittstellen/202604/pruefi/ORDRSP/PI_19117) |
| `A11` | Rejection | A future confirmed start of supply towards another supplier already exists. The execution period of 6 WT from the earliest possible disconnection date affects the confirmed start of supply date towards another supplier. | [19117](/schnittstellen/202604/pruefi/ORDRSP/PI_19117) |
| `A02` | Rejection | At least one metering location has a different MSB assigned than the market location. Note: electricity-specific question | [19117](/schnittstellen/202604/pruefi/ORDRSP/PI_19117) |
| `A03` | Rejection | The market location is not in the low voltage grid. Note: electricity-specific question | [19117](/schnittstellen/202604/pruefi/ORDRSP/PI_19117) |
| `A04` | Rejection | At least one further consuming market location is affected by the disconnection. Note: electricity-specific question | [19117](/schnittstellen/202604/pruefi/ORDRSP/PI_19117) |
| `A12` | Rejection | A confirmed start of supply towards the ordering LF already exists within the execution period. | [19117](/schnittstellen/202604/pruefi/ORDRSP/PI_19117) |
| `A05` | Rejection | A reason for prevention exists. Note: The identified problem must be described/named in the response. | [19117](/schnittstellen/202604/pruefi/ORDRSP/PI_19117) |
| `A06` | Rejection | Deadline violation for a date-bound disconnection order. | [19117](/schnittstellen/202604/pruefi/ORDRSP/PI_19117) |
| `A07` | Rejection | Deadline violation for a disconnection order that is not date-bound. | [19117](/schnittstellen/202604/pruefi/ORDRSP/PI_19117) |
| `A99` | Rejection | Other Note: The identified problem is to be described/named in the response. End of usability: 01.10.2026 00:00 | [19117](/schnittstellen/202604/pruefi/ORDRSP/PI_19117) |
| `A08` | Consent | Disconnection is mapped via the electronic price sheet. | [19116](/schnittstellen/202604/pruefi/ORDRSP/PI_19116) |
| `A09` | Consent | The individual disconnection costs are exchanged in the message. | [19116](/schnittstellen/202604/pruefi/ORDRSP/PI_19116) |
*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 13 result codes of the decision tree are contained in the generated process `E_0470.bpmn`.
:::