NB (69)
E_0513 — Check whether the registration can be rejected directly
Check whether the registration can be rejected directly
| Attribute | Value |
|---|---|
| Designation | Check whether the registration can be rejected directly |
| Market role | NB |
| Regulatory determination / chapter | On model 2 for the charging-session-specific balancing allocation of energy quantities |
| Section | 17.1.1: AD: Registration of a market location in model 2 by NB (LPB)_new |
| Check identifiers | Response: 55239 |
| EBD version | 4.2 |
| As at | 2026-06-23 |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 1 | Has an error occurred? | yes | A99 | Cluster: Rejection Other Note: The identified problem must be described/named in the response. End of usability: 01.10.2026, 00:00 |
| — | — | no | End | E_0514_Check termination of the assignment |
Result codes
| Result code | Cluster | Meaning |
|---|---|---|
A99 | Rejection | Other Note: The identified problem is to be described/named in the response. End of usability: 01.10.2026, 00:00 |
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.