ÜNB (9 / 8)
E_0574 — Check master data on balancing group integrity
Check master data on balancing group integrity
| Attribute | Value |
|---|---|
| Designation | Check master data on balancing group integrity |
| Market role | ÜNB |
| Regulatory determination / chapter | GPKE |
| Section | 6.54.1: AD: Master data for balancing group integrity |
| Check identifiers | Response: 55671 |
| EBD version | 4.2 |
| As at | 2026-06-23 |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| from 10 | All responses found are to be given as far as the format allows (at most 8 response codes)*. | — | — | — |
| 10 | Is this a usage period with the quality „no data“? | yes | → Step 110 | — |
| — | — | no | → Step 20 | — |
| 20 | Does the sender of the message for this usage period match the grid operator previously assigned in the recipient's system? Note: If no previous assignment exists, the question must be answered with "yes". | no | A17 | For this usage period, the sender of the message is not the previous grid operator. A grid operator change has therefore been carried out. |
| — | — | yes | → Step 30 | — |
| 30 | Is the balancing area valid in the control area at the specified point in time? | no | A03 | Balancing area not valid. |
| — | — | yes | → Step 40 | — |
| 40 | Is the specified grid operator assigned to the balancing area? | no | A14 | The specified NB does not match the assigned NB of the balancing area. |
| — | — | yes | → Step 60 | — |
| 60 | Is the metering point operator registered in the BDEW code number database at the point in time of the check? | no | A15 | Metering point operator not valid. |
| — | — | yes | → Step 70 | — |
| 70 | Is the supplier registered in the BDEW code number database at the point in time of the check? | no | A04 | Supplier not valid. |
| — | — | yes | → Step 80 | — |
| 80 | Is the balancing group valid in the control area at the specified point in time? | no | A05 | Balancing group not valid. |
| — | — | yes | → step 90 | — |
| 90 | Does the time series type (ZRT) match the valid ZRT for balancing group integrity at the ÜNB? | no | A16 | ZRT not matching. |
| — | — | yes | → Step 100 | — |
| 100 | Does the delivery direction derived from the transaction reason supplement match the ZRT? | no | A07 | Delivery direction does not match. |
| — | — | yes | → Step 110 | — |
| 110 | Has a previously unspecified error occurred? | yes | A99 | Other quality response message Note: The identified problem is to be described / named in the response. End of usability: 01.10.2026 00:00 |
| — | — | no | → Step 120 | — |
| 120 | Has no preceding check led to a response? | yes | A13 | Master data have been adopted without conflict for the specified usage period. |
| — | — | no | A** | Master data have been adopted Note A**: All noted response codes of the preceding check steps are transmitted for each usage period of the data identified as erroneous, stating the period ID. |
| 130 | Are there further usage periods to be checked? | yes | → Step 10 | — |
| — | — | no | End | — |
Result codes
| Result code | Cluster | Meaning |
|---|---|---|
A17 | — | For this usage period, the sender of the message is not the previous grid operator. A grid operator change has therefore been carried out. |
A03 | — | Balancing area not valid. |
A14 | — | The specified NB does not match the assigned NB of the balancing area. |
A15 | — | Metering point operator not valid. |
A04 | — | Supplier not valid. |
A05 | — | Balancing group not valid. |
A16 | — | ZRT not matching. |
A07 | — | Delivery direction does not match. |
A99 | — | Other quality response message Note: The identified problem is to be described / named in the response. End of usability: 01.10.2026 00:00 |
A13 | — | Master data have been adopted without conflict for the specified usage period. |
A** | — | Master data have been adopted Note A**: All noted response codes of the preceding check steps are transmitted for each usage period of the data identified as erroneous, stating the period ID. |
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.