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

Marktrolle **NB** · 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_29002](/schnittstellen/202604/pruefi/COMDIS/PI_29002) | COMDIS | Rejection IFTSTA | GPKE part 2 | NB → 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.

<Handbuchsatz>

<div className="maco-tabellenrahmen">

| Structure (BO4E) | Description | Format | <span className="hbs-p" title="Ablehnung IFTSTA">29002</span> | Condition |
|---|---|---|---|---|
| <span className="hbs-g hbs-e0">**stammdaten**</span> | — | object | May | — |
| <span className="hbs-g hbs-e1">**HANDELSUNSTIMMIGKEIT** <span className="hbs-liste">[ ]</span> <span className="hbs-pflicht">\*</span></span> | — | object[] | Must | — |
| <span className="hbs-f hbs-e2">[nummer](/en/bo4e/202604/bo/Handelsunstimmigkeit#nummer) <span className="hbs-pflicht">\*</span></span><span className="hbs-nr">00010</span> | Trade discrepancy number | string | Must | — |
| <span className="hbs-f hbs-e2">[typ](/en/bo4e/202604/bo/Handelsunstimmigkeit#typ) <span className="hbs-pflicht">\*</span></span><span className="hbs-nr">00020</span> | Specifies the type of trade discrepancy. | [Enum Handelsunstimmigkeitstyp](/en/bo4e/202604/enum/Handelsunstimmigkeitstyp) | Must | — |
| <span className="hbs-w hbs-e3">`HANDELSRECHNUNG`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`LIEFERSCHEIN_HANDELSUNSTIMMIGKEITSTYP`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`LIEFERSCHEIN_GRUND_ARBEITSPREIS`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`LIEFERSCHEIN_ARBEITS_LEISTUNGSPREIS`</span> | — | — | Must | — |
| <span className="hbs-g hbs-e2">**begruendung** <span className="hbs-pflicht">\*</span></span> | — | object | Must | — |
| <span className="hbs-f hbs-e3">[grund](/en/bo4e/202604/com/Handelsunstimmigkeitsbegruendung#grund) <span className="hbs-pflicht">\*</span></span><span className="hbs-nr">00030</span> | Reason for the trade discrepancy | [Enum Handelsunstimmigkeitsgrund](/en/bo4e/202604/enum/Handelsunstimmigkeitsgrund) | Must | — |
| <span className="hbs-w hbs-e4">`ANMELDUNG_BESTAETIGT`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`ABRECHNUNGSBEGINN_GLEICH_BESTAETIGTEM_VERTRAGSBEGINN`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`ABRECHNUNGSENDE_GLEICH_BESTAETIGTEM_VERTRAGSENDE`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`NN_MSCONS_UEBERSENDET`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`RICHTIGE_MESSWERTE_ENERGIEMENGEN_UEBERSENDET`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`SONSTIGES_SIEHE_BEGRUENDUNG`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`GUELTIGES_PREISBLATT_VERSENDET`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`GUELTIGER_SPERRAUFTRAG_VORHANDEN`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`KORREKTE_ARTIKEL_ID_IN_RECHNUNG`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`KORREKTER_PREIS_ZU_GUELTIGEM_PREISBLATT_IN_RECHNUNG`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`RECHNUNG_KORREKT_A05`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`RECHNUNG_KORREKT_A10`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`RECHNUNG_KORREKT_A11`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`GUELTIGES_PREISBLATT_FRISTGERECHT_VERSENDET`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`GUELTIGE_RECHNUNG_VORHANDEN`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`ARTIKEL_ID_FUER_VERZUGSKOSTEN_VERWENDET`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`KORREKTER_PREIS_IN_RECHNUNG_ABGERECHNET`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`GUELTIGES_PREISBLATT_BLINDARBEIT_VERSENDET`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`KORREKTE_ARTIKEL_ID_IST_ANGEGEBEN`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`RECHNUNG_BREGRUENDET_KORREKT`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`KORREKTE_ARTIKEL_ID_FUER_ABRECHNUNG_STORNIERTER_SPERRAUFTRAG_ANGEGEBEN`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`ABRECHNUNG_BLINDARBEIT_SPARTE_GAS_NICHT_RELEVANT`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`SONSTIGES`</span> | — | — | Must | — |
| <span className="hbs-f hbs-e3">[hinweis](/en/bo4e/202604/com/Handelsunstimmigkeitsbegruendung#hinweis) <span className="hbs-pflicht">\*</span></span><span className="hbs-nr">00040</span> | Note on the reason | string | Must | — |

</div>

</Handbuchsatz>

## Chain of this trigger

The event triggers the message.

| Message | Responses | Write call after the response |
|---|---|---|
| [29002](/schnittstellen/202604/pruefi/COMDIS/PI_29002) | — | — |

This event triggers a step in this role view:

| Process | Party involved | Rulebook | Division |
|---|---|---|---|
| [Transmission of the delivery note for grid usage settlement](/en/prozessdoku/202604/NB/GPKE-Teil2-uebermittlung-des-lieferscheins-zur-netznutzungsabrechnung) | 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 |
|---|---|---|---|
| [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 — 29002. Possible values: `29002` |
| [absender › rollencodenummer](/en/bo4e/202604/bo/Marktteilnehmer#rollencodenummer) | string | no | Specifies the code value of the market role. |
| [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_WIEDERSPRUCH_ABLEHNUNG**. 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_WIEDERSPRUCH_ABLEHNUNG` | **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).