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

Marktrolle **NB** · 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_25006](/schnittstellen/202610/pruefi/UTILTS/PI_25006) | UTILTS | Transmission of overview of switching time definitions | GPKE part 3 | 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="Übermittlung Übersicht Schaltzeitdefinitionen">25006</span> | Condition |
|---|---|---|---|---|
| <span className="hbs-g hbs-e0">**stammdaten**</span> | — | object | May | — |
| <span className="hbs-g hbs-e1">**SCHALTZEITDEFINITION** <span className="hbs-liste">[ ]</span> <span className="hbs-pflicht">\*</span></span> | — | object[] | Must | — |
| <span className="hbs-f hbs-e2">[beginndatum](/en/bo4e/202610/bo/Schaltzeitdefinition#beginndatum) <span className="hbs-pflicht">\*</span></span><span className="hbs-nr">00010</span> | beginndatum | string (date-time) | Must | — |
| <span className="hbs-f hbs-e2">[notwendigkeit](/en/bo4e/202610/bo/Schaltzeitdefinition#notwendigkeit) <span className="hbs-pflicht">\*</span></span><span className="hbs-nr">00020</span> | DefinitionsNecessity | [Enum DefinitionenNotwendigkeit](/en/bo4e/202610/enum/DefinitionenNotwendigkeit) | Must | — |
| <span className="hbs-w hbs-e3">`ZAEHLZEITDEFINITIONEN_WERDEN_VERWENDET`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`ZAEHLZEITDEFINITIONEN_WERDEN_NICHT_VERWENDET`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`DEFINITIONEN_WERDEN_VERWENDET`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`DEFINITIONEN_WERDEN_NICHT_VERWENDET`</span> | — | — | Must | — |
| <span className="hbs-f hbs-e2">[version](/en/bo4e/202610/bo/Schaltzeitdefinition#version) <span className="hbs-pflicht">\*</span></span><span className="hbs-nr">00030</span> | version | string (date-time) | Must | — |
| <span className="hbs-g hbs-e2">**schaltzeiten** <span className="hbs-liste">[ ]</span></span> | — | object[] | May | — |
| <span className="hbs-f hbs-e3">[code](/en/bo4e/202610/com/Schaltzeit#code)</span><span className="hbs-nr">00040</span> | code | string | May | — |
| <span className="hbs-f hbs-e3">[haeufigkeit](/en/bo4e/202610/com/Schaltzeit#haeufigkeit)</span><span className="hbs-nr">00050</span> | HaeufigkeitSchaltzeit | [Enum HaeufigkeitSchaltzeit](/en/bo4e/202610/enum/HaeufigkeitSchaltzeit) | May | — |
| <span className="hbs-w hbs-e4">`EINMALIG`</span> | — | — | May | — |
| <span className="hbs-w hbs-e4">`JAEHRLICH`</span> | — | — | May | — |
| <span className="hbs-f hbs-e3">[uebermittelbarkeit](/en/bo4e/202610/com/Schaltzeit#uebermittelbarkeit)</span><span className="hbs-nr">00060</span> | Switching time transmissibility | [Enum UebermittelbarkeitSchaltzeit](/en/bo4e/202610/enum/UebermittelbarkeitSchaltzeit) | May | — |
| <span className="hbs-w hbs-e4">`ELEKTRONISCH`</span> | — | — | May | — |
| <span className="hbs-w hbs-e4">`NICHT_ELEKTRONISCH`</span> | — | — | May | — |

</div>

</Handbuchsatz>

## Chain of this trigger

The event triggers the message.

| Message | Responses | Write call after the response |
|---|---|---|
| [25006](/schnittstellen/202610/pruefi/UTILTS/PI_25006) | — | — |

This event triggers a step in this role view:

| Process | Party involved | Rulebook | Division |
|---|---|---|---|
| [Transmission of the overview of the definitions of the NB by the NB](/en/prozessdoku/202610/NB/GPKE-Teil3-uebermittlung-der-uebersicht-der-definitionen-des-nb-durch-den-nb) | NB | 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 |
|---|---|---|---|
| `pruefidentifikator` | — | no | Determined dynamically in the event process. A value supplied by the sender is ignored. Prüfis possible in the topic — 25006. Possible values: `25006` |

## Additional data

`eventname` is fixed to **START_UEBERSICHT_SCHALTZEITDEF**. 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_UEBERSICHT_SCHALTZEITDEF` | **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).