# Process
<span hidden data-pagefind-meta={"title:Process — BO4E document object (FV 202610)"} />

BO4E document object · 7 fields · 0 uses in check identifiers and events

## Fields

<Feldansicht>

<div data-ansicht-teil="tabelle">

<div className="maco-tabellenrahmen maco-bo4e-felder" data-maco="bo4e-tabelle">

| Field | Type | Description |
|---|---|---|
| <a id="businesskey"></a>`businessKey` | string | BusinessKey · Id of the process that is currently performing the call. *(not from the time slice; source: api-definitionen/schema-eigen/backend-schreiben-lf.yaml)* There as `zusatzdaten.businessKey`, mandatory in „ZUSATZDATEN ( create SST)" and „ZUSATZDATEN ( update SST)"; identical in wording in `backend-schreiben-msb.yaml` and `backend-schreiben-nb.yaml`. In the success responses of the triggers (`site-d/apis/trigger-<fv>.json`, schema `event_responses_success`) a field of the same name carries the text „Unique identifier of the business process" (`format: uuid`, mandatory). Both are fields of the same name in API schemas, not a use of the cdoc object `Process`. |
| <a id="datasource"></a>`dataSource` | [DataSource](/en/bo4e/202610/cdoc/DataSource)<br/><Werte>`INBOUND`, `OUTBOUND`</Werte> | CDOC DataSource |
| <a id="version"></a>`version` | integer | Versioning of the JSON schema |
| <a id="edifactversion"></a>`edifactVersion` | integer | The EDIFACT format version in format YYYYMM, example 202504 |
| <a id="data"></a>`data` | [ProcessData](/en/bo4e/202610/cdoc/ProcessData) | — |
| <a id="tenantid"></a>`tenantId` | string | Identification of the tenant, NONE for a system without tenants |
| <a id="processdate"></a>`processDate` | string (date-time) | Process date |

</div>

</div>

<div data-ansicht-teil="baum" data-pagefind-ignore="all">

<Handbuchsatz art="struktur" start="zu">

<div className="maco-tabellenrahmen" data-maco="bo4e-baum">

| Structure (BO4E) | Description | Format |
|---|---|---|
| <span className="hbs-f hbs-e0">[businessKey](/en/bo4e/202610/cdoc/Process#businesskey)</span> | BusinessKey · Id of the process that is currently performing the call. *(not from the time slice; source: api-definitionen/schema-eigen/backend-schreiben-lf.yaml)* There as `zusatzdaten.businessKey`, mandatory in „ZUSATZDATEN ( create SST)" and „ZUSATZDATEN ( update SST)"; identical in wording in `backend-schreiben-msb.yaml` and `backend-schreiben-nb.yaml`. In the success responses of the triggers (`site-d/apis/trigger-<fv>.json`, schema `event_responses_success`) a field of the same name carries the text „Unique identifier of the business process" (`format: uuid`, mandatory). Both are fields of the same name in API schemas, not a use of the cdoc object `Process`. | string |
| <span className="hbs-f hbs-e0">[dataSource](/en/bo4e/202610/cdoc/Process#datasource)</span> | CDOC DataSource | [DataSource](/en/bo4e/202610/cdoc/DataSource)<br/><Werte>`INBOUND`, `OUTBOUND`</Werte> |
| <span className="hbs-f hbs-e0">[version](/en/bo4e/202610/cdoc/Process#version)</span> | Versioning of the JSON schema | integer |
| <span className="hbs-f hbs-e0">[edifactVersion](/en/bo4e/202610/cdoc/Process#edifactversion)</span> | The EDIFACT format version in format YYYYMM, example 202504 | integer |
| <span className="hbs-f hbs-e0">[data](/en/bo4e/202610/cdoc/Process#data)</span> | — | [ProcessData](/en/bo4e/202610/cdoc/ProcessData) |
| <span className="hbs-f hbs-e0">[tenantId](/en/bo4e/202610/cdoc/Process#tenantid)</span> | Identification of the tenant, NONE for a system without tenants | string |
| <span className="hbs-f hbs-e0">[processDate](/en/bo4e/202610/cdoc/Process#processdate)</span> | Process date | string (date-time) |

</div>

</Handbuchsatz>

</div>

</Feldansicht>

:::note{title="Interchange envelope of the process data"}

`Process` carries the `businessKey` of the process instance, the origin (`dataSource`), the versions (`version`, `edifactVersion`), the tenant (`tenantId`), the `processDate` and, in `data`, the actual process data.

The Prüfi and event specifications of this format version start at the *content* (`stammdaten`, `transaktionsdaten`, `zusatzdaten`) and do not reference any field of the envelope via `$ref`. The 0 uses in the summary line above therefore measure the `$ref` graph of these schemas and say nothing about whether the envelope is sent.

**Measured on 05.09.2026:** `updateProcessData` and `createProcessData` send `{stammdaten, transaktionsdaten, zusatzdaten}` — **without** this interchange envelope. The `businessKey` is located *in* `zusatzdaten`, not on the body. Established from the construction rule of the sender in the connector flow; the counter-check is the same flow, which does build an interchange envelope for the message to the process engine. **Not measured:** a captured real call, and the MaloIdent branch (03002/03003), which runs independently.

The interface specification shows the same body. The one outlier with a field `data` at the root is exactly **1 of 112** members of the `updateProcessData` schema of role LF and not a second body form.

The keys `businessKey`, `prozessId` and `targetBusinessKey` are described in context under [Keys](/en/schnittstellen/schluessel).

:::

<Hinweisbereich>

A **\*** after a field name marks a **mandatory field**; the BO4E schema lists it under `required`.

The descriptions marked *not from the time slice* are not in `_sources/v202610/bo4e` but in the source named in each case; they have been adopted editorially and are not derived from the schemas of this page. The page [Keys](/en/schnittstellen/schluessel) describes the keys in context.

</Hinweisbereich>