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

Marktrolle **MSB** · 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_35001](/schnittstellen/202604/pruefi/REQOTE/PI_35001) | REQOTE | Request for device takeover quotation | WiM gas | MSBN → MSBA |

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="Anfrage Geräteübernahmeangebot">35001</span> | Condition |
|---|---|---|---|---|
| <span className="hbs-g hbs-e0">**stammdaten**</span> | — | object | May | — |
| <span className="hbs-g hbs-e1">**MESSLOKATION** <span className="hbs-liste">[ ]</span> <span className="hbs-pflicht">\*</span></span> | — | object[] | Must | — |
| <span className="hbs-f hbs-e2">[messlokationsId](/en/bo4e/202604/bo/Messlokation#messlokationsid) <span className="hbs-pflicht">\*</span></span><span className="hbs-nr">00010</span> | The metering location identification. This is the former metering point identifier,<br/>e.g. DE 47108151234567 | string | Must | — |

</div>

</Handbuchsatz>

## Chain of this trigger

The event triggers the message.

| Message | Responses | Write call after the response |
|---|---|---|
| [35001](/schnittstellen/202604/pruefi/REQOTE/PI_35001) | — | — |

This event triggers steps in these role views:

| Process | Party involved | Rulebook | Division |
|---|---|---|---|
| [Device takeover](/en/prozessdoku/202604/MSB--MSBN/awh-wim-gas-2-0-gerateubernahme) | MSBN | AWH WiM gas 2.0 | Gas |
| [Device takeover](/en/prozessdoku/202604/MSB--MSBN/WiM-Teil1-geraeteuebernahme) | MSBN | 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 |
|---|---|---|---|
| [gueltigAb](/en/bo4e/202604/cdoc/Transaktionsdaten#gueltigab) | string (date-time) | **yes** | Effective date/time / DTM+7 |
| [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 — 35001. Possible values: `35001` |
| [absender › 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) |
| [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_GERAETEUEBERNAHME**. 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_GERAETEUEBERNAHME` | **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).