# [LF] START_UEBERSICHT_ZAEHLZEITDEF
<span hidden data-pagefind-meta={"title:Trigger event START_UEBERSICHT_ZAEHLZEITDEF — 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_25004](/schnittstellen/202604/pruefi/UTILTS/PI_25004) | UTILTS | Transmission of overview of metering 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 Zählzeitdefinitionen">25004</span> | Condition |
|---|---|---|---|---|
| <span className="hbs-g hbs-e0">**stammdaten**</span> | — | object | May | — |
| <span className="hbs-g hbs-e1">**ZAEHLZEITDEFINITION** <span className="hbs-liste">[ ]</span> <span className="hbs-pflicht">\*</span></span> | — | object[] | Must | — |
| <span className="hbs-f hbs-e2">[beginndatum](/en/bo4e/202604/bo/Zaehlzeitdefinition#beginndatum) <span className="hbs-pflicht">\*</span></span><span className="hbs-nr">00010</span> | The inclusive point in time from which the metering time period definitions are rolled out | string (date-time) | Must | — |
| <span className="hbs-f hbs-e2">[notwendigkeit](/en/bo4e/202604/bo/Zaehlzeitdefinition#notwendigkeit) <span className="hbs-pflicht">\*</span></span><span className="hbs-nr">00020</span> | Describes whether metering time period definitions are necessary | [Enum DefinitionenNotwendigkeit](/en/bo4e/202604/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/202604/bo/Zaehlzeitdefinition#version) <span className="hbs-pflicht">\*</span></span><span className="hbs-nr">00030</span> | Version of the metering time period definition as a date | string (date-time) | Must | — |
| <span className="hbs-g hbs-e2">**zaehlzeiten** <span className="hbs-liste">[ ]</span></span> | — | object[] | May | — |
| <span className="hbs-f hbs-e3">[beschreibungTyp](/en/bo4e/202604/com/Zaehlzeit#beschreibungtyp)</span><span className="hbs-nr">00040</span> | Description of the metering time definition type | string | May | — |
| <span className="hbs-f hbs-e3">[code](/en/bo4e/202604/com/Zaehlzeit#code)</span><span className="hbs-nr">00050</span> | Metering time period definition | string | May | — |
| <span className="hbs-f hbs-e3">[ermittlungLeistungsmaximum](/en/bo4e/202604/com/Zaehlzeit#ermittlungleistungsmaximum)</span><span className="hbs-nr">00060</span> | Determination of maximum demand | [Enum ErmittlungLeistungsmaximum](/en/bo4e/202604/enum/ErmittlungLeistungsmaximum) | May | — |
| <span className="hbs-w hbs-e4">`VERWENDUNG_HOCHLASTFENSTER`</span> | — | — | May | — |
| <span className="hbs-w hbs-e4">`KEINE_VERWENDUNG_HOCHLASTFENSTER`</span> | — | — | May | — |
| <span className="hbs-f hbs-e3">[haeufigkeit](/en/bo4e/202604/com/Zaehlzeit#haeufigkeit)</span><span className="hbs-nr">00070</span> | Frequency of transmission | [Enum HaeufigkeitZaehlzeit](/en/bo4e/202604/enum/HaeufigkeitZaehlzeit) | 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">[istBestellbar](/en/bo4e/202604/com/Zaehlzeit#istbestellbar)</span><span className="hbs-nr">00080</span> | Can the metering time period be ordered? | boolean | May | — |
| <span className="hbs-f hbs-e3">[typ](/en/bo4e/202604/com/Zaehlzeit#typ)</span><span className="hbs-nr">00090</span> | ZählzeitdefinitionTyp | [Enum ZaehlzeitdefinitionTyp](/en/bo4e/202604/enum/ZaehlzeitdefinitionTyp) | May | — |
| <span className="hbs-w hbs-e4">`WAERMEPUMPE`</span> | — | — | May | — |
| <span className="hbs-w hbs-e4">`NACHTSPEICHERHEIZUNG`</span> | — | — | May | — |
| <span className="hbs-w hbs-e4">`SCHWACHLASTZEITFENSTER`</span> | — | — | May | — |
| <span className="hbs-w hbs-e4">`SONSTIGE`</span> | — | — | May | — |
| <span className="hbs-w hbs-e4">`HOCHLASTZEITFENSTER`</span> | — | — | May | — |
| <span className="hbs-f hbs-e3">[uebermittelbarkeit](/en/bo4e/202604/com/Zaehlzeit#uebermittelbarkeit)</span><span className="hbs-nr">00100</span> | Type of transmission | [Enum UebermittelbarkeitZaehlzeit](/en/bo4e/202604/enum/UebermittelbarkeitZaehlzeit) | May | — |
| <span className="hbs-w hbs-e4">`ELEKTRONISCH`</span> | — | — | May | — |
| <span className="hbs-w hbs-e4">`NICHT_ELEKTRONISCH`</span> | — | — | May | — |
| <span className="hbs-g hbs-e2">**zaehlzeitregister** <span className="hbs-liste">[ ]</span></span> | — | object[] | May | — |
| <span className="hbs-f hbs-e3">[register](/en/bo4e/202604/com/Zaehlzeitregister#register)</span><span className="hbs-nr">00110</span> | Metering time period register | string | May | — |
| <span className="hbs-f hbs-e3">[schwachlastfaehig](/en/bo4e/202604/com/Zaehlzeitregister#schwachlastfaehig)</span><span className="hbs-nr">00120</span> | Off-peak capability of the register | [Enum Schwachlastfaehig](/en/bo4e/202604/enum/Schwachlastfaehig) | May | — |
| <span className="hbs-w hbs-e4">`SCHWACHLASTFAEHIG`</span> | — | — | May | — |
| <span className="hbs-w hbs-e4">`NICHT_SCHWACHLASTFAEHIG`</span> | — | — | May | — |
| <span className="hbs-f hbs-e3">[zaehlzeitDefinition](/en/bo4e/202604/com/Zaehlzeitregister#zaehlzeitdefinition)</span><span className="hbs-nr">00130</span> | Metering time period definition | string | May | — |

</div>

</Handbuchsatz>

## Chain of this trigger

The event triggers the message.

| Message | Responses | Write call after the response |
|---|---|---|
| [25004](/schnittstellen/202604/pruefi/UTILTS/PI_25004) | — | — |

This event triggers a step in this role view:

| Process | Party involved | Rulebook | Division |
|---|---|---|---|
| [Transmission of the overview of the definitions of the LF by the LF](/en/prozessdoku/202604/LF/GPKE-Teil3-uebermittlung-der-uebersicht-der-definitionen-des-lf-durch-den-lf) | LF | 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 |
|---|---|---|---|
| [anfrageReferenz](/en/bo4e/202604/cdoc/Transaktionsdaten#anfragereferenz) | string | **yes** | Application number / RFF+AGI |
| [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 — 25004. Possible values: `25004` |
| [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_UEBERSICHT_ZAEHLZEITDEF**. 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_ZAEHLZEITDEF` | **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).