# E_0468 — Check cancellation
Check cancellation
| Attribute | Value |
|---|---|
| Designation | Check cancellation |
| Market role | NB |
| Regulatory determination / chapter | GPKE |
| Section | 6.14.1: AD: Cancellation of the interruption and restoration of grid connection use on the instruction of LF |
| Check identifiers | checked: [39000](/en/schnittstellen/202604/pruefi/ORDCHG/PI_39000) · response: [19128](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19128), [19129](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19129) |
| EBD version | 4.2 |
| As at | 2026-06-23 |
## Decision tree
\nDecision tree E_0468: Stornierung prüfen\n\n\n\nE_0468\nStornierung prüfen\nChecking role: NB\n\nyes\n\nno\n\nyes\n\nno\n\nyes\n\nno\n\nyes\n\nno\n\nyes\n\nno\n\n\n1\nWurde der Sperr- /\nEntsperrauftrag bereits durch den\nNB abgelehnt?\n\n\nA06\nCluster: Rejection\nAuftrag wurde bereits abgelehnt und\nkann nicht mehr storniert werden\n\n\n2\nHandelt es sich um eine\nStornierung eines\nEntsperrauftrags?\n\n\n3\nIst die Stornierung vor der\nDurchführung der Entsperrung\neingegangen?\n\n\nA01\nCluster: Consent\nEntsperrauftrag ist storniert.\n\n\nA02\nCluster: Rejection\nStornierung des Entsperrauftrags\nnicht mehr möglich.\n\n\n4\nIst der Nachrichteneingang der\nStornierung spätestens am Tag\nvor dem geplanten\nAusführungstermin bzw. fixen\nSperrtermin aus dem Sperrauftrag\neingegangen?\n\n\nA03\nCluster: Consent\nSperrauftrag ist bis zum Vortag der\nSperrung storniert.\n\n\n5\nIst die Stornierung vor der\nDurchführung der Sperrung\neingegangen?\n\n\nA04\nCluster: Consent\nSperrauftrag ist am Tag der Sperrung\nstorniert.\n\n\nA05\nCluster: Rejection\nStornierung des Sperrauftrags nicht\nmehr möglich.\n"} kapitel={"GPKE · 6.14.1: AD: Stornieren der Unterbrechung und Wiederherstellung der Anschlussnutzung auf Anweisung des LF"} name={"Stornierung prüfen"}>
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 1 | Has the disconnection/reconnection order already been rejected by the NB? | yes | A06 | Cluster: Rejection Order has already been rejected and can no longer be cancelled |
| — | — | no | → Step 2 | — |
| 2 | Is this a cancellation of a reconnection order? | yes | → Step 3 | — |
| — | — | no | → Step 4 | Note: This is a cancellation of a disconnection order. |
| 3 | Was the cancellation received before the reconnection was carried out? | yes | A01 | Cluster: Consent Reconnection order is cancelled. |
| — | — | no | A02 | Cluster: Rejection Cancellation of the reconnection order is no longer possible. |
| 4 | Was the cancellation message received no later than the day before the planned execution date or the fixed disconnection date from the disconnection order? | yes | A03 | Cluster: Consent Disconnection order is cancelled up to the day before the disconnection. |
| — | — | no | → Step 5 | — |
| 5 | Was the cancellation received before the disconnection was carried out? | yes | A04 | Cluster: Consent Disconnection order is cancelled on the day of the disconnection. |
| — | — | no | A05 | Cluster: Rejection Cancellation of the disconnection order is no longer possible. |
## Result codes
| Result code | Cluster | Meaning | Response check identifier |
|---|---|---|---|
| `A06` | Rejection | Order has already been rejected and can no longer be cancelled | [19129](/schnittstellen/202604/pruefi/ORDRSP/PI_19129) |
| `A01` | Consent | Reconnection order is canceled. | [19128](/schnittstellen/202604/pruefi/ORDRSP/PI_19128) |
| `A02` | Rejection | Cancellation of the reconnection order is no longer possible. | [19129](/schnittstellen/202604/pruefi/ORDRSP/PI_19129) |
| `A03` | Consent | Disconnection order is cancelled up to the day before the disconnection. | [19128](/schnittstellen/202604/pruefi/ORDRSP/PI_19128) |
| `A04` | Consent | Disconnection order is cancelled on the day of the disconnection. | [19128](/schnittstellen/202604/pruefi/ORDRSP/PI_19128) |
| `A05` | Rejection | Cancellation of the disconnection order is no longer possible. | [19129](/schnittstellen/202604/pruefi/ORDRSP/PI_19129) |
*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.*
:::note{title="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.
:::