# Activation of a MaBiS metering point for the settlement aggregated time series from the BIKO to ÜNB — BIKO view The BIKO activates a MaBiS-ZP for the ÜNB-DZR in the BK named by the ÜNB and sends the corresponding information to the ÜNB. ## Process flow from the perspective of the BIKO \nSystem diagram: Aktivierung eines MaBiS-Zählpunkts für die Abrechnungssummenzeitreihe vom BIKO an ÜNB — view of BIKO\n\n\nCustomer backend system\n\nMACO APP · BIKO\n\nMarket partner\n\n\n\n1. Aktivierung eines\nMaBiS-ZP für die ÜNB-DZR\n\nÜNB\n\nAS4\n55062\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Aktivierung eines MaBiS-Zählpunkts für die Abrechnungssummenzeitreihe vom BIKO an ÜNB — view of BIKO\n\n\nBackend (customer)\n\n\nMACO APP · BIKO\n\n\nÜNB\n\n\n1. Aktivierung eines MaBiS-ZP für die ÜNB-DZR\nAS4 · PI 55062\n\nUpdate transaction\nUpdate process data\n"} titel="BIKO" /> ## Process steps ### Activation of a MaBiS-ZP for the ÜNB-DZR
**Check identifiers** - [55062](/en/schnittstellen/202604/pruefi/UTILMD/PI_55062) — Activation of ZP · AS4
**Flow**
  1. Message to **ÜNB** · AS4
  2. **Write endpoint** - Transaction updated — `AKTUALISIEREN_PROZESSDATEN` Updates the existing transaction in the backend once the message has been created.
## Process information Wording of the consolidated version, profile ch. 13.4.1, p. 185.
  1. ### Preconditions - The BK for accommodating the ÜNB-DZR is known. - The BK is active in the RZ for the affected time period.
  2. ### First message The party involved on this page sends this itself: “Activation of a MaBiS-ZP for the ÜNB-DZR” to **ÜNB** (step 1).
  3. ### Objective The BIKO has activated the MaBiS-ZP for the settlement aggregated time series at the ÜNB.
## 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/UENB/MaBiS-aktivierung-eines-mabis-zaehlpunkts-fuer-die-abrechnungssummenzeitreihe-vom-biko-an-uenb) — Ü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 source does not yet name the event that triggers these steps. 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)