# E_0020 — Check MaBiS-ZP activation
Check MaBiS-ZP activation
| Attribute | Value |
|---|---|
| Designation | Check MaBiS-ZP activation |
| Market role | NB |
| Regulatory determination / chapter | MaBiS |
| Section | 7.1.1: AD: Activation of a MaBiS metering point for the grid time series to NB |
| Check identifiers | Response: [55064](/en/schnittstellen/202604/pruefi/UTILMD/PI_55064) |
| EBD version | 4.2 |
| As at | 2026-06-23 |
## Decision tree
\nDecision tree E_0020: MaBiS-ZP Aktivierung prüfen\n\n\n\nE_0020\nMaBiS-ZP Aktivierung prüfen\nChecking role: NB\n\nyes\n\nno\n\nno\n\nyes\n\nyes\n\nno\n\nno\n\nyes\n\nno\n\nyes\n\nno\n\nyes\n\nyes\n\nno\n\nyes\n\nno\n\nno\n\nyes\n\nno\n\nyes\n\nyes\n\nno\n\n\n1\nErfolgt die Aktivierung nach\nAblauf der Clearingfrist für die\nKBKA?\n\n\nA01\nCluster: Rejection\nFristüberschreitung\n\n\n2\nErfolgt die Aktivierung zum\nMonatsersten 00:00 Uhr?\n\n\nA02\nCluster: Rejection\nGewählter Zeitpunkt nicht zulässig\n\n\n3\nWird die ID bereits für die\nIdentifikation eines\nNicht-MaBiS-ZP verwendet?\n\n\nA03\nCluster: Rejection\nID bereits außerhalb MaBiS\nverwendet\n\n\n4\nIst genau eines der angegebenen\nBilanzierungsgebiete das\nBilanzierungsgebiet des\nEmpfängers?\n\n\nA04\nCluster: Rejection\nBilanzierungsgebiet des\nbenachbarten NB nicht gültig\n\n\n5\nIst die richtige Regelzone\nangegeben?\n\n\nA05\nCluster: Rejection\nRegelzone falsch\n\n\n6\nIst der Empfänger zum\nAktivierungsbeginn für eines der\nzwei angegebenen\nBilanzierungsgebiete zuständig?\n\n\nA06\nCluster: Rejection\nKeine Berechtigung\n\n\n7\nExistiert bereits ein abweichendes\nTupel unter der ID des MaBiS-ZP?\n\n\nA07\nCluster: Rejection\nAbweichender MaBiS-ZP bereits\nvorhanden\n\n\n8\nExistiert bereits für das genannte\nTupel aus Bilanzierungsgebiet des\nverantwortlichen NB,\nBilanzierungsgebiet des\nbenachbarten NB und ZRT eine\nabweichende ID des MaBiS-ZP?\n\n\nA08\nCluster: Rejection\nAbweichende ID zum MaBiS-ZP\nbereits vorhanden\n\n\n9\nIst der NB zur Aktivierung des ZRT\nberechtigt?\n\n\nA09\nCluster: Rejection\nZRT Aktivierung nicht berechtigt\n\n\n10\nPasst die OBIS-Kennzahl zum\nZRT?\n\n\nA10\nCluster: Rejection\nOBIS nicht passend\n\n\n11\nIst der MaBiS-ZP zum Zeitpunkt\nder Aktivierung bereits aktiviert?\n\n\nA11\nCluster: Rejection\nMaBiS-ZP bereits aktiviert\n\n\nA12\nCluster: Consent\nAktivierung durchgeführt\n"} kapitel={"MaBiS · 7.1.1: AD: Aktivierung eines MaBiS-Zählpunkts für die Netzzeitreihe an NB"} name={"MaBiS-ZP Aktivierung prüfen"}>
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 1 | Does the activation take place after expiry of the clearing deadline for the KBKA? | yes | A01 | Cluster: Rejection Deadline exceeded |
| — | — | no | → Step 2 | — |
| 2 | Does the activation take effect as of the first day of the month, 00:00? | no | A02 | Cluster: Rejection Selected point in time not permitted |
| — | — | yes | → Step 3 | — |
| 3 | Is the ID already used to identify a non-MaBiS-ZP? | yes | A03 | Cluster: Rejection ID already used outside MaBiS |
| — | — | no | → Step 4 | — |
| 4 | Is exactly one of the specified balancing areas the balancing area of the recipient? | no | A04 | Cluster: Rejection Balancing area of the neighbouring NB not valid |
| — | — | yes | → Step 5 | — |
| 5 | Is the correct control area specified? | no | A05 | Cluster: Rejection Control area incorrect |
| — | — | yes | → Step 6 | — |
| 6 | Is the recipient responsible for one of the two specified balancing areas at the start of activation? | no | A06 | Cluster: Rejection No authorization |
| — | — | yes | → Step 7 | — |
| 7 | Does a deviating tuple already exist under the ID of the MaBiS-ZP? | yes | A07 | Cluster: Rejection Deviating MaBiS-ZP already exists |
| — | — | no | → Step 8 | — |
| 8 | Does a deviating ID of the MaBiS-ZP already exist for the named tuple of balancing area of the responsible NB, balancing area of the neighboring NB and ZRT? | yes | A08 | Cluster: Rejection Deviating ID for the MaBiS-ZP already exists |
| — | — | no | → step 9 | — |
| 9 | Is the NB entitled to activate the ZRT? | no | A09 | Cluster: Rejection ZRT activation not authorised |
| — | — | yes | → Step 10 | — |
| 10 | Does the OBIS code match the ZRT? | no | A10 | Cluster: Rejection OBIS does not match |
| — | — | yes | → Step 11 | — |
| 11 | Is the MaBiS-ZP already activated at the point in time of the activation? | yes | A11 | Cluster: Rejection MaBiS-ZP already activated |
| — | — | no | A12 | Cluster: Consent Activation carried out |
## Result codes
| Result code | Cluster | Meaning |
|---|---|---|
| `A01` | Rejection | Deadline exceeded |
| `A02` | Rejection | Selected point in time not permitted |
| `A03` | Rejection | ID already used outside MaBiS |
| `A04` | Rejection | Balancing area of the neighbouring NB not valid |
| `A05` | Rejection | Control area incorrect |
| `A06` | Rejection | No authorization |
| `A07` | Rejection | Deviating MaBiS-ZP already exists |
| `A08` | Rejection | Deviating ID for the MaBiS-ZP already exists |
| `A09` | Rejection | ZRT Activation not authorized |
| `A10` | Rejection | OBIS not matching |
| `A11` | Rejection | MaBiS-ZP already activated |
| `A12` | Consent | Activation carried out |
*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.*
:::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.
:::