System diagram: Übermittlung der Bilanzkreissummenzeitreihe vom ÜNB an BIKO und BKV

# Transmission of the balancing group aggregated time series from ÜNB to BIKO and BKV — BKV view The ÜNB delivers the BK-SZR (category B) for the time period under consideration to the BIKO. The BIKO forwards the currently valid aggregation level of the BK-SZR (category B) to the BKV, provided it is not to be rejected. ## Process flow from the perspective of the BKV \nSystem diagram: Übermittlung der Bilanzkreissummenzeitreihe vom ÜNB an BIKO und BKV — view of BKV\n\n\nCustomer backend system\n\nMACO APP · BKV\n\nMarket partner\n\n\n\n3. Weiterleitung BK-SZR\n(Kategorie B)\n\nBIKO\n\nAS4\n13003\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n"} gesamt={""} titel="BKV" /> ## Process steps ### Transmission of BK-SZR (category B) This step runs between other market partners and is not relevant for this view.

**Check identifiers** - [13003](/en/schnittstellen/202610/pruefi/MSCONS/PI_13003) — Aggregated time series · AS4

### Response This step runs between other market partners and is not relevant for this view.

**Check identifiers** - [21002](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21002) — Refusal · AS4

**Response per decision tree** - `21002` → [E_0023](/en/referenz/202610/ebd/E_0023) · BIKO · Check balancing group aggregated time series (category B)

### Forwarding of BK-SZR (category B)

**Check identifiers** - [13003](/en/schnittstellen/202610/pruefi/MSCONS/PI_13003) — Aggregated time series · AS4

**Flow**

Message from **BIKO** · AS4
**Write endpoint** - Transaction created — `ERSTELLEN_PROZESSDATEN` Creates a new transaction in the backend with the data of the incoming message.

Decision trees of the other parties involved

| EBD | Name | |---|---| | [E_0023](/referenz/202610/ebd/E_0023) | Check balancing group aggregated time series (category B) |

## Process information Wording of the consolidated version, profile ch. 11.9.1, pp. 156–157.

### Preconditions The ÜNB has activated the MaBiS-ZP for the BK-SZR (category B) at the BIKO for the time period under consideration.
### Results The BIKO can determine the data status. (The data status depends on the receipt date of the data at the BIKO).
### Further requirements Aggregated time series that are received from the BIKO after the clearing deadline of the BKA (excluding KBKA) has expired and whose version differs from the highest version with „billing data“ enter the clearing phase for KBKA and are given the data status „check data“.
### First message **BIKO** sends “Forwarding of BK-SZR (category B)” (step 3). From here on, it is the turn of the party involved on this page.
### Objective - The BK-SZR (category B) formed by ÜNB is available to BIKO. - The BKV has received the BK-SZR (category B) from the BIKO and can check it against its data.

## Other views of the process The same process through the eyes of the other parties involved: the same steps, each read from their point of view. - [View BIKO](/en/prozessdoku/202610/BIKO/MaBiS-uebermittlung-der-bilanzkreissummenzeitreihe-vom-uenb-an-biko-und-bkv) — BIKO - [View ÜNB](/en/prozessdoku/202610/UENB/MaBiS-uebermittlung-der-bilanzkreissummenzeitreihe-vom-uenb-an-biko-und-bkv) — ÜNB · market role UENB *The steps are the **possible** messages of this process, not a sequence — the source lists neither conditions nor alternatives. The small box on the step names the own view on the left: with **←** it receives, with **→** it sends. Collapsed steps run between other market partners.* The connector table lists no write call for these steps. Derived from the process flow: the process begins for the own role with their message, so the transaction is created. Applies to: [3](#schritt-3) For this market role there is no write catalog; the step therefore shows only the command of the write call, without address and without button. Applies to: [3](#schritt-3)