# [LF] START_BESTELLUNG_AEND_PROGNOSEGRUNDLAGE
<span hidden data-pagefind-meta={"title:Trigger event START_BESTELLUNG_AEND_PROGNOSEGRUNDLAGE — 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_17120](/schnittstellen/202604/pruefi/ORDERS/PI_17120) | ORDERS | Order placement change of forecast basis | GPKE part 3 | 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="Bestellung Änderung Prognosegrundlage">17120</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">[lokationsId](/en/bo4e/202604/bo/Anfrage#lokationsid) <span className="hbs-pflicht">\*</span></span><span className="hbs-nr">00010</span> | Which market or metering location this request applies to. | string | Must | — |
| <span className="hbs-g hbs-e1">**AUFTRAG** <span className="hbs-liste">[ ]</span> <span className="hbs-pflicht">\*</span></span> | — | object[] | Must | — |
| <span className="hbs-f hbs-e2">[ausfuehrungsdatum](/en/bo4e/202604/bo/Auftrag#ausfuehrungsdatum) <span className="hbs-pflicht">\*</span></span><span className="hbs-nr">00020</span> | The execution date describes at which point in time an order is to be executed. | string (date-time) | Must | — |
| <span className="hbs-g hbs-e1">**BILANZIERUNG** <span className="hbs-liste">[ ]</span> <span className="hbs-pflicht">\*</span></span> | — | object[] | Must | — |
| <span className="hbs-f hbs-e2">[prognosegrundlage](/en/bo4e/202604/bo/Bilanzierung#prognosegrundlage) <span className="hbs-pflicht">\*</span></span><span className="hbs-nr">00030</span> | Forecast basis | [Enum Prognosegrundlage](/en/bo4e/202604/enum/Prognosegrundlage) | Must | — |
| <span className="hbs-w hbs-e3">`WERTE`</span> | — | — | Must | — |
| <span className="hbs-w hbs-e3">`PROFILE`</span> | — | — | Must | — |

</div>

</Handbuchsatz>

## 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 |
|---|---|---|
| [17120](/schnittstellen/202604/pruefi/ORDERS/PI_17120) | [19121](/schnittstellen/202604/pruefi/ORDRSP/PI_19121) | `POST /updateProcessData` (derived) |

This event triggers a step in this role view:

| Process | Party involved | Rulebook | Division |
|---|---|---|---|
| [Order placement for a configuration from the LF to NB](/en/prozessdoku/202604/LF/GPKE-Teil3-bestellung-einer-konfiguration-vom-lf-an-nb) | 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 |
|---|---|---|---|
| `pruefidentifikator` | — | no | Determined dynamically in the event process. A value supplied by the sender is ignored. Prüfis possible in the topic — 17120. Possible values: `17120` |

## Additional data

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