# E_0595 — Check order placement
Check order placement
| Attribute | Value |
|---|---|
| Designation | Check order placement |
| Market role | NB |
| Regulatory determination / chapter | GPKE |
| Section | 6.17.1: AD: Order placement for a change of billing data from LF to NB |
| Check identifiers | checked: [17133](/en/schnittstellen/202610/pruefi/ORDERS/PI_17133), [55673](/en/schnittstellen/202610/pruefi/UTILMD/PI_55673) · response: [19133](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19133), [21047](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21047) |
| EBD version | 4.3 |
| As at | — |
## Decision tree
\nDecision tree E_0595: Bestellung prüfen\n\n\n\nE_0595\nBestellung prüfen\nChecking role: NB\n\nyes\n\nno\n\nyes\n\nno\n\nno\n\nyes\n\nyes\n\nno\n\nyes\n\nno\n\nyes\n\nno\n\nyes\n\nno\n\nno\n\nyes\n\nyes\n\nno\n\nno\n\nyes\n\nyes\n\nno\n\nno\n\nyes\n\nyes\n\nno\n\nyes\n\nno\n\nyes\n\nno\n\nyes\n\nno\n\nyes\n\nno\n\nno\n\nyes\n\nyes\n\nno\n\nno\n\nyes\n\nyes\n\nno\n\n\n10\nHandelt es sich bei dem\nAnwendungsfall um eine\nBestellung mittels ORDERS?\n\n\n15\nHandelt es sich um eine\nBestellung Änderung Netzentgelte\naufgrund netzorientierter\nSteuerungsmöglichkeit?\n\n\n17\nWurde die Vorlauffrist von\nmindestens 2 WT vor dem\nÄnderungszeitpunkt eingehalten?\n\n\nA21\nCluster: no change to the data\nDie Frist zur Änderung wurde nicht\neingehalten\n\n\n30\nHandelt es sich um eine\nBestellung Änderung\nKonzessionsabgabe?\n\n\n40\nIst der Marktlokation zum\nZeitpunkt der bestellten Änderung\ndie Sondervertragskunden-KA\nzugeordnet? Hinweis: Wenn der\nMarktlokation zum Zeitpunkt der\nbestellten Änderung die\nSondervertragskunden-KA\nzugeordnet ist und die Kriterien\nnach § 2 Abs. 7 KAV wurden nicht\nerreicht, so ist diese Frage mit\n„nein“ zu beantworten.\n\n\nA23\nCluster: no change to the data\nSondervertragskunden-KA gemäß § 2\nAbs. 3 der\nKonzessionsabgabenverordnung,\ndaher keine Änderung möglich.\n\n\n50\nIst die Marktlokation von der\nKonzessionsabgabe befreit?\n\n\nA24\nCluster: no change to the data\nÄnderung nicht möglich, da\nMarktlokation von\nKonzessionsabgabe befreit ist.\n\n\n55\nIst der bestellte Zustand an der\nMarktlokation bereits vorhanden?\n\n\nA25\nCluster: no change to the data\nDer gewünschte Zustand ist bereits\nan der Marktlokation hinterlegt.\n\n\n60\nBestellt der LF für eine\nMarktlokation den Wechsel auf\neine\nSchwachlast-Konzessionsabgabe?\n\n\n65\nMöchte der NB die Bestellung der\nrückwirkenden Änderung der\nKonzessionsabgabe aufgrund\nrechtlicher Fristen ablehnen?\n\n\nA26\nCluster: no change to the data\nEine rückwirkende Änderung wird\nabgelehnt.\n\n\n70\nLässt die Gerätekonfiguration der\nMesslokationen der angefragten\nMarktlokation zum\nUmsetzungszeitpunkt die\nseparate Erfassung der Energie in\nden Schwachlastzeiten zu, um die\nniedrige Konzessionsabgabe für\ndiese Menge abrechnen zu\nkönnen?\n\n\nA27\nCluster: no change to the data\nAn der Marktlokation kann die\nEnergie in den Schwachlastzeiten\nnicht zum angefragten Zeitpunkt\nseparat erfasst werden.\n\n\n90\nHandelt es sich um eine\nBestellung Änderung Bilanzkreis\nbzw. Jahresverbrauchsprognose?\n\n\n100\nWurde die Vorlauffrist von\nmindestens 7 WT vor dem\nÄnderungszeitpunkt eingehalten?\n\n\nA22\nCluster: no change to the data\nDie Frist zur Änderung von\nBilanzkreis oder\nJahresverbrauchsprognose wurde\nnicht eingehalten.\n\n\n105\nHandelt es sich um eine\nBestellung Änderung Bilanzkreis?\n\n\n110\nIst der Bilanzkreis zum\nangegebenen Zeitpunkt in der\nRegelzone gültig?\n\n\nA28\nCluster: no change to the data\nBilanzkreis nicht gültig.\n\n\n120\nIst der Bilanzkreis und der\nerforderliche Zeitreihentyp in der\nZuordnungsermächtigung\naufgeführt?\n\n\nA29\nCluster: no change to the data\nBilanzkreis und der erforderliche\nZeitreihentyp ist in der\nZuordnungsermächtigung nicht\naufgeführt.\n\n\n200\nKonnte die Bestellung umgesetzt\nwerden?\n\n\nA20\nCluster: Change of the data\nDer Bestellung der Stammdaten\nkonnte zugestimmt werden.\nHinweis: NB versendet neue\nStammdaten\n\n\nA99\nCluster: no change to the data\nDer Bestellung der Stammdaten\nkonnte nicht zugestimmt werden.\nHinweis: Das identifizierte Problem\nist in der Antwort zu\nbeschreiben/benennen.\nNutzungsmöglichkeit Ende: offen\n\n\n210\nStimmen alle Stammdaten für\nVerwendungszeiträume, welche\nmit „Im System vorhandene\nDaten“ gekennzeichnet sind,\nsowie Verwendungszeiträume\nwelche mit „Im System keine\nDaten vorhanden“ gekennzeichnet\nsind, mit dem beim\nVerantwortlichen vorliegenden\nStammdaten überein? Hinweis:\nDies ist für jeden in der Anfrage\nvorhandenen\nVerwendungszeitraum jeweils für\nden gesamten Zeitraum zu prüfen.\n\n\n220\nSind in der Bestellung der\nStammdatenänderung\nVerwendungszeiträume der Daten\nmit dem Code „Erwartete Daten“\nund / oder „Keine Daten erwartet“\nenthalten?\n\n\nA01\nCluster: no change to the data\nDer Verantwortliche teilt in dem\nBearbeitungsstand der Stammdaten\nmit:\n- Die beim Berechtigten vorliegenden\nDaten stimmen mit den Daten des\nVerantwortlichen überein.\n- Es wurden keine Stammdaten zur\nÄnderung angegeben.\nEine Stammdatenänderung wird nicht\nversendet.\n\n\n230\nKommt der Verantwortliche zu\ndem Ergebnis, dass er\nÄnderungen an seinen\nStammdaten vornimmt?\n\n\nA02\nCluster: Change of the data\nDer Verantwortliche teilt in dem\nBearbeitungstand der Stammdaten\nmit:\n- Die beim Berechtigten vorliegenden\nDaten stimmen mit den Daten des\nVerantwortlichen überein.\n- Änderungen an den Stammdaten\nwerden vorgenommen.\nEine Stammdatenänderung wird\nversendet.\n\n\nA03\nCluster: no change to the data\nDer Verantwortliche teilt in dem\nBearbeitungsstand der Stammdaten\nmit:\n- Die beim Berechtigten vorliegenden\nDaten stimmen mit den Daten des\nVerantwortlichen überein.\n- Änderungen an den Stammdaten\nwerden nicht vorgenommen.\nEine Stammdatenänderung wird nicht\nversendet.\n\n\n240\nSind in der Bestellung der\nStammdatenänderung\nVerwendungszeiträume der Daten\nmit dem Code „Erwartete Daten“\nund / oder „Keine Daten erwartet“\nenthalten?\n\n\nA04\nCluster: Change of the data\nDer Verantwortliche teilt in dem\nBearbeitungsstand der Stammdaten\nmit:\n- Die beim Berechtigten vorliegenden\nDaten stimmen mit den Daten des\nVerantwortlichen nicht überein.\n- Es wurden keine Stammdaten zur\nÄnderung angegeben.\nEine Stammdatenänderung wird\nversendet.\n\n\n250\nKommt der Verantwortliche zu\ndem Ergebnis, dass er\nÄnderungen an seinen\nStammdaten vornimmt?\n\n\nA05\nCluster: Change of the data\nDer Verantwortliche teilt in dem\nBearbeitungsstand der Stammdaten\nmit:\n- Die beim Berechtigten vorliegenden\nDaten stimmen mit den Daten des\nVerantwortlichen nicht überein.\n- Änderungen an den Stammdaten\nwerden vorgenommen.\nEine Stammdatenänderung wird\nversendet.\n\n\nA06\nCluster: Change of the data\nDer Verantwortliche teilt in dem\nBearbeitungsstand der Stammdaten\nmit:\n- Die beim Berechtigten vorliegenden\nDaten stimmen mit den Daten des\nVerantwortlichen nicht überein.\n- Änderungen an den Stammdaten\nwerden nicht vornehmen\nEine Stammdatenänderung wird\nversendet.\n"} kapitel={"GPKE · 6.17.1: AD: Bestellung einer Änderung von Abrechnungsdaten von LF an NB"} name={"Bestellung prüfen"} bpmnFv="202610" bpmnCode="E_0595">
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 10 | Is the use case an order placement by means of ORDERS? | yes | → Step 15 | Note: Order placement for master data by means of ORDERS |
| — | — | no | → Step 210 | Note: Order placement for the master data clearing by means of UTILMD |
| 15 | Is this an order placement for a change of grid fees due to grid-oriented control capability? | yes | → Step 17 | — |
| — | — | no | → Step 30 | — |
| 17 | Was the lead time of at least 2 WT before the point in time of the change met? | no | A21 | Cluster: no change of data The deadline for the change was not met |
| — | — | yes | → Step 200 | — |
| 30 | Is this an order placement for a change of concession levy? | yes | → Step 40 | — |
| — | — | no | → step 90 | — |
| 40 | Is the special contract customer concession levy assigned to the market location at the point in time of the ordered change? Note: If the special contract customer concession levy is assigned to the market location at the point in time of the ordered change and the criteria under § 2 para. 7 KAV have not been met, this question is to be answered with “no”. | yes | A23 | Cluster: no change of data Special contract customer concession levy pursuant to § 2 (3) of the Konzessionsabgabenverordnung, therefore no change possible. |
| — | — | no | → Step 50 | — |
| 50 | Is the market location exempt from the concession levy? | yes | A24 | Cluster: no change of data Change not possible because the market location is exempt from the concession levy. |
| — | — | no | → Step 55 | — |
| 55 | Is the ordered state already present at the market location? | yes | A25 | Cluster: no change of data The requested state is already recorded at the market location. |
| — | — | no | → Step 60 | — |
| 60 | Does the LF order the change to an off-peak concession levy for a market location? | no | → Step 200 | Master data change originating from NB (responsible) Note: The LF instructs the NB to stop billing the off-peak concession levy at the market location from the specified point in time. The regular concession levy is to be billed. |
| — | — | yes | → Step 65 | — |
| 65 | Does the NB want to reject the order placement of the retroactive change to the concession levy on account of legal deadlines? | yes | A26 | Cluster: no change of data A retroactive change is rejected. |
| — | — | no | → Step 70 | — |
| 70 | Does the device configuration of the metering locations of the requested market location permit, at the implementation date, the separate recording of the energy during off-peak periods so that the reduced concession levy can be billed for this quantity? | no | A27 | Cluster: no change of data At the market location, the energy in the off-peak periods cannot be recorded separately at the requested point in time. |
| — | — | yes | → Step 200 | — |
| 90 | Is this an order placement for a change of balancing group or annual consumption forecast? | yes | → Step 100 | — |
| — | — | no | → Step 200 | — |
| 100 | Was the lead time of at least 7 WT before the point in time of the change met? | no | A22 | Cluster: no change of data The deadline for changing the balancing group or the annual consumption forecast was not met. |
| — | — | yes | → Step 105 | — |
| 105 | Is this an order placement for a change of balancing group? | yes | → Step 110 | — |
| — | — | no | → Step 200 | Note: This is an order placement for a change of the annual consumption forecast. |
| 110 | Is the balancing group valid in the control area at the specified point in time? | yes | → Step 120 | — |
| — | — | no | A28 | Cluster: no change of data Balancing group not valid. |
| 120 | Are the balancing group and the required time series type listed in the allocation authorization? | yes | → Step 200 | — |
| — | — | no | A29 | Cluster: no change of data Balancing group and the required time series type are not listed in the allocation authorization. |
| 200 | Could the order placement be implemented? | yes | A20 | Cluster: change of data The order placement of the master data could be consented to. Note: NB sends new master data |
| — | — | no | A99 | Cluster: no change of data The order placement of the master data could not be consented to. Note: The identified problem must be described/named in the response. End of usability: open |
| 210 | Does all master data for usage periods marked “Data available in the system”, as well as usage periods marked “No data available in the system”, match the master data held by the responsible party? Note: This is to be checked for each usage period contained in the request, in each case for the entire time period. | yes | → Step 220 | — |
| — | — | no | → Step 240 | — |
| 220 | Does the order placement of the master data change contain usage periods of the data with the code “Expected data” and / or “No data expected”? | no | A01 | Cluster: no change of data In the processing status of the master data, the responsible party states: - The data held by the authorized party matches the data of the responsible party. - No master data was specified for change. No master data change is sent. |
| — | — | yes | → Step 230 | — |
| 230 | Does the responsible party conclude that it will make changes to its master data? | yes | A02 | Cluster: change of data In the processing status of the master data, the responsible party states: - The data held by the authorized party matches the data of the responsible party. - Changes are made to the master data. A master data change is sent. |
| — | — | no | A03 | Cluster: no change of data In the processing status of the master data, the responsible party states: - The data held by the authorized party matches the data of the responsible party. - No changes are made to the master data. No master data change is sent. |
| 240 | Does the order placement of the master data change contain usage periods of the data with the code “Expected data” and / or “No data expected”? | no | A04 | Cluster: change of data In the processing status of the master data, the responsible party states: - The data held by the authorized party does not match the data of the responsible party. - No master data was specified for change. A master data change is sent. |
| — | — | yes | → Step 250 | — |
| 250 | Does the responsible party conclude that it will make changes to its master data? | yes | A05 | Cluster: change of data In the processing status of the master data, the responsible party states: - The data held by the authorized party does not match the data of the responsible party. - Changes are made to the master data. A master data change is sent. |
| — | — | no | A06 | Cluster: change of data In the processing status of the master data, the responsible party states: - The data held by the authorized party does not match the data of the responsible party. - No changes to the master data will be made A master data change is sent. |
## Result codes
| Result code | Cluster | Meaning |
|---|---|---|
| `A21` | no change to the data | The deadline for the change was not met |
| `A23` | no change to the data | Special contract customer KA pursuant to § 2 para. 3 of the Concession Levy Ordinance, therefore no change possible. |
| `A24` | no change to the data | Change not possible because the market location is exempt from the concession levy. |
| `A25` | no change to the data | The requested state is already stored at the market location. |
| `A26` | no change to the data | A retroactive change is rejected. |
| `A27` | no change to the data | At the market location, the energy cannot be recorded separately during off-peak periods at the requested point in time. |
| `A22` | no change to the data | The deadline for changing the balancing group or the annual consumption forecast was not met. |
| `A28` | no change to the data | Balancing group not valid. |
| `A29` | no change to the data | Balancing group and the required time series type are not listed in the allocation authorization. |
| `A20` | Change of the data | The order placement for the master data could be approved. Note: NB sends new master data |
| `A99` | no change to the data | The order placement for the master data could not be approved. Note: the identified problem is to be described/named in the response. End of usability: open |
| `A01` | no change to the data | In the processing status of the master data, the responsible party reports: - The data held by the authorised party matches the data of the responsible party. - No master data was specified for change. A master data change is not sent. |
| `A02` | Change of the data | In the processing status of the master data, the responsible party reports: - The data held by the authorised party matches the data of the responsible party. - The master data is changed. A master data change is sent. |
| `A03` | no change to the data | In the processing status of the master data, the responsible party reports: - The data held by the authorised party matches the data of the responsible party. - The master data is not changed. A master data change is not sent. |
| `A04` | Change of the data | In the processing status of the master data, the responsible party reports: - The data held by the authorised party does not match the data of the responsible party. - No master data was specified for change. A master data change is sent. |
| `A05` | Change of the data | In the processing status of the master data, the responsible party reports: - The data held by the authorised party does not match the data of the responsible party. - The master data is changed. A master data change is sent. |
| `A06` | Change of the data | In the processing status of the master data, the responsible party reports: - The data held by the authorised party does not match the data of the responsible party. - The master data is not changed A master data change is sent. |
*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.*
:::warning{title="Deviation from the generated process"}
The following result codes are in the decision tree but are **not contained in the generated BPMN**: `A22`.
Checked against `E_0595.bpmn`. This is a known behavior of the process generation (review of 06.07.2026: pass-through result codes are discarded). The note is here so that the deviation is visible and does not surface only in operation.
:::