# Transmission of data status for the balancing group aggregated time series from BIKO to NB and BKV — BKV view The BIKO transmits the data status to the NB and BKV for the BK-SZR (category A) - after receipt of the BK-SZR (category A) from the NB or - after receipt of the validation notification from the BKV or - after use of the aggregated time series for the BKA (without KBKA) or the KBKA. The data status is sent regardless of whether it has changed or not. ## Process flow from the perspective of the BKV \nSystem diagram: Übermittlung Datenstatus für die Bilanzkreissummenzeitreihe vom BIKO an NB und BKV — view of BKV\n\n\nCustomer backend system\n\nMACO APP · BKV\n\nMarket partner\n\n\n\n1. Datenstatus\n\nBIKO\n\nAS4\n21004\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Übermittlung Datenstatus für die Bilanzkreissummenzeitreihe vom BIKO an NB und BKV — view of BKV\n\n\nBackend (customer)\n\n\nMACO APP · BKV\n\n\nBIKO\n\n\nNB\n\n\n1. Datenstatus\nAS4 · PI 21004 · E_0056, E_0057…\nE_0056 — Datenstatus nach erfolgter Bilanzkreisabrechnung vergeben\nE_0057 — Datenstatus nach Eingang einer Bilanzkreissummenzeitreihe (Kat…\nE_0058 — Datenstatus nach Vorliegen einer Prüfmitteilung vergeben\n\nCreate transaction\nCreate process data\n\n2. Datenstatus\nAS4 · PI 21003 · E_0056, E_0057…\nE_0056 — Datenstatus nach erfolgter Bilanzkreisabrechnung vergeben\nE_0057 — Datenstatus nach Eingang einer Bilanzkreissummenzeitreihe (Kat…\nE_0058 — Datenstatus nach Vorliegen einer Prüfmitteilung vergeben\n"} titel="BKV" /> ## Process steps ### Data status
**Check identifiers** - [21004](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21004) — Status message · AS4
**Flow**
  1. Message from **BIKO** · AS4
    **Response per decision tree** - `21004` → [E_0056](/en/referenz/202604/ebd/E_0056) · BIKO · Assign data status after completed balancing group settlement - `21004` → [E_0057](/en/referenz/202604/ebd/E_0057) · BIKO · Assign data status after receipt of a balancing group aggregated time series (category A) - `21004` → [E_0058](/en/referenz/202604/ebd/E_0058) · BIKO · Assign data status once a validation notification is available
  2. **Write endpoint** - Transaction created — `ERSTELLEN_PROZESSDATEN` Creates a new transaction in the backend with the data of the incoming message.
### Data status This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [21003](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21003) — Status message · AS4
**Response per decision tree** - `21003` → [E_0056](/en/referenz/202604/ebd/E_0056) · BIKO · Assign data status after completed balancing group settlement - `21003` → [E_0057](/en/referenz/202604/ebd/E_0057) · BIKO · Assign data status after receipt of a balancing group aggregated time series (category A) - `21003` → [E_0058](/en/referenz/202604/ebd/E_0058) · BIKO · Assign data status once a validation notification is available
Decision trees of this process | EBD | Name | |---|---| | [E_0056](/referenz/202604/ebd/E_0056) | Assign data status after completed balancing group settlement | | [E_0057](/referenz/202604/ebd/E_0057) | Assign data status after receipt of a balancing group aggregated time series (category A) | | [E_0058](/referenz/202604/ebd/E_0058) | Assign data status once a validation notification is available |
## Process information Wording of the consolidated version, profile ch. 10.11.1, pp. 137–138.
  1. ### Preconditions - The BIKO has a BK-SZR (category A) transmitted by the NB. - The BIKO has forwarded the BK-SZR (category A) transmitted by the NB to the BKV.
  2. ### Results All systems of BKV, BIKO and NB hold the same data status for a version of the aggregated time series.
  3. ### Error case #### Result in the error case The BIKO informs all affected market participants and, after the error has been corrected, ensures that the correct data status is assigned to all affected BK-SZR (category A). #### Error cases The algorithm applied by the BIKO for assigning the data status is faulty.
  4. ### First message **BIKO** sends “Data status” (step 1). From here on, it is the turn of the party involved on this page.
  5. ### Objective The data status managed by the BIKO is available at the NB and at the BKV for the BK-SZR (category A).
## 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 NB](/en/prozessdoku/202604/NB/MaBiS-uebermittlung-datenstatus-fuer-die-bilanzkreissummenzeitreihe-vom-biko-an-nb-und-bkv) — NB - [View BIKO](/en/prozessdoku/202604/BIKO/MaBiS-uebermittlung-datenstatus-fuer-die-bilanzkreissummenzeitreihe-vom-biko-an-nb-und-bkv) — BIKO *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: [1](#schritt-1) 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: [1](#schritt-1)