# Activation of an allocation authorization of the BKV at the NB — NB 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 NB \nSystem diagram: Aktivierung einer Zuordnungsermächtigung des BKV beim NB — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\n1. Aktivierung der\nZu-ordnungsermächtigung\n\nBKV\n\nAS4\n55071\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\nLoad data for the check\n\n\n3 read APIs called\n\nAPI\nlisted at the step\n\nTrigger follow-up process:\n55071\n\n"} gesamt={"\nSequence diagram: Aktivierung einer Zuordnungsermächtigung des BKV beim NB — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB\n\n\nBKV\n\n\n1. Aktivierung der Zu-ordnungsermächtigung\nAS4 · PI 55071\n\nCreate transaction\nCreate process data\n"} titel="NB" /> ## Process steps ### Activation of the allocation authorization
**Check identifiers** - [55071](/en/schnittstellen/202610/pruefi/UTILMD/PI_55071) — Activation of the allocation authorization · AS4
**Flow**
  1. Message from **BKV** · AS4
  2. **Write endpoint** - Transaction created — [Create process data](/en/api/202610/backend-schreiben-nb/createprocessdata#prozessdaten-erstellen) `POST /createProcessData` Try it out Creates a new transaction in the backend with the data of the incoming message.
  3. **Load data for the check** - `LESEN_BILANZKREIS_INTERN` - `LESEN_STAMMDATEN_LIEFERANTENRAHMENVERTRAG` - `LESEN_STAMMDATEN_ZUORDNUNGSERMAECHTIGUNG`
  4. **Trigger follow-up process** - [55071](/en/schnittstellen/202610/pruefi/UTILMD/PI_55071) — Activation of the allocation authorization After processing, the MACO APP starts this follow-up process itself.
## 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 **BKV** sends “Activation of the assignment authorization” (Step 1). From here on, the party involved on this page takes its turn.
  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 BKV](/en/prozessdoku/202610/BKV/MaBiS-aktivierung-einer-zuordnungsermaechtigung-des-bkv-beim-nb) — BKV *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.* These read accesses are not listed in the API catalogue of this format version; the step therefore shows only their command, without address and without button. Applies to: [1](#schritt-1) For the check identifiers of these steps there is no test case in the test data set; the »Try it out« button of the write interface therefore offers no body. Applies to: [1](#schritt-1)