# [LF] START_STORNO_SE_AUFTRAG
<span hidden data-pagefind-meta={"title:Trigger event START_STORNO_SE_AUFTRAG — Market role LF (FV 202604)"} />

Marktrolle **LF** · Formatversion **202604** · 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_39000](/schnittstellen/202604/pruefi/ORDCHG/PI_39000) | ORDCHG | Cancellation of disconnection/reconnection order | AWH disconnection processes gas | 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.

<Handbuchsatz>

<div className="maco-tabellenrahmen">

| Structure (BO4E) | Description | Format | <span className="hbs-p" title="Stornierung Sperr-/Entsperrauftrag">39000</span> | Condition |
|---|---|---|---|---|
| <span className="hbs-g hbs-e0">**stammdaten**</span> | — | object | May | — |
| <span className="hbs-g hbs-e1">**ANFRAGE** <span className="hbs-liste">[ ]</span> <span className="hbs-pflicht">\*</span></span> | — | object[] | Must | — |
| <span className="hbs-f hbs-e2">[anfragekategorie](/en/bo4e/202604/bo/Anfrage#anfragekategorie) <span className="hbs-pflicht">\*</span></span><span className="hbs-nr">00010</span> | Category of the request (ORDERS ORDRSP BGM 1001) | [Enum Anfragekategorie](/en/bo4e/202604/enum/Anfragekategorie) | Must | — |
| <span className="hbs-w hbs-e3">`PROZESSDATENBERICHT`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`GERAETEUEBERNAHME`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`WEITERVERPFLICHTUNG_BETRIEB_MELO`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`AENDERUNG_MELO`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`STAMMDATEN_MALO_ODER_MELO`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`BILANZIERTE_MENGE_MEHR_MINDER_MENGEN`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`ALLOKATIONSLISTE_MEHR_MINDER_MENGEN`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`ENERGIEMENGE_UND_LEISTUNGSMAXIMUM`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`ABRECHNUNG_MESSSTELLENBETRIEB_MSB_AN_LF`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`AENDERUNG_PROGNOSEGRUNDLAGE_GERAETEKONFIGURATION`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`AENDERUNG_GERAETEKONFIGURATION`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`REKLAMATION_VON_WERTEN`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`LASTGANG_MALO_TRANCHE`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`SPERRUNG`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`ENTSPERRUNG`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`REKLAMATION_ZAEHLZEITDEFINITION`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`ZEITREIHEN_IM_RAHMEN_BILANZKREISABRECHNUNG`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`GERAETEWECHSELABSICHT`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`AENDERUNG_KONZESSIONSABGABE`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`AENDERUNG_ZAEHLZEITDEFINITION`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`UEBERMITTLUNG_WERTE_AN_ESA`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`AENDERUNG`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`BILANZKREISZUORDNUNGSLISTE`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`CLEARINGLISTE`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`NORMIERTES_PROFIL_PROFILSCHAR`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`REDISPATCH_EINZELZEITREIHE_AUSFALLARBEIT`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`REKLAMATION_PROFIL_PROFILSCHAR`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`STAMMDATEN_MALO`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`STAMMDATEN_MELO`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`STAMMDATEN_TRANCHE`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`BEENDIGUNG_EINER_KONFIGURATION`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`BESTELLUNG_EINER_KONFIGURATION`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`BESTELLUNG_EINES_ANGEBOTS_EINER_KONFIGURATION`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`REKLAMATION_EINER_KONFIGURATION`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`BESTELLUNG_AENDERUNG_NETZENTGELTE_NETZORIENTIERTER_STEUERUNGSMOEGLICHKEIT`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`AENDERUNG_DER_TECHNIK_DER_LOKATION`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`AENDERUNG_INDIVIDUELLER_KONFIGURATION`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`BESTELLUNG_AENDERUNG_ABRECHNUNGSDATEN`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`EINRICHTUNG_KONFIGURATION_AUFGRUND_ZUORDNUNG_LF`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`REKLAMATION_DEFINITION`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`BESTELLUNG_ANGEBOT_AENDERUNG_TECHNIK_LOKATION`</span> | — | — | Must | — |

</div>

</Handbuchsatz>

## 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 |
|---|---|---|
| [39000](/schnittstellen/202604/pruefi/ORDCHG/PI_39000) | [19128](/schnittstellen/202604/pruefi/ORDRSP/PI_19128), [19129](/schnittstellen/202604/pruefi/ORDRSP/PI_19129) | `POST /updateProcessData` |

This event triggers steps in these role views:

| Process | Party involved | Rulebook | Division |
|---|---|---|---|
| [Cancellation of the interruption and restoration of grid connection use on instruction of the LF](/en/prozessdoku/202604/LF/awh-sperrprozesse-gas-stornieren-der-unterbrechung-und-wiederherstellung-der-anschlussnutzung-auf-anweisung-des-lf) | LF | AWH disconnection processes gas | Gas |
| [Cancellation of the interruption and restoration of grid connection use on instruction of the LF](/en/prozessdoku/202604/LF/GPKE-Teil2-stornieren-der-unterbrechung-und-wiederherstellung-der-anschlussnutzung-auf-anweisung-des-lf) | LF | 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 |
|---|---|---|---|
| [auftragsReferenz](/en/bo4e/202604/cdoc/Transaktionsdaten#auftragsreferenz) | string | **yes** | Order number 'purchasing' / RFF+ON |
| [kategorie](/en/bo4e/202604/cdoc/Transaktionsdaten#kategorie) | string | **yes** | Qualifier from the beginning of the EDIFACT message / BGM |
| [sparte](/en/bo4e/202604/cdoc/Transaktionsdaten#sparte) | [Enum Sparte](/en/bo4e/202604/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 — 39000. Possible values: `39000` |
| [absender › rollencodenummer](/en/bo4e/202604/bo/Marktteilnehmer#rollencodenummer) | string | no | Specifies the code value of the market role. |
| [empfaenger › marktrolle](/en/bo4e/202604/bo/Marktteilnehmer#marktrolle) | [Enum Marktrolle](/en/bo4e/202604/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](/en/bo4e/202604/bo/Marktteilnehmer#rollencodenummer) | string | no | Specifies the code value of the market role. |

## Additional data

`eventname` is fixed to **START_STORNO_SE_AUFTRAG**. 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_STORNO_SE_AUFTRAG` | **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](/en/schnittstellen/schluessel).