# Activation of a MaBiS metering point for the delta time series carry-over from the ÜNB to BIKO and NB — ÜNB view The ÜNB activates a MaBiS-ZP of a DZÜ 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 DZÜ to the NB, provided the activation was correct. The NB can inform the ÜNB of an activation that it considers faulty. In the event of an error message from the NB, ÜNB and NB clarify where the error lies and – if necessary – arrange for the error to be corrected. ## Process flow from the perspective of the ÜNB \nSystem diagram: Aktivierung eines MaBiS-Zählpunkts für den Deltazeitreihenübertrag vom ÜNB an BIKO und NB — view of ÜNB\n\n\nCustomer backend system\n\nMACO APP · ÜNB\n\nMarket partner\n\n\n\n1. Aktivierung eines\nMaBiS-ZP für den DZÜ\n\nBIKO\n\nAS4\n55062\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Antwort\n\n\nBIKO\n\nAS4\n55064\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Aktivierung eines MaBiS-Zählpunkts für den Deltazeitreihenübertrag vom ÜNB an BIKO und NB — view of ÜNB\n\n\nBackend (customer)\n\n\nMACO APP · ÜNB\n\n\nBIKO\n\n\nNB\n\n\n1. Aktivierung eines MaBiS-ZP für den DZÜ\nAS4 · PI 55062\n\nUpdate transaction\nUpdate process data\n\n2. Antwort\nAS4 · PI 55064 · E_0027\nE_0027 — MaBiS-ZP Aktivierung prüfen\n\nUpdate transaction\nUpdate process data\n\n4. Weiterleitung des aktivierten MaBiS-ZP für de…\nAS4 · PI 55062\n"} titel="ÜNB" /> ## Process steps ### Activation of a MaBiS-ZP for the DZÜ
**Check identifiers** - [55062](/en/schnittstellen/202604/pruefi/UTILMD/PI_55062) — Activation of ZP · AS4
**Flow**
  1. Message to **BIKO** · AS4
  2. **Write endpoint** - Transaction updated — `AKTUALISIEREN_PROZESSDATEN` Updates the existing transaction in the backend once the message has been created.
### Response
**Check identifiers** - [55064](/en/schnittstellen/202604/pruefi/UTILMD/PI_55064) — Response · AS4
**Flow**
  1. Message from **BIKO** · AS4
    **Response per decision tree** - `55064` → [E_0027](/en/referenz/202604/ebd/E_0027) · BIKO · Check MaBiS-ZP activation
  2. **Write endpoint** - Transaction updated — `AKTUALISIEREN_PROZESSDATEN` Updates the existing transaction in the backend with the data of the incoming message.
### Forwarding of the activated MaBiS-ZP for the DZÜ This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [55062](/en/schnittstellen/202604/pruefi/UTILMD/PI_55062) — Activation of ZP · AS4
Decision trees of this process | EBD | Name | |---|---| | [E_0027](/referenz/202604/ebd/E_0027) | Check MaBiS-ZP activation |
## Process information Wording of the consolidated version, profile ch. 12.2.1, pp. 163–164.
  1. ### Preconditions The BG in the RZ without an active MaBiS-ZP exists for the DZÜ.
  2. ### Results - The BIKO and the NB can assign the DZÜ to a MaBiS-ZP.
  3. ### First message The party involved on this page sends this itself: “Activation of a MaBiS-ZP for the DZÜ” to **BIKO** (step 1).
  4. ### Objective - The ÜNB has activated the MaBiS-ZP for the corresponding DZÜ at the BIKO. - The BIKO has forwarded the MaBiS-ZP for the DZÜ to the NB, and the NB 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 NB](/en/prozessdoku/202604/NB/MaBiS-aktivierung-eines-mabis-zaehlpunkts-fuer-den-deltazeitreihenuebertrag-vom-uenb-an-biko-und-nb) — NB - [View BIKO](/en/prozessdoku/202604/BIKO/MaBiS-aktivierung-eines-mabis-zaehlpunkts-fuer-den-deltazeitreihenuebertrag-vom-uenb-an-biko-und-nb) — 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 numbers are those of the source; where one is missing, it is missing there.* The source does not yet name the event that triggers these steps. Applies to: [1](#schritt-1) The connector table lists no write call for these steps. Derived from the process flow: the own role was already involved in this process, so the transaction already exists. Applies to: [2](#schritt-2) 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), [2](#schritt-2)