MSB (55 / 54)
E_0533 — Check order placement
Check order placement
| Attribute | Value |
|---|---|
| Designation | Check order placement |
| Market role | MSB |
| Regulatory determination / chapter | GPKE |
| Section | 6.30.3: AD: Order placement of a configuration from LF to MSB |
| Check identifiers | checked: 17123 · response: 19124, 19132 |
| EBD version | 4.2 |
| As at | 2026-06-23 |
Decision tree
| 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 | Is this an order placement of a free-of-charge configuration? | yes | → Step 25 | — |
| — | — | no | → Step 30 | Note: This is a chargeable configuration |
| 25 | Have the lead times been met? Note: The maximum and the minimum lead time must be checked. | no | A08 | Cluster: Rejection The lead time was not met. |
| — | — | yes | → Step 70 | — |
| 30 | Does a configuration from the ordering party already exist at the affected location? | no | → Step 60 | — |
| — | — | yes | → Step 40 | — |
| 40 | Does the request for the quotation contain the reference of the order placement of the existing configuration? Note: If a configuration of the requesting party already exists at the location concerned, this configuration must be terminated. For this reason the requesting party specifies the reference of the configuration valid so far, since only one configuration can exist at any point in time. | no | A02 | Cluster: Rejection A configuration already exists at the location. The request does not contain the reference to the existing configuration. |
| — | — | yes | → Step 60 | — |
| 60 | Is the quotation still valid? | no | A04 | Cluster: Rejection Quotation is no longer valid (e.g. quotation is too old, prices have changed in the meantime) |
| — | — | yes | → Step 70 | — |
| 70 | Does the existing device technology allow the configuration at the ordered point in time? | no | A05 | 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 80 | — |
| 80 | Is this the configuration of a metering time period definition, switching time definition or power curve definition that is not known to the MSB at the ordered point in time? | yes | A06 | Cluster: Rejection Ordered configuration is not known to the MSB |
| — | — | no | → step 90 | — |
| 90 | 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 | A07 | Cluster: Consent Setting up the configuration is generally possible |
Result codes
| Result code | Cluster | Meaning |
|---|---|---|
A01 | Rejection | The ordered configuration already exists |
A08 | Rejection | The lead time was not met. |
A02 | Rejection | A configuration already exists at the location. The request does not contain the reference to the existing configuration. |
A04 | Rejection | Quotation is no longer valid (e.g. quotation is too old, prices have changed in the meantime) |
A05 | 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. |
A06 | Rejection | The ordered configuration is not known to the MSB |
A99 | Rejection | Other Note: The identified problem is to be described/named in the response. End of usability: 01.10.2026 00:00 |
A07 | Consent | Setting up the configuration is generally possible |
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.