# Activation of a MaBiS metering point for the balancing group aggregated time series from the ÜNB to BIKO and BKV — BKV view The ÜNB activates the MaBiS-ZP of a BK-SZR (category B) and sends the corresponding information to the BIKO, which is accepted or rejected by the BIKO. On receipt, the BIKO forwards the activation of a MaBiS-ZP for a BK-SZR (category B) to the BKV if the activation was correct. The BKV can inform the ÜNB of an activation that it considers faulty. In the event of an error message from the BKV, ÜNB and BKV clarify where the error lies and – if necessary – arrange for the error to be corrected. ## Process flow from the perspective of the BKV \nSystem diagram: Aktivierung eines MaBiS-Zählpunkts für die 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\n4. Weiterleitung des\naktivierten MaBiS-ZP für\nBK-SZR (Kategori…\n\nBIKO\n\nAS4\n55062\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Aktivierung eines MaBiS-Zählpunkts für die Bilanzkreissummenzeitreihe vom ÜNB an BIKO und BKV — view of BKV\n\n\nBackend (customer)\n\n\nMACO APP · BKV\n\n\nÜNB\n\n\nBIKO\n\n\n1. Aktivierung eines MaBiS-ZP für die BK-SZR (Ka…\nAS4 · PI 55062\n\n2. Antwort\nAS4 · PI 55064 · E_0011\nE_0011 — MaBiS-ZP Aktivierung prüfen\n\n4. Weiterleitung des aktivierten MaBiS-ZP für BK…\nAS4 · PI 55062\n\nCreate transaction\nCreate process data\n"} titel="BKV" /> ## Process steps ### Activation of a MaBiS-ZP for the BK-SZR (category B) This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [55062](/en/schnittstellen/202610/pruefi/UTILMD/PI_55062) — Activation of ZP · AS4
### Response This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [55064](/en/schnittstellen/202610/pruefi/UTILMD/PI_55064) — Response · AS4
**Response per decision tree** - `55064` → [E_0011](/en/referenz/202610/ebd/E_0011) · BIKO · Check MaBiS-ZP activation
### Forwarding of the activated MaBiS-ZP for BK-SZR (category B)
**Check identifiers** - [55062](/en/schnittstellen/202610/pruefi/UTILMD/PI_55062) — Activation of ZP · AS4
**Flow**
  1. Message from **BIKO** · AS4
  2. **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_0011](/referenz/202610/ebd/E_0011) | Check MaBiS-ZP activation |
## Process information Wording of the consolidated version, profile ch. 11.2.1, pp. 140–141.
  1. ### Preconditions - The ÜNB has been informed by the NB responsible for the BG about the assignment of the first market location with ÜNB aggregation responsibility, for whose assigned combination of BK, ZRT and RZ/BG no MaBiS-ZP for the BK-SZR (category B) is activated yet, or - The request for the aggregation level of the BK-SZR (category B) at the level of the RZ is available from the BKV.
  2. ### Results - The BIKO and the BKV can assign the BK-SZR (category B) to a MaBiS-ZP.
  3. ### First message **BIKO** sends “Forwarding of the activated MaBiS-ZP for BK-SZR (category B)” (step 4). From here on, it is the turn of the party involved on this page.
  4. ### Objective - The ÜNB has activated the MaBiS-ZP for the corresponding BK-SZR (category B) at the BIKO. - The BIKO has forwarded the MaBiS-ZP for the BK-SZR (category B) to the BKV, and the BKV has accepted it and, in the error case, initiated clearing with the ÜNB where applicable.
## 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-aktivierung-eines-mabis-zaehlpunkts-fuer-die-bilanzkreissummenzeitreihe-vom-uenb-an-biko-und-bkv) — BIKO - [View ÜNB](/en/prozessdoku/202610/UENB/MaBiS-aktivierung-eines-mabis-zaehlpunkts-fuer-die-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 numbers are those of the source; where one is missing, it is missing there.* 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: [4](#schritt-4) 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: [4](#schritt-4)