NB (69)
E_0070 — Check DZÜ list
Check DZÜ list
| Attribute | Value |
|---|---|
| Designation | Check DZÜ list |
| Market role | NB |
| Regulatory determination / chapter | MaBiS |
| Section | 7.48.1: AD: Exchange of the delta time series carry-over list from ÜNB to NB |
| Check identifiers | Response: 55224 |
| EBD version | 4.2 |
| As at | 2026-06-23 |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 1 | Is the DZÜ list received within the clearing phase for DZÜ? | no | A01 | Cluster: Rejection of the entire list Receipt is not within the clearing phase DZÜ |
| — | — | yes | → Step 2 | — |
| from 2 | The following checks are performed for each market location: | — | — | — |
| 2 | Is the market location known? | no | A02 | Cluster: Correction list due to rejection Market location is not known |
| — | — | yes | → Step 3 | — |
| 3 | Does the balancing area match the balancing area exchanged between NB and ÜNB? | no | A03 | Cluster: Correction list due to rejection balancing-rel. data not correct / missing Is filled with values of the NB for all master data |
| — | — | yes | → Step 4 | — |
| 4 | Does the balancing group match the balancing group exchanged between NB and ÜNB? | no | A03 | Cluster: Correction list due to rejection balancing-rel. data not correct / missing Is filled with values of the NB for all master data |
| — | — | yes | → Step 5 | — |
| 5 | Does the start of balancing match the expectation of the NB? | no | A03 | Cluster: Correction list due to rejection balancing-rel. data not correct / missing Is filled with values of the NB for all master data |
| — | — | yes | → Step 6 | — |
| 6 | Does the end of balancing match the expectation of the NB? | no | A03 | Cluster: Correction list due to rejection balancing-rel. data not correct / missing Is filled with values of the NB for all master data |
| — | — | yes | → Step 7 | — |
| 7 | Does the normalized profile match the normalized profile exchanged between NB and LF? | no | A03 | Cluster: Correction list due to rejection balancing-rel. data not correct / missing Is filled with values of the NB for all master data |
| — | — | yes | → Step 8 | — |
| 8 | Does the version specification of the profile match the version of the profile exchanged between NB and ÜNB for SLS? | no | A03 | Cluster: Correction list due to rejection balancing-rel. data not correct / missing Is filled with values of the NB for all master data |
| — | — | yes | → step 9 | — |
| 9 | Does the estimated forecast quantity (JVP) match the forecast quantity exchanged between NB and LF? | no | A03 | Cluster: Correction list due to rejection balancing-rel. data not correct / missing Is filled with values of the NB for all master data |
| — | — | yes | → Step 10 | — |
| 10 | Does the actually balanced quantity match the expected balanced quantity (monthly measured quantity based on 1/4-h values)? | no | A03 | Cluster: Correction list due to rejection balancing-rel. data not correct / missing Is filled with values of the NB for all master data |
| — | — | yes | → Step 11 | — |
| 11 | Does the time series type match the one exchanged between NB and LF? | no | A03 | Cluster: Correction list due to rejection balancing-rel. data not correct / missing Is filled with values of the NB for all master data |
| — | — | yes | → Step 12 | — |
| 12 | Is the transfer of the energy quantity of the market location from the ÜNB-DZR to the NB-DZR justified? | no | A03 | Cluster: Correction list due to rejection balancing-rel. data not correct / missing Is filled with values of the NB for all master data |
| — | — | yes | End | — |
Result codes
| Result code | Cluster | Meaning |
|---|---|---|
A01 | Rejection of the entire list | Receipt is not within the clearing phase DZÜ |
A02 | Correction list due to rejection | Market location is unknown |
A03 (10 outputs) | Correction list due to rejection | balancing-rel. data incorrect / missing Is filled with values of the NB for all master data |
Notes on this page
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.
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.