LF (54)
E_0604 — Check assignment
Check assignment
| Attribute | Value |
|---|---|
| Designation | Check assignment |
| Market role | LF |
| Regulatory determination / chapter | GPKE |
| Section | 6.51.1: AD: Case 2: LF assignment for EEG market location with DV obligation |
| Check identifiers | Response: 55608, 55609 |
| EBD version | 4.3 |
| As at | — |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 10 | Has a previously unspecified error occurred? | yes | A99 | Cluster: Rejection Other Note: The identified problem must be described/named in the response. End of usability: open |
| — | — | no | A01 | Cluster: Consent Consent |
Result codes
| Result code | Cluster | Meaning | Response check identifier |
|---|---|---|---|
A99 | Rejection | Other Note: The identified problem is to be described/named in the response. End of usability: open | 55609 |
A01 | Consent | Consent | 55608 |
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. The »response check identifier« column of the result codes assigns a cluster only because this tree carries exactly one checked message and exactly one response per pole; their pole comes from the use case title of the response.
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.