[NB] START_ENDE_ZUORDNUNG
Marktrolle NB · Formatversion 202604 · BO4E-Schema 1.7.8
Master data
Exactly one of the following 2 check identifiers is permitted under this topic — which one is decided by the event process.
| Prüfi | Scope | Use case | Regulatory determination | Communication |
|---|---|---|---|---|
| PI_55037 | UTILMD | Termination of the assignment | GPKE part 2 | NB → LFA |
| PI_55611 | UTILMD | Termination of the assignment | GPKE part 2 | NB → MSB |
The master data of the 2 check identifiers in one structure — one column per check identifier, as in the application handbook. A value in the column means that the field belongs to this check identifier: Must where its specification requires it, otherwise May. An empty cell means »not part of it«, not »unknown«. The first one is preselected; the bar above the table adds the others.
| Structure (BO4E) | Description | Format | 55037 | 55611 | Condition |
|---|---|---|---|---|---|
| stammdaten | — | object | May | May | — |
| MARKTLOKATION [ ] | — | object[] | May | May | — |
| marktlokationsId00010 | Identification number of a market location at which energy is either consumed or generated | string | May | May | — |
| NETZNUTZUNGSVERTRAG [ ] | — | object[] | May | May | — |
| vertragsende00020 | Specifies when the contract (is expected to) end or was ended. | string (date-time) | May | May | — |
| vertragsbeginn00030 | Specifies when the contract begins. | string (date-time) | — | May | — |
| TRANCHE [ ] | — | object[] | May | — | — |
| tranchenId00040 | tranchenId | string | May | — | — |
| MESSLOKATION [ ] | — | object[] | — | May | — |
| messlokationsId00050 | The metering location identification. This is the former metering point identifier, e.g. DE 47108151234567 | string | — | May | — |
Chain of this trigger
The event triggers the message.
| Message | Responses | Write call after the response |
|---|---|---|
| 55037 | — | — |
| 55611 | — | — |
This event triggers steps in these role views:
| Process | Party involved | Rulebook | Division |
|---|---|---|---|
| Case 2: LF assignment for a EEG market location with DV obligation | NB | GPKE part 2 | Electricity |
| Case 3: LF assignment for KWKG market location with DV obligation or non-EEG/non-KWKG market location and market location is mapped without tranches | NB | GPKE part 2 | Electricity |
| Case 4: LF assignment for KWKG market location with DV obligation or non-EEG/non-KWKG market location and market location is mapped with tranches | NB | GPKE part 2 | Electricity |
| Start of supply | NB | GPKE part 2 | Electricity |
| End of supply from NB to LF | NB | GPKE part 2 | Electricity |
Transaction data
The interchange envelope of the message. Mandatory fields must be set on the trigger call.
| Field | Type | Mandatory | Description |
|---|---|---|---|
| sparte | Enum Sparte | yes | Contains information about the division Values: STROM, GAS, FERNWAERME, NAHWAERME, WASSER, ABWASSER |
| transaktionsgrund | string | yes | The transaction reason describes the business transaction for the category in more detail / UTILMD STS+7++###+ZW4+E03 |
| transaktionsgrundergaenzung | string | yes | Supplement to the transaction reason / UTILMD STS+7++E01+###+E03 |
pruefidentifikator | — | no | Determined dynamically in the event process (decision basis: marktrolle). A value supplied by the sender is ignored. Check identifiers possible in the topic — 55037, 55611. Possible values: 55037, 55611 |
| absender › rollencodenummer | string | no | Specifies the code value of the market role. |
| empfaenger › marktrolle | Enum Marktrolle | no | Specifies the designation of the market role as free text. Values: NB, LF, MSB, MSBA, GMSB, MDL, DL, BKV, UENB, KUNDE-SELBST-NN … (+9) |
| empfaenger › rollencodenummer | string | no | Specifies the code value of the market role. |
Additional data
eventname is fixed to START_ENDE_ZUORDNUNG. This value stays German in the English version as well, because Camunda correlates on it.
| Field | Type | Mandatory | Description |
|---|---|---|---|
prozessId | string | yes | — |
eventname | const START_ENDE_ZUORDNUNG | yes | — |
Response
The trigger assigns its own businessKey. The MACO APP adopts neither the businessKey nor the prozessId of the calling system as the identifier of the process instance. The businessKey of the response is created when the process starts and is new. The body of this call carries no businessKey field; there is thus no place where a key of your own could be passed in. The prozessId passed in (a mandatory field of this call) remains the document number of the backend: it comes back in zusatzdaten.prozessId of the callbacks — mandatory there only for MaloIdent (03002/03003), otherwise optional.
201 — Success. Success message for the process data API call.
| Field | Type | Mandatory | Description |
|---|---|---|---|
businessKey | string (uuid) | yes | Unique identifier of the business process |
message | string | yes | Message with details of the triggered event — example from the source: received event XXXXXXXXXXXX with id at 2024-08-08T12:58:22Z and started process with businessKey 4c7170ed-3518-41ee-8582-39ab65b00107 |
400 — Error. Error message for the process data API call.
| Field | Type | Mandatory | Description |
|---|---|---|---|
errorCode | string | no | Error identifier — example from the source: 400 |
message | string | no | Technical message — example from the source: Validation Failed |
Which body the callbacks updateProcessData and createProcessData send is measured against the NiFi flow of the MACO APP: {stammdaten, transaktionsdaten, zusatzdaten} without an interchange envelope, the businessKey inside zusatzdaten. This is not measured against a recorded call, and not for MaloIdent (03002/03003).
What distinguishes businessKey, prozessId and targetBusinessKey is explained on Keys and assignment.