BIKO (46)
E_0043 — 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.45.3: 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.3 |
| As at | — |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 1 | Is the MaBiS-ZP at the RZ aggregation level? | no | → Step 2 | — |
| — | — | yes | → Step 8 | — |
| 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 | 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“ A03 data status „billed data“ A04 data status „billing data KBKA“ |
| — | — | yes | → Step 5 | — |
| 5 | 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“ A03 data status „billed data“ A04 data status „billing data KBKA“ |
| — | — | yes | → Step 6 | — |
| 6 | Is the validation notification received before expiry of the deadline for the clearing phase of the BKA (excluding KBKA)? | yes | A01 | Data status “Billing data” |
| — | — | no | → Step 7 | — |
| 7 | Is the validation notification received before expiry of the deadline for the clearing phase KBKA? | yes | A04 | Data status “Billing data KBKA” |
| — | — | no | End | — |
| 8 | Has the BKV already notified for this balancing month that the further checks must take place at BG level? | yes | End | — |
| — | — | no | → step 9 | Setting the data status for the version of the MaBiS-ZP at aggregation level RZ |
| 9 | 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“ A03 data status „billed data“ A04 data status „billing data KBKA“ |
| — | — | yes | → Step 10 | — |
| 10 | 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“ A03 data status „billed data“ A04 data status „billing data KBKA“ |
| — | — | yes | → Step 11 | — |
| 11 | Is the validation notification received before expiry of the deadline for the clearing phase of the BKA (excluding KBKA)? | yes | A01 | Data status “Billing 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 | A04 | Data status “Billing 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 12 | The following actions are to be run through for each associated MaBiS-ZP at aggregation level BG: | — | — | — |
| 12 | Does the associated version at aggregation level RZ have the data status billing data? | yes | A01 | Data status “Billing data” |
| — | — | no | A02 | Data status “Validation data” |
Result codes
| Result code | Cluster | Meaning |
|---|---|---|
A** (2 outputs) | — | 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“ A03 data status „billed data“ A04 data status „billing data KBKA“ |
A** (2 outputs) | — | Note: A** is replaced by the correct code from the system of the BIKO. Possible codes are: A01 data status „billing data“ A03 data status „billed data“ A04 data status „billing data KBKA“ |
A01 (2 outputs) | — | Data status “Billing data” |
A04 | — | Data status “Billing data KBKA” |
A01 | — | Data status “Billing 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 |
A04 | — | Data status “Billing 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 |
A02 | — | Data status “Validation 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 202610); »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.