# Activation of an allocation authorization of the BKV at the NB — BKV view By activating the allocation authorization, the BKV grants the NB permission to have market locations of a ZRT that lie within the BG assigned to its BK by a LF from the point in time named in the allocation authorization. The authorization is given per ZRT, BG, BK and LF from a specific point in time. Even where BKV and LF are the same legal entity, the allocation authorization must be given to the NB. In the error case, the NB clarifies it manually with the BKV. The allocation authorization is a basis for checking the assignment processes under GPKE. A granted allocation authorization alone does not yet trigger the activation of a metering point for balancing group or supplier sums, nor any transmission of master data relevant to balancing. ## Process flow from the perspective of the BKV \nSystem diagram: Aktivierung einer Zuordnungsermächtigung des BKV beim NB — view of BKV\n\n\nCustomer backend system\n\nMACO APP · BKV\n\nMarket partner\n\n\n\n1. Aktivierung der\nZu-ordnungsermächtigung\n\nNB\n\nAS4\n55071\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Aktivierung einer Zuordnungsermächtigung des BKV beim NB — view of BKV\n\n\nBackend (customer)\n\n\nMACO APP · BKV\n\n\nNB\n\n\n1. Aktivierung der Zu-ordnungsermächtigung\nAS4 · PI 55071\n\nUpdate transaction\nUpdate process data\n"} titel="BKV" /> ## Process steps ### Activation of the allocation authorization
**Check identifiers** - [55071](/en/schnittstellen/202604/pruefi/UTILMD/PI_55071) — Activation of the allocation authorization · 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. 10.2.1, pp. 119–120.
  1. ### Preconditions The BK named in the allocation authorization - is a BK of the BKV that sends the allocation authorization and - is valid from the point in time stated in the allocation authorization.
  2. ### Results The NB has the allocation authorization, and it serves as the basis for checking the GPKE.
  3. ### First message The party involved on this page sends this itself: “Activation of the allocation authorization” to **NB** (step 1).
  4. ### Objective The NB has received the activation of the allocation authorization and can apply it correctly.
## 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-einer-zuordnungsermaechtigung-des-bkv-beim-nb) — NB *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)