NB (69)
E_0052 — Reconcile market locations with BG-CL
Reconcile market locations with BG-CL
| Attribute | Value |
|---|---|
| Designation | Reconcile market locations with BG-CL |
| Market role | NB |
| Regulatory determination / chapter | MaBiS |
| Section | 7.24.1: AD: Transmission of the balancing area clearing list from ÜNB to NB (valid subscription) |
| Check identifiers | Response: 55196 |
| EBD version | 4.3 |
| As at | — |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 1 | Is there a valid BG-CL subscription for this MaBiS-ZP? | no | A01 | Cluster: Rejection of the entire list Subscription was not ordered (this also means that a subscription for this time period has already been terminated). |
| — | — | yes | → Step 2 | — |
| 2 | Does the version specification in the BG-CL match the version specification of an available BG-SZR (category B)? | no | A02 | Cluster: Rejection of the entire list Version not permitted |
| — | — | yes | → Step 3 | — |
| from 3 | The following checks are performed for each market location: | — | — | — |
| 3 | Is an expected market location missing from the BG-CL? | yes | A03 | Cluster: Correction list due to rejection Additional data record / added market location |
| — | — | no | → Step 4 | — |
| 4 | Does the BG-CL contain a market location that is not assigned to the NB for balancing in the balancing month? | yes | A04 | Cluster: Correction list due to rejection Market location assigned to the wrong NB |
| — | — | no | → Step 5 | — |
| 5 | Is the market location contained in the BG-CL assigned to the MaBiS-ZP? | no | A05 | Cluster: Correction list due to rejection Too many market locations contained / market location no longer applicable |
| — | — | yes | → Step 6 | — |
| 6 | Does the balancing area match the balancing area exchanged between NB and ÜNB? | no | A06 | Cluster: Correction list due to rejection balancing-rel. data not correct / missing |
| — | — | yes | → Step 7 | — |
| 7 | Does the balancing group match the balancing group exchanged between NB and ÜNB? | no | A06 | Cluster: Correction list due to rejection balancing-rel. data not correct / missing |
| — | — | yes | → Step 8 | — |
| 8 | Does the start of balancing match the expectation of the NB? | no | A06 | Cluster: Correction list due to rejection balancing-rel. data not correct / missing |
| — | — | yes | → step 9 | — |
| 9 | Does the end of balancing match the expectation of the NB? | no | A06 | Cluster: Correction list due to rejection balancing-rel. data not correct / missing |
| — | — | yes | → Step 10 | — |
| 10 | Does the normalized profile match the normalized profile exchanged between NB and ÜNB? | no | A06 | Cluster: Correction list due to rejection balancing-rel. data not correct / missing |
| — | — | yes | → Step 11 | — |
| 11 | Does the version specification of the profile match the version of the profile exchanged between NB and ÜNB? | no | A06 | Cluster: Correction list due to rejection balancing-rel. data not correct / missing |
| — | — | yes | → Step 12 | — |
| 12 | Does the estimated forecast quantity (JVP) match the forecast quantity exchanged between NB and ÜNB? | no | A06 | Cluster: Correction list due to rejection balancing-rel. data not correct / missing |
| — | — | yes | → Step 13 | — |
| 13 | Does the actually balanced quantity match the expected balanced quantity (monthly measured quantity based on the sum of the 1/4-h values)? | no | A06 | Cluster: Correction list due to rejection balancing-rel. data not correct / missing |
| — | — | yes | → Step 14 | — |
| 14 | Does the time series type match the one exchanged between NB and ÜNB? | no | A06 | Cluster: Correction list due to rejection balancing-rel. data not correct / missing |
| — | — | yes | End | — |
Result codes
| Result code | Cluster | Meaning |
|---|---|---|
A01 | Rejection of the entire list | Subscription was not ordered (this also means that a subscription for this time period has already been terminated). |
A02 | Rejection of the entire list | Version not permitted |
A03 | Correction list due to rejection | Additional data record / added market location |
A04 | Correction list due to rejection | Market location assigned to the wrong NB |
A05 | Correction list due to rejection | Too many market locations included / market location no longer applicable |
A06 (9 outputs) | Correction list due to rejection | balancing-rel. data incorrect / missing |
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.