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

Marktrolle **LF** · 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_17201](/schnittstellen/202610/pruefi/ORDERS/PI_17201) | ORDERS | Req. standardized profiles and profile sets | MaBiS | LF → NB |

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="Anforder. normierter Profile und Profilscharen">17201</span> | Condition |
|---|---|---|---|---|
| <span className="hbs-g hbs-e0">**stammdaten**</span> | — | object | May | — |
| <span className="hbs-g hbs-e1">**ANFRAGE** <span className="hbs-liste">[ ]</span> <span className="hbs-pflicht">\*</span></span> | — | object[] | Must | — |
| <span className="hbs-f hbs-e2">[abonnement](/en/bo4e/202610/bo/Anfrage#abonnement) <span className="hbs-pflicht">\*</span></span><span className="hbs-nr">00010</span> | Start or end of subscription | [Enum Abonnement](/en/bo4e/202610/enum/Abonnement) | Must | — |
| <span className="hbs-w hbs-e3">`START_ABO`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`ENDE_ABO`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`OHNE_ABO`</span> | — | — | Must | — |
| <span className="hbs-g hbs-e1">**AUFTRAG** <span className="hbs-liste">[ ]</span> <span className="hbs-pflicht">\*</span></span> | — | object[] | Must | — |
| <span className="hbs-g hbs-e2">**positionsdaten** <span className="hbs-liste">[ ]</span> <span className="hbs-pflicht">\*</span></span> | — | object[] | Must | — |
| <span className="hbs-f hbs-e3">[positionsnummer](/en/bo4e/202610/com/AuftragPosition#positionsnummer) <span className="hbs-pflicht">\*</span></span><span className="hbs-nr">00020</span> | Line item number | integer | Must | — |
| <span className="hbs-g hbs-e1">**BILANZIERUNG** <span className="hbs-liste">[ ]</span> <span className="hbs-pflicht">\*</span></span> | — | object[] | Must | — |
| <span className="hbs-g hbs-e2">**lastprofile** <span className="hbs-liste">[ ]</span> <span className="hbs-pflicht">\*</span></span> | — | object[] | Must | — |
| <span className="hbs-f hbs-e3">[einspeisung](/en/bo4e/202610/com/Lastprofil#einspeisung) <span className="hbs-pflicht">\*</span></span><span className="hbs-nr">00030</span> | Feed-in indicator | boolean | Must | — |
| <span className="hbs-f hbs-e3">[profilart](/en/bo4e/202610/com/Lastprofil#profilart) <span className="hbs-pflicht">\*</span></span><span className="hbs-nr">00040</span> | Profile category | [Enum Profilart](/en/bo4e/202610/enum/Profilart) | Must | — |
| <span className="hbs-w hbs-e4">`ART_STANDARDLASTPROFIL`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`ART_TAGESPARAMETERABHAENGIGES_LASTPROFIL`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e4">`ART_LASTPROFIL`</span> | — | — | Must | — |

</div>

</Handbuchsatz>

## Chain of this trigger

The event triggers the message.

| Message | Responses | Write call after the response |
|---|---|---|
| [17201](/schnittstellen/202610/pruefi/ORDERS/PI_17201) | — | — |

This event triggers steps in these role views:

| Process | Party involved | Rulebook | Division |
|---|---|---|---|
| [Termination of a subscription to standardized profiles and profile sets from the LF or ÜNB to NB](/en/prozessdoku/202610/LF/MaBiS-beendigung-eines-abonnements-von-normierten-profilen-und-profilscharen-vom-lf-bzw-uenb-an-nb) | LF | MaBiS | Electricity |
| [Start of a subscription to standardized profiles and profile sets from the LF or ÜNB to NB](/en/prozessdoku/202610/LF/MaBiS-start-eines-abonnements-von-normierten-profilen-und-profilscharen-vom-lf-bzw-uenb-an-nb) | LF | MaBiS | 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 |
| [typ](/en/bo4e/202610/cdoc/Transaktionsdaten#typ) | string | **yes** | Old FW - OBSOLET |
| [vorgangsreferenznummer](/en/bo4e/202610/cdoc/Transaktionsdaten#vorgangsreferenznummer) | string | **yes** | Reference number of the transaction of the registration according to WiM / ORDERS RFF+Z41 / IFTSTA RFF+ACW |
| `pruefidentifikator` | — | no | Wird dynamisch im Event-Prozess ermittelt. Ein vom Sender mitgegebener Wert wird ignoriert. Im Topic mögliche Prüfis — 17201. Mögliche Werte: `17201` |
| [absender › rollencodenummer](/en/bo4e/202610/bo/Marktteilnehmer#rollencodenummer) | string | no | Specifies the code value of the market role. |
| [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_ABO_PROFILE**. 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_ABO_PROFILE` | **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).