# E_0102 — Check assignment
Check assignment
| Attribute | Value |
|---|---|
| Designation | Check assignment |
| Market role | NB |
| Regulatory determination / chapter | MaBiS |
| Section | 7.8.1: AD: Assignment of a grid load time series to a grid time series at NB |
| Check identifiers | Response: [55237](/en/schnittstellen/202610/pruefi/UTILMD/PI_55237) |
| EBD version | 4.3 |
| As at | — |
## Decision tree
\nDecision tree E_0102: Zuordnung prüfen\n\n\n\nE_0102\nZuordnung prüfen\nChecking role: NB\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\n\n1\nWird die ID der Netzgangzeitreihe\nbereits für die Identifikation eines\nNicht-MaBiS-ZP verwendet?\n\n\nA01\nCluster: Rejection\nID bereits außerhalb MaBiS\nverwendet\n\n\n2\nEntspricht die Zuordnung der\nNetzgangzeitreihe zur\nNetzzeitreihe der Vereinbarung\nzur messtechnischen Abgrenzung\nder beiden benachbarten NB?\n\n\nA02\nCluster: Rejection\nZuordnung passt nicht zur\nVereinbarung\n\n\n3\nIst der Absender zum\nZuordnungsbeginn an der\nNetzzeitreihe beteiligt?\n\n\nA03\nCluster: Rejection\nKeine Berechtigung für die\nNetzzeitreihe\n\n\n4\nIst der Empfänger zum\nZuordnungsbeginn an der\nNetzzeitreihe beteiligt?\n\n\nA04\nCluster: Rejection\nKeine Beteiligung an der\nNetzzeitreihe\n\n\n5\nExistiert zum Zuordnungsbeginn\nbereits eine Zuordnung der\nangegebenen Netzgangzeitreihe\nzu einer Netzzeitreihe?\n\n\nA05\nCluster: Rejection\nZuordnung bereits vorhanden\nHinweis: In der Antwort ist die\nzugeordnete Netzzeitreihe\nanzugeben.\n\n\n6\nIst ein nicht spezifizierter Fehler\naufgetreten?\n\n\nA99\nCluster: Rejection\nSonstiges\nHinweis: Das identifizierte Problem\nist in der Antwort zu beschreiben /\nbenennen.\nNutzungsmöglichkeit Ende:\n01.04.2027 00:00 Uhr\n\n\nA06\nCluster: Consent\nZuordnung durchgeführt\n"} kapitel={"MaBiS · 7.8.1: AD: Zuordnung einer Netzgangzeitreihe zu einer Netzzeitreihe beim NB"} name={"Zuordnung prüfen"}>
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 1 | Is the ID of the grid load time series already used to identify a non-MaBiS-ZP? | yes | A01 | Cluster: Rejection ID already used outside MaBiS |
| — | — | no | → Step 2 | — |
| 2 | Does the assignment of the grid load time series to the grid time series match the agreement on the metering-based delimitation of the two adjacent NB? | no | A02 | Cluster: Rejection Assignment does not match the agreement |
| — | — | yes | → Step 3 | — |
| 3 | Is the sender involved in the grid time series at the allocation start? | no | A03 | Cluster: Rejection No authorization for the grid time series |
| — | — | yes | → Step 4 | — |
| 4 | Is the recipient involved in the grid time series at the allocation start? | no | A04 | Cluster: Rejection No participation in the grid time series |
| — | — | yes | → Step 5 | — |
| 5 | Does an assignment of the specified grid load time series to a grid time series already exist at the allocation start? | yes | A05 | Cluster: Rejection Assignment already exists Note: The assigned grid time series must be stated in the response. |
| — | — | no | → Step 6 | — |
| 6 | Has an unspecified error occurred? | yes | A99 | Cluster: Rejection Other Note: The identified problem must be described / named in the response. End of usability: 01.04.2027 00:00 |
| — | — | no | A06 | Cluster: Consent Assignment carried out |
## Result codes
| Result code | Cluster | Meaning |
|---|---|---|
| `A01` | Rejection | ID already used outside MaBiS |
| `A02` | Rejection | Assignment does not match the agreement |
| `A03` | Rejection | No authorization for the grid time series |
| `A04` | Rejection | No participation in the grid time series |
| `A05` | Rejection | Assignment already exists Note: The assigned grid time series must be specified in the response. |
| `A99` | Rejection | Other Note: The identified problem is to be described / named in the response. End of usability: 01.04.2027 00:00 |
| `A06` | Consent | Assignment 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 202610); »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.
:::