[LF] START_BESTELLUNG_ANGEBOT_KONFIGURATION
Marktrolle LF · Formatversion 202610 · BO4E-Schema 1.7.8
Check identifiers not yet covered
The following check identifiers are intended for this topic in business terms, but are not yet available as a specification in the current format version: 17131.
The information comes from the generator pipeline and is deliberately made visible here instead of being withheld.
Master data
This event defines no Prüfi selection. The master data follow from the triggering process.
Chain of this trigger
The event triggers the message.
| Message | Responses | Write call after the response |
|---|---|---|
| 17131 | — | — |
Transaction data
The interchange envelope of the message. Mandatory fields must be set on the trigger call.
| Field | Type | Mandatory | Description |
|---|---|---|---|
| angebotsnummer | string | yes | Quotation number / RFF+AAG |
| kategorie | string | yes | Qualifier from the beginning of the EDIFACT message / BGM |
| sparte | 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 — 17131. Possible values: 17131 |
| absender › rollencodenummer | string | no | Specifies the code value of the market role. |
| empfaenger › rollencodenummer | string | no | Specifies the code value of the market role. |
Additional data
eventname is fixed to START_BESTELLUNG_ANGEBOT_KONFIGURATION. 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_ANGEBOT_KONFIGURATION | 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.