BIKO (46)
E_0026 — Assign data status after completed balancing group settlement
Assign data status after the balancing group settlement has taken place
| Attribute | Value |
|---|---|
| Designation | Assign data status after completed balancing group settlement |
| Market role | BIKO |
| Regulatory determination / chapter | MaBiS |
| Section | 7.45.1: AD: Transmission of the data status for the balancing group aggregated time series from BIKO to ÜNB and BKV |
| Check identifiers | Response: 21003, 21004 |
| EBD version | 4.2 |
| As at | 2026-06-23 |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| from 1 | The following checks are performed for each highest version of the BK-SZR with the data status “billing data” or “billing data KBKA” in this balancing month: | — | — | — |
| 1 | Is the MaBiS-ZP at the RZ aggregation level? | no | → Step 2 | — |
| — | — | yes | → Step 5 | — |
| 2 | Has the BKV cancelled the subscription for aggregation level RZ for the BK of this MaBiS-ZP in this balancing month? | yes | → Step 4 | Setting the data status for the version of the MaBiS-ZP at aggregation level BG |
| — | — | no | → Step 3 | — |
| 3 | Has the BKV already notified for this balancing month that the further checks must take place at BG level? | yes | → Step 4 | Setting the data status for the version of the MaBiS-ZP at aggregation level BG |
| — | — | no | End | — |
| 4 | Has the BKA (without KBKA) taken place? | yes | A03 | Data status “Billed data” |
| — | — | no | A06 | Data status “Billed data KBKA” |
| 5 | Has the BKV already notified for this balancing month that the further checks must take place at BG level? | yes | End | — |
| — | — | no | → Step 6 | Setting the data status for the version of the MaBiS-ZP at aggregation level RZ |
| 6 | Has the BKA (without KBKA) taken place? | yes | A03 | Data status “Billed data” Setting the data status for the version of the MaBiS-ZP at aggregation level BG that belongs to the version of the MaBiS-ZP at aggregation level RZ |
| — | — | no | A06 | Data status “Billed data KBKA” Setting the data status for the version of the MaBiS-ZP at aggregation level BG that belongs to the version of the MaBiS-ZP at aggregation level RZ |
| from 7 | The following actions are to be run through for each associated MaBiS-ZP at aggregation level BG: | — | — | — |
| 7 | Does the associated version at aggregation level RZ have the data status „billed data“? | yes | A03 | Data status “Billed data” |
| — | — | no | A06 | Data status “Billed data KBKA” |
Result codes
| Result code | Cluster | Meaning |
|---|---|---|
A03 (2 outputs) | — | Data status “Billed data” |
A06 (2 outputs) | — | Data status “Billed data KBKA” |
A03 | — | Data status “Billed data” Setting the data status for the version of the MaBiS-ZP at aggregation level BG that belongs to the version of the MaBiS-ZP at aggregation level RZ |
A06 | — | Data status “Billed data KBKA” Setting the data status for the version of the MaBiS-ZP at aggregation level BG that belongs to the version of the MaBiS-ZP at aggregation level RZ |
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.