# E_0536 — Assessment of the overall process
Assessment of the overall process
| Attribute | Value |
|---|---|
| Designation | Assessment of the overall process |
| Market role | MSB |
| Regulatory determination / chapter | GPKE |
| Section | 6.30.6: AD: Order placement of a configuration from LF to MSB |
| Check identifiers | Response: [21043](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21043) |
| EBD version | 4.3 |
| As at | — |
## Decision tree
\nDecision tree E_0536: Bewertung des Gesamtvorgangs\n\n\n\nE_0536\nBewertung des\nGesamtvorgangs\nChecking role: MSB\n\nno\n\nyes\n\nyes\n\nno\n\n\n10\nKonnte die Konfiguration an allen\nLokationen umgesetzt werden?\n\n\nA01\nCluster: Rejection\nDie Konfiguration konnte nicht an\nallen Lokationen umgesetzt werden\n\n\n20\nIst ein zuvor nicht spezifizierter\nFehler aufgetreten?\n\n\nA99\nCluster: Rejection\nSonstiges\nHinweis: Das identifizierte Problem\nist in der Antwort zu\nbeschreiben/benennen.\nNutzungsmöglichkeit Ende:\n01.04.2027 00:00 Uhr\n\n\nA02\nCluster: Consent\nKonfiguration konnte an allen\nLokationen umgesetzt werden\n"} kapitel={"GPKE · 6.30.6: AD: Bestellung einer Konfiguration vom LF an MSB"} name={"Bewertung des Gesamtvorgangs"}>
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 10 | Could the configuration be implemented at all locations? | no | A01 | Cluster: Rejection The configuration could not be implemented at all locations |
| — | — | yes | → Step 20 | — |
| 20 | 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: 01.04.2027 00:00 |
| — | — | no | A02 | Cluster: Consent Configuration could be implemented at all locations |
## Result codes
| Result code | Cluster | Meaning |
|---|---|---|
| `A01` | Rejection | The configuration could not be implemented at all locations |
| `A99` | Rejection | Other Note: The identified problem is to be described/named in the response. End of usability: 01.04.2027 00:00 |
| `A02` | Consent | Configuration could be implemented at all locations |
*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.*
:::note{title="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.
:::