NB (69)
E_0608 — Registration of an assignment
Registration of an assignment
| Attribute | Value |
|---|---|
| Designation | Registration of an assignment |
| Market role | NB |
| Regulatory determination / chapter | GPKE |
| Section | 6.5.1: AD: Creation |
| Check identifiers | checked: 55600 · response: 55602, 55604 |
| Check identifiers | checked: 55601 · response: 55603, 55605 |
| EBD version | 4.3 |
| As at | — |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 10 | Was the use case used for a consuming market location? | yes | → Step 20 | — |
| — | — | no | → Step 500 | — |
| 20 | Was the lead time met? | no | A01 | Cluster: Rejection Lead time was not met |
| — | — | yes | → Step 30 | — |
| 30 | Was exactly one market location determined with all information provided in the registration, exercising due diligence? Note: The NB checks, applying at least the standardized identification requirements (taking into account chapter 6. of the GPKE part 1 (see in particular b) and c))), whether the market location can be uniquely identified. | yes | → Step 40 | — |
| — | — | no | → Step 50 | — |
| 40 | Does the market location participate in market communication on the registration date? Note: market locations that do not participate in market communication are market locations that are decommissioned or market locations assigned to the "Model 2 for the option of charging-process-specific balancing allocation of energy quantities". | no | A02 | Cluster: Rejection The identified market location does not participate in market communication. Furthermore, this is not a creation. |
| — | — | yes | → Step 60 | — |
| 50 | Was more than one market location determined with all information provided in the registration, exercising due diligence? | no | → Step 110 | No market location determined |
| — | — | yes | → Step 55 | More than one market location determined |
| 55 | Does exactly one of the identified market locations participate in market communication? Note: market locations that do not participate in market communication are market locations that are decommissioned or market locations assigned to the "Model 2 for the option of charging-process-specific balancing allocation of energy quantities". | no | A08 | Cluster: Rejection No or multiple identification |
| — | — | yes | → Step 60 | — |
| 60 | Is this an initial commissioning? | no | A03 | Cluster: Rejection No creation, incorrect use case |
| — | — | yes | → Step 70 | — |
| 70 | Is a LF already assigned? | yes | A04 | Cluster: Rejection Incorrect use case, a LF is already assigned |
| — | — | no | → Step 80 | — |
| 80 | Is the market location assigned to the grid operator on the receipt date of the message? | no | A05 | Cluster: Rejection As at the receipt date of the notification, the market location is no longer in the grid area of the NB. |
| — | — | yes | → step 90 | — |
| 90 | Are all mandatory requirements of the LF met? Note: In particular, the required allocation authorization (balancing group/balancing procedure) is available | no | A06 | Cluster: Rejection Requirements cannot be met Note: The deviations must be named. |
| — | — | yes | → Step 130 | — |
| 110 | Was the registration (of the creation) received more than 60 WT ago? | yes | A07 | Cluster: Rejection Newly created market location could not be identified |
| — | — | no | → Step 30 | — |
| 130 | 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 | A09 | Cluster: Consent |
| 500 | Was the lead time met? | no | A10 | Cluster: Rejection Lead time was not met |
| — | — | yes | → Step 510 | — |
| 510 | Was exactly one market location determined with all information provided in the registration, exercising due diligence? Note: The NB checks, applying at least the standardized identification requirements (taking into account chapter 6. of the GPKE part 1 (see in particular b) and c))), whether the market location can be uniquely identified. | yes | → Step 520 | — |
| — | — | no | → Step 530 | — |
| 520 | Does the market location participate in market communication on the registration date? Note: market locations that do not participate in market communication are market locations that are decommissioned or market locations assigned to the " Model 2 for the option of charging-process-specific balancing allocation of energy quantities ". | no | A11 | Cluster: Rejection The identified market location does not participate in market communication. Furthermore, this is not a creation. |
| — | — | yes | → Step 540 | — |
| 530 | Was more than one market location determined with all information provided in the registration, exercising due diligence? | no | → Step 590 | No market location determined |
| — | — | yes | → Step 535 | More than one market location determined |
| 535 | Does exactly one of the identified market locations participate in market communication? A market location that participates in market communication is a market location to which a balancing group and a supplier are or can be assigned. | no | A17 | Cluster: Rejection No or multiple identification |
| — | — | yes | → Step 610 | — |
| 540 | Is this an initial commissioning? | no | A12 | Cluster: Rejection No creation, incorrect use case |
| — | — | yes | → Step 545 | — |
| 545 | Is the metering technology for quarter-hourly measurement available at all metering devices required to determine the energy quantity of the market location? Note: If the configuration for a quarter-hourly resolution does not yet exist, this configuration is set up via the UC “Setting up the configurations on the basis of an assignment of a LF to a market location or tranche”, which is called from this UC (creation), provided that the corresponding product was ordered by LF in SD step 1. | no | A19 | Cluster: Rejection Not all metering devices required for determining the energy quantity of the market location have the metering technology for quarter-hourly measurement. |
| — | — | yes | → Step 550 | — |
| 550 | Is a LF already assigned? | yes | A13 | Cluster: Rejection Incorrect use case, a LF is already assigned |
| — | — | no | → Step 560 | — |
| 560 | Is the market location assigned to the grid operator on the receipt date of the message? | no | A14 | Cluster: Rejection As at the receipt date of the notification, the market location is no longer in the grid area of the NB. |
| — | — | yes | → Step 570 | — |
| 570 | Are all mandatory requirements of the LF met? Note: In particular, the required allocation authorization (balancing group/balancing procedure) is available | no | A15 | Cluster: Rejection Requirements cannot be met Note: The deviations must be named. |
| — | — | yes | → Step 610 | — |
| 590 | Was the registration (of the creation) received more than 60 WT ago? | yes | A16 | Cluster: Rejection Newly created market location could not be identified |
| — | — | no | → Step 510 | — |
| 610 | 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 | A18 | Cluster: Consent |
Result codes
| Result code | Cluster | Meaning |
|---|---|---|
A01 | Rejection | Lead time was not met |
A02 | Rejection | Identified market location does not take part in market communication. Furthermore, this is not a creation. |
A08 | Rejection | No or multiple identification |
A03 | Rejection | Not a creation, wrong use case |
A04 | Rejection | Incorrect use case, a LF is already assigned |
A05 | Rejection | As of the receipt date of the notification, the market location is no longer in the grid area of the NB. |
A06 | Rejection | Requirements cannot be met Note: The deviations must be named. |
A07 | Rejection | Newly created market locations could not be identified |
A99 (2 outputs) | Rejection | Other Note: The identified problem is to be described/named in the response. End of usability: 01.04.2027 00:00 |
A09 | Consent | — |
A10 | Rejection | Lead time was not met |
A11 | Rejection | Identified market location does not take part in market communication. Furthermore, this is not a creation. |
A17 | Rejection | No or multiple identification |
A12 | Rejection | Not a creation, wrong use case |
A19 | Rejection | Not all measuring devices required to determine the energy quantity of the market location are equipped with the metering technology for quarter-hourly measurement. |
A13 | Rejection | Incorrect use case, a LF is already assigned |
A14 | Rejection | As of the receipt date of the notification, the market location is no longer in the grid area of the NB. |
A15 | Rejection | Requirements cannot be met Note: The deviations must be named. |
A16 | Rejection | Newly created market locations could not be identified |
A18 | Consent | — |
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 202610); »checked« is the difference set to it from the return path of the process steps.
Consistent with the generated process
All 20 result codes of the decision tree are contained in the generated process E_0608.bpmn.