BIKO (46)
E_0061 — Assign data status once a validation notification is available
Assign data status once a validation notification is available
| Attribute | Value |
|---|---|
| Designation | Assign data status once a validation notification is available |
| Market role | BIKO |
| Regulatory determination / chapter | MaBiS |
| Section | 7.51.3: AD: Transmission of the data status for the delta time series carry-over from BIKO to ÜNB and NB |
| Check identifiers | Response: 21003, 21004 |
| EBD version | 4.2 |
| As at | 2026-06-23 |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 1 | Is the received validation notification positive? | no | A** | Note: A** is replaced by the correct code from the system of the BIKO. Possible codes are: A01 data status „billing data“ A02 data status „check data“ A04 data status „billing data KBKA“ |
| — | — | yes | → Step 2 | — |
| 2 | Is the data status “check data” present? | no | A** | Note: A** is replaced by the correct code from the system of the BIKO. Possible codes are: A01 data status „billing data“ A04 data status „billing data KBKA“ |
| — | — | yes | → Step 3 | — |
| 3 | Is the validation notification received within the clearing phase for DZÜ of the BKA (excluding KBKA)? | yes | A01 | Data status “Billing data” |
| — | — | no | A04 | Data status “Billing data KBKA” |
Result codes
| Result code | Cluster | Meaning |
|---|---|---|
A** | — | Note: A** is replaced by the correct code from the system of the BIKO. Possible codes are: A01 data status „billing data“ A02 data status „check data“ A04 data status „billing data KBKA“ |
A** | — | Note: A** is replaced by the correct code from the system of the BIKO. Possible codes are: A01 data status „billing data“ A04 data status „billing data KBKA“ |
A01 | — | Data status “Billing data” |
A04 | — | Data status “Billing data KBKA” |
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.