MSB (55 / 54)
E_0257 — Check cancellation
Check cancellation
| Attribute | Value |
|---|---|
| Designation | Check cancellation |
| Market role | MSB |
| Regulatory determination / chapter | MaBiS |
| Section | 7.94.5: AD: Request and order placement of values by ESA |
| Check identifiers | Response: 19013, 19014 |
| EBD version | 4.3 |
| As at | — |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 1 | Was the order placement of the ESA confirmed by the MSB? | no | A01 | Cluster: Rejection The order placement of the ESA was not confirmed by the MSB. |
| — | — | yes | → Step 2 | — |
| 2 | Was the order placement a periodic/regular transmission (subscription)? | yes | → Step 3 | — |
| — | — | no | → Step 4 | Note: The order placement was a one-time transmission. |
| 3 | Has the periodic/regular transmission (subscription) of values already begun? | yes | A02 | Cluster: Rejection Transmission of values from the subscription has already begun. |
| — | — | no | A04 | Cluster: Consent Cancellation is confirmed. |
| 4 | Has the one-off transmission of values already taken place? | yes | A03 | Cluster: Rejection The one-time transmission of the values has already taken place. |
| — | — | no | A04 | Cluster: Consent Cancellation is confirmed. |
Result codes
| Result code | Cluster | Meaning | Response check identifier |
|---|---|---|---|
A01 | Rejection | The order placement of the ESA was not confirmed by the MSB. | 19014 |
A02 | Rejection | Transmission of values from the subscription has already begun. | 19014 |
A04 (2 outputs) | Consent | Cancellation is confirmed. | 19013 |
A03 | Rejection | The one-time transmission of the values has already taken place. | 19014 |
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.