[LF] START_REKLAMATION_DEFINITIONEN
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_17122 | ORDERS | Complaint about a definition | GPKE part 3 | LF → NB |
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 | 17122 | Condition |
|---|---|---|---|---|
| stammdaten | — | object | May | — |
| AUFTRAG [ ] * | — | object[] | Must | — |
| positionsdaten [ ] * | — | object[] | Must | — |
| definitionsTyp *00010 | DefinitionsType | Enum DefinitionsTyp | Must | — |
ZAEHLZEIT | — | — | Must | — |
SCHALTZEIT | — | — | Must | — |
LEISTUNGSKURVEN | — | — | Must | — |
| positionsnummer *00020 | Line item number | integer | Must | — |
| LEISTUNGSKURVENDEFINITION [ ] | — | object[] | May | — |
| leistungskurven [ ] | — | object[] | May | — |
| code00030 | Code of the power curve | string | May | — |
| REKLAMATION [ ] * | — | object[] | Must | — |
| reklamationsgrund *00040 | This specifies the reason for the complaint about values. | Enum Reklamationsgrund | Must | — |
WERTE_ZU_HOCH | — | — | Must | — |
WERTE_ZU_NIEDRIG | — | — | Must | — |
WERTE_FEHLEN | — | — | Must | — |
KONFIGURATION_WIRKT_NICHT | — | — | Must | — |
KONFIGURATION_WIRKT_TEILWEISE | — | — | Must | — |
WERTE_WERDEN_NICHT_NACH_VORGABEN_UEBERMITTELT | — | — | Must | — |
UEBERSICHT_FEHLT | — | — | Must | — |
UEBERSICHT_UNPLAUSIBEL | — | — | Must | — |
AUSGEROLLTE_DEFINITION_FEHLT | — | — | Must | — |
AUSGEROLLTE_DEFINITION_UNPLAUSIBEL | — | — | Must | — |
| reklamationsgrundBemerkung | — | object | May | — |
| bemerkung100050 | bemerkung1 | string | May | — |
| bemerkung200060 | bemerkung2 | string | May | — |
| bemerkung300070 | bemerkung3 | string | May | — |
| bemerkung400080 | bemerkung4 | string | May | — |
| bemerkung500090 | bemerkung5 | string | May | — |
| SCHALTZEITDEFINITION [ ] | — | object[] | May | — |
| schaltzeiten [ ] | — | object[] | May | — |
| code00100 | code | string | May | — |
| ZAEHLZEITDEFINITION [ ] | — | object[] | May | — |
| zaehlzeiten [ ] | — | object[] | May | — |
| code00110 | Metering time period definition | string | 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 |
|---|---|---|
| 17122 | 19123 | POST /updateProcessData (derived) |
This event triggers steps in these role views:
| Process | Party involved | Rulebook | Division |
|---|---|---|---|
| Complaint about the overview of the definitions of the NB from LF to NB | LF | GPKE part 3 | Electricity |
| Complaint about a definition of the NB from LF to NB | LF | GPKE part 3 | Electricity |
Transaction data
The interchange envelope of the message. Mandatory fields must be set on the trigger call.
| Field | Type | Mandatory | Description |
|---|---|---|---|
| kategorie | string | yes | Qualifier from the beginning of the EDIFACT message / BGM |
| sparte | Enum Sparte | yes | Contains information about the division Values: STROM, GAS, FERNWAERME, NAHWAERME, WASSER, ABWASSER |
pruefidentifikator | — | no | Determined dynamically in the event process. A value supplied by the sender is ignored. Prüfis possible in the topic — 17122. Possible values: 17122 |
| absender › rollencodenummer | string | no | Specifies the code value of the market role. |
| empfaenger › rollencodenummer | string | no | Specifies the code value of the market role. |
Additional data
eventname is fixed to START_REKLAMATION_DEFINITIONEN. 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_REKLAMATION_DEFINITIONEN | 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.