[LF] START_BEENDIGUNG_RECHNUNG_MSB
Marktrolle LF · Formatversion 202610 · BO4E-Schema 1.7.8
Master data
Exactly one of the following 1 check identifiers is permitted under this topic — which one is decided by the event process.
| Prüfi | Scope | Use case | Regulatory determination | Communication |
|---|---|---|---|---|
| PI_17006 | ORDERS | Termination of invoice processing MSB via LF | WiM electricity part 1 | MSB (corresponds to MSB on the object market location) → LF |
The master data of the 1 check identifier 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 | 17006 | Condition |
|---|---|---|---|---|
| stammdaten | — | object | May | — |
| ANFRAGE [ ] * | — | object[] | Must | — |
| abonnement *00010 | Start or end of subscription | Enum Abonnement | Must | — |
START_ABO | — | — | Must | — |
ENDE_ABO | — | — | Must | — |
OHNE_ABO | — | — | Must | — |
| lokationsId *00020 | Which market or metering location this request applies to. | string | Must | — |
| AUFTRAG [ ] * | — | object[] | Must | — |
| ausfuehrungsdatum *00030 | The execution date describes at which point in time an order is to be executed. | string (date-time) | Must | — |
| positionsdaten [ ] | — | object[] | May | — |
| anfragegrund00040 | Request reason | Enum Anfragegrund | May | — |
ABGRENZUNG_VON_ENERGIEMENGEN | — | — | May | — |
ABGRENZUNG | — | — | May | — |
WECHSELEREIGNIS | — | — | May | — |
ZWISCHENABLESUNG | — | — | May | — |
DIREKTER_VERTRAG_MSB_AN | — | — | May | — |
DIREKTER_VERTRAG_MSB_ANN | — | — | May | — |
AENDERUNG_IM_LOKATIONSBUENDEL | — | — | May | — |
NEUKONFIGURATION | — | — | May | — |
KONFIGURATION_UNVERAENDERT | — | — | May | — |
Chain of this trigger
The event triggers the message. The market partner responds with one of the responses listed, and after that the MACO APP writes the transaction to your backend system.
| Message | Responses | Write call after the response |
|---|---|---|
| 17006 | 19009, 19010 | POST /updateProcessData (derived) |
This event triggers a step in this role view:
| Process | Party involved | Rulebook | Division |
|---|---|---|---|
| Termination of invoicing for metering point operation via the LF by the LF | LF | WiM electricity part 1 | Electricity |
Transaction data
The interchange envelope of the message. Mandatory fields must be set on the trigger call.
| Field | Type | Mandatory | Description |
|---|---|---|---|
pruefidentifikator | — | no | Determined dynamically in the event process. A value supplied by the sender is ignored. Prüfis possible in the topic — 17006. Possible values: 17006 |
Additional data
eventname is fixed to START_BEENDIGUNG_RECHNUNG_MSB. 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_BEENDIGUNG_RECHNUNG_MSB | 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.