# E_0527 — Order placement
Order placement
| Attribute | Value |
|---|---|
| Designation | Order placement |
| Market role | MSB |
| Regulatory determination / chapter | GPKE |
| Section | 6.29.4: AD: Order placement of a configuration from NB to MSB |
| Check identifiers | Response: [19127](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19127), [19132](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19132) |
| EBD version | 4.2 |
| As at | 2026-06-23 |
## Decision tree
\nDecision tree E_0527: Bestellung\n\n\n\nE_0527\nBestellung\nChecking role: MSB\n\nyes\n\nno\n\nno\n\nyes\n\nyes\n\nno\n\n\n10\nLiegt die Bestellte Konfiguration\nzum bestellten Zeitpunkt an der /\nbzw. allen Lokationen bereits vor?\n\n\nA01\nCluster: Rejection\nDie bestellte Konfiguration liegt\nbereits vor\n\n\n20\nErlaubt die vorhandene\nGerätetechnik die Konfiguration\nzum bestellten Zeitpunkt?\n\n\nA02\nCluster: Rejection\nDie vorhandene Gerätetechnik erlaubt\ndie Konfiguration zum bestellten\nZeitpunkt nicht.\nHinweis:\nWenn die Gerätetechnik eine\ndetailliertere Auflösung als die\nbestellten Werte bereitstellt, kann\ndiese nicht abgelehnt werden.\nBeispiel: Messung bietet Lastgang\n1/4h Auflösung. Geforderte Werte\nsind kumulierte Werte.\n\n\n30\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.10.2026 00:00 Uhr\n\n\nA03\nCluster: Consent\nDie Einrichtung der Konfiguration ist\ngrundsätzlich möglich\n"} kapitel={"GPKE · 6.29.4: AD: Bestellung einer Konfiguration vom NB an MSB"} name={"Bestellung"} bpmnFv="202604" bpmnCode="E_0527">
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 10 | Does the ordered configuration already exist at the point in time ordered at the / or at all locations? | yes | A01 | Cluster: Rejection The ordered configuration already exists |
| — | — | no | → Step 20 | — |
| 20 | Does the existing device technology allow the configuration at the ordered point in time? | no | A02 | Cluster: Rejection The existing device technology does not allow the configuration at the ordered point in time. Note: If the device technology provides a more detailed resolution than the ordered values, it cannot be rejected. Example: Metering provides a load curve with 1/4 h resolution. The required values are cumulative values. |
| — | — | yes | → Step 30 | — |
| 30 | 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.10.2026 00:00 |
| — | — | no | A03 | Cluster: Consent Setting up the configuration is generally possible |
## Result codes
| Result code | Cluster | Meaning |
|---|---|---|
| `A01` | Rejection | The ordered configuration already exists |
| `A02` | Rejection | The existing device technology does not permit the configuration at the ordered point in time. Note: If the device technology provides a more detailed resolution than the ordered values, this cannot be rejected. Example: The metering provides a load curve with 1/4h resolution. The required values are cumulative values. |
| `A99` | Rejection | Other Note: The identified problem is to be described/named in the response. End of usability: 01.10.2026 00:00 |
| `A03` | Consent | Setting up the configuration is generally possible |
*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.*
:::tip{title="Consistent with the generated process"}
All 4 result codes of the decision tree are contained in the generated process `E_0527.bpmn`.
:::