# [MSB] START_GERAETEWECHSEL
Marktrolle **MSB** · 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_17009](/schnittstellen/202610/pruefi/ORDERS/PI_17009) | ORDERS | Notification of device replacement intent | WiM electricity part 1 | MSB (corresponds to MSBN on the object metering location) → MSB (corresponds to MSBA on the object metering location) |
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 | 17009 | Condition |
|---|---|---|---|---|
| **stammdaten** | — | object | May | — |
| **ANFRAGE** [ ] \* | — | object[] | Must | — |
| [anfragetyp](/en/bo4e/202610/bo/Anfrage#anfragetyp) \*00010 | Type/kind of the request (ORDERS ORDRSP IMD 7081) | [Enum Anfragetyp](/en/bo4e/202610/enum/Anfragetyp) | Must | — |
| `KAUF` | — | — | Must | — |
| `NUTZUNGSUEBERLASSUNG` | — | — | Must | — |
| `ABRECHNUNGSBRENNWERT_UND_ZUSTANDSZAHL` | — | — | Must | — |
| `LASTGANGDATEN` | — | — | Must | — |
| `ZAEHLERSTAENDE` | — | — | Must | — |
| `WERTEERMITTLUNG` | — | — | Must | — |
| `ENERGIEMENGE_EINZELWERT` | — | — | Must | — |
| `INNERHALB_DER_ARBEITSZEIT` | — | — | Must | — |
| `AUCH_AUSSERHALB_DER_ARBEITSZEIT` | — | — | Must | — |
| `WECHSEL_SAEMTLICHER_EINRICHTUNGEN` | — | — | Must | — |
| `TEILWEISER_WECHSEL` | — | — | Must | — |
| `AENDERUNG_ZAEHLZEITDEFINITION` | — | — | Must | — |
| `ABBESTELLUNG_ZAEHLZEITEN` | — | — | Must | — |
| `ABBESTELLUNG_MESSPRODUKT` | — | — | Must | — |
| `ANGEBOT_AUF_BASIS_PREISBLATT` | — | — | Must | — |
| `INDIVIDUELLES_ANGEBOT` | — | — | Must | — |
| `AENDERUNG_KONFIGURATION` | — | — | Must | — |
| `KANN_NICHT_ANGEBOTEN_WERDEN` | — | — | Must | — |
| `NEUKONFIGURATION` | — | — | Must | — |
| `BEENDIGUNG_KONFIGURATION` | — | — | Must | — |
| `AKTIVIERUNG_KONFIGURATION` | — | — | Must | — |
| [lokationsId](/en/bo4e/202610/bo/Anfrage#lokationsid) \*00020 | Which market or metering location this request applies to. | string | Must | — |
| **AUFTRAG** [ ] \* | — | object[] | Must | — |
| [ausfuehrungsdatum](/en/bo4e/202610/bo/Auftrag#ausfuehrungsdatum) \*00030 | The execution date describes at which point in time an order is to be executed. | string (date-time) | Must | — |
| **ZAEHLER** [ ] \* | — | object[] | Must | — |
| **geraete** [ ] \* | — | object[] | Must | — |
| [geraetenummer](/en/bo4e/202610/com/Geraet#geraetenummer) \*00040 | The number printed on the device, which is assigned by the MSB. | string | Must | — |
| [weitereGeraetenummern](/en/bo4e/202610/com/Geraet#weiteregeraetenummern)00050 | weitereGeraetenummern | array | May | — |
| **geraeteeigenschaften** \* | — | object | Must | — |
| [geraetetyp](/en/bo4e/202610/com/Geraeteeigenschaften#geraetetyp) \*00060 | List of possible billable device types | [Enum Geraetetyp](/en/bo4e/202610/enum/Geraetetyp) | Must | — |
| `WECHSELSTROMZAEHLER` | — | — | Must | — |
| `DREHSTROMZAEHLER` | — | — | Must | — |
| `ZWEIRICHTUNGSZAEHLER` | — | — | Must | — |
| `RLM_ZAEHLER` | — | — | Must | — |
| `IMS_ZAEHLER` | — | — | Must | — |
| `BALGENGASZAEHLER` | — | — | Must | — |
| `MAXIMUMZAEHLER` | — | — | Must | — |
| `MULTIPLEXANLAGE` | — | — | Must | — |
| `PAUSCHALANLAGE` | — | — | Must | — |
| `VERSTAERKERANLAGE` | — | — | Must | — |
| `SUMMATIONSGERAET` | — | — | Must | — |
| `IMPULSGEBER` | — | — | Must | — |
| `EDL_21_ZAEHLERAUFSATZ` | — | — | Must | — |
| `VIER_QUADRANTEN_LASTGANGZAEHLER` | — | — | Must | — |
| `MENGENUMWERTER` | — | — | Must | — |
| `STROMWANDLER` | — | — | Must | — |
| `SPANNUNGSWANDLER` | — | — | Must | — |
| `DATENLOGGER` | — | — | Must | — |
| `KOMMUNIKATIONSANSCHLUSS` | — | — | Must | — |
| `MODEM` | — | — | Must | — |
| `TELEKOMMUNIKATIONSEINRICHTUNG` | — | — | Must | — |
| `KOMMUNIKATIONSEINRICHTUNG` | — | — | Must | — |
| `DREHKOLBENGASZAEHLER` | — | — | Must | — |
| `TURBINENRADGASZAEHLER` | — | — | Must | — |
| `ULTRASCHALLZAEHLER` | — | — | Must | — |
| `WIRBELGASZAEHLER` | — | — | Must | — |
| `MODERNE_MESSEINRICHTUNG` | — | — | Must | — |
| `ELEKTRONISCHER_HAUSHALTSZAEHLER` | — | — | Must | — |
| `STEUEREINRICHTUNG` | — | — | Must | — |
| `TECHNISCHESTEUEREINRICHTUNG` | — | — | Must | — |
| `TARIFSCHALTGERAET` | — | — | Must | — |
| `RUNDSTEUEREMPFAENGER` | — | — | Must | — |
| `OPTIONALE_ZUS_ZAEHLEINRICHTUNG` | — | — | Must | — |
| `MESSWANDLERSATZ_IMS_MME` | — | — | Must | — |
| `KOMBIMESSWANDLER_IMS_MME` | — | — | Must | — |
| `TARIFSCHALTGERAET_IMS_MME` | — | — | Must | — |
| `RUNDSTEUEREMPFAENGER_IMS_MME` | — | — | Must | — |
| `TEMPERATUR_KOMPENSATION` | — | — | Must | — |
| `HOECHSTBELASTUNGS_ANZEIGER` | — | — | Must | — |
| `SONSTIGES_GERAET` | — | — | Must | — |
| `SMARTMETERGATEWAY` | — | — | Must | — |
| `STEUERBOX` | — | — | Must | — |
| `BLOCKSTROMWANDLER` | — | — | Must | — |
| `KOMBIMESSWANDLER` | — | — | Must | — |
| `MODEM_GSM` | — | — | Must | — |
| `ETHERNET_KOM` | — | — | Must | — |
| `PLC_COM` | — | — | Must | — |
| `MODEM_FESTNETZ` | — | — | Must | — |
| `DSL_KOM` | — | — | Must | — |
| `LTE_KOM` | — | — | Must | — |
| `DICHTEMENGENUMWERTER` | — | — | Must | — |
| `TEMPERATURMENGENUMWERTER` | — | — | Must | — |
| `ZUSTANDSMENGENUMWERTER` | — | — | Must | — |
| `MESSDATENREGISTRIERGERAET` | — | — | Must | — |
| `WANDLER` | — | — | Must | — |
| `BEFESTIGUNGSEINRICHTUNG` | — | — | Must | — |
## 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 |
|---|---|---|
| [17009](/schnittstellen/202610/pruefi/ORDERS/PI_17009) | [19015](/schnittstellen/202610/pruefi/ORDRSP/PI_19015), [19016](/schnittstellen/202610/pruefi/ORDRSP/PI_19016) | `AKTUALISIEREN_PROZESSDATEN_BASIS` |
This event triggers steps in these role views:
| Process | Party involved | Rulebook | Division |
|---|---|---|---|
| [Device replacement](/en/prozessdoku/202610/MSB--MSBN/awh-wim-gas-2-0-geratewechsel) | MSBN | AWH WiM gas 2.0 | Gas |
| [Device replacement](/en/prozessdoku/202610/MSB--MSBN/WiM-Teil1-geraetewechsel) | 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 |
|---|---|---|---|
| [kategorie](/en/bo4e/202610/cdoc/Transaktionsdaten#kategorie) | string | **yes** | Qualifier from the beginning of the EDIFACT message / BGM |
| [sparte](/en/bo4e/202610/cdoc/Transaktionsdaten#sparte) | [Enum Sparte](/en/bo4e/202610/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 — 17009. Possible values: `17009` |
| [absender › marktrolle](/en/bo4e/202610/bo/Marktteilnehmer#marktrolle) | [Enum Marktrolle](/en/bo4e/202610/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/202610/bo/Marktteilnehmer#rollencodenummer) | string | no | Specifies the code value of the market role. |
| [empfaenger › marktrolle](/en/bo4e/202610/bo/Marktteilnehmer#marktrolle) | [Enum Marktrolle](/en/bo4e/202610/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/202610/bo/Marktteilnehmer#rollencodenummer) | string | no | Specifies the code value of the market role. |
## Additional data
`eventname` is fixed to **START_GERAETEWECHSEL**. 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_GERAETEWECHSEL` | **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).