MSB (55 / 54)
E_0531 — Check request
Check request
| Attribute | Value |
|---|---|
| Designation | Check request |
| Market role | MSB |
| Regulatory determination / chapter | GPKE |
| Section | 6.30.1: AD: Order placement of a configuration from LF to MSB |
| Check identifiers | Response: 21033 |
| 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 a chargeable configuration listed in price sheet A of the MSB? | no | A02 | Cluster: Rejection Non-chargeable configuration |
| — | — | yes | → Step 30 | — |
| 30 | Does a chargeable configuration from the requesting party already exist at the affected location? | no | → Step 50 | — |
| — | — | yes | → Step 40 | — |
| 40 | Does this order placement contain the order number of the order placement with which the existing chargeable configuration was ordered? 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 | A03 | Cluster: Rejection A configuration already exists at the location. The order placement does not contain the order number of the existing configuration. |
| — | — | yes | → Step 50 | — |
| 50 | Are the articles contained in the request also valid in the price sheet of the MSB at the requested point in time | no | A04 | Cluster: Rejection The request contains at least one article that is not offered by the MSB |
| — | — | yes | → Step 60 | — |
| 60 | Is the MSB the active MSB at all affected locations? | no | A05 | Cluster: Rejection The MSB is not the assigned MSB at all locations |
| — | — | yes | → Step 70 | Create quotation |
| 70 | Is the ordered configuration possible at the affected location? | no | A06 | Cluster: Rejection Configuration is not possible at the location concerned |
| — | — | yes | → Step 75 | — |
| 75 | Have the lead times been met? Note: The maximum and the minimum lead time must be checked | no | A07 | Cluster: Rejection The lead time was not met. |
| — | — | yes | → Step 80 | — |
| 80 | 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 | End | Send quotation |
Result codes
| Result code | Cluster | Meaning |
|---|---|---|
A01 | Rejection | The ordered configuration already exists |
A02 | Rejection | Non-chargeable configuration |
A03 | Rejection | A configuration already exists at the location. The order placement does not contain the order number for the existing configuration. |
A04 | Rejection | The request contains at least one article that is not offered by the MSB |
A05 | Rejection | The MSB is not the assigned MSB at all locations |
A06 | Rejection | Configuration is not possible at the affected location |
A07 | Rejection | The lead time was not met. |
A99 | Rejection | Other Note: The identified problem is to be described/named in the response. End of usability: 01.10.2026 00:00 |
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.