# Deactivation of an allocation authorization of the BKV at the NB — NB view By transmitting the deactivation of the allocation authorization, the BKV withdraws from the NB the approval to assign market locations of the named ZRT that are located in the BG to its BK by means of a LF. The authorization is withdrawn per ZRT, BG, BK and LF from a specific point in time. A deactivation is possible only for the future, not retroactively. In the error case, the NB clarifies this manually with the BKV ## Process flow from the perspective of the NB \nSystem diagram: Deaktivierung 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. Deaktivierung der\nZuordnungsermächtigung\n\nBKV\n\nAS4\n55072\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nLoad data for the check\n\n\nLESEN_STAMMDATEN_ZUOR\nDNUNGSERMAEC…\n\nAPI\n\nTrigger follow-up process:\n55072\n\n"} gesamt={"\nSequence diagram: Deaktivierung 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. Deaktivierung der Zuordnungsermächtigung\nAS4 · PI 55072\n\nUpdate transaction\nUpdate process data\n"} titel="NB" /> ## Process steps ### Deactivation of the allocation authorization
**Check identifiers** - [55072](/en/schnittstellen/202610/pruefi/UTILMD/PI_55072) — Deactivation of the allocation authorization · AS4
**Flow**
  1. Message from **BKV** · AS4
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend with the data of the incoming message.
  3. **Load data for the check** - `LESEN_STAMMDATEN_ZUORDNUNGSERMAECHTIGUNG`
  4. **Trigger follow-up process** - [55072](/en/schnittstellen/202610/pruefi/UTILMD/PI_55072) — Deactivation 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.3.1, p. 122.
  1. ### Preconditions The allocation authorization to be deactivated is still active.
  2. ### Results - No further assignments with validity after the deactivation date can be carried out. - For all market locations of this ZRT, in the BG that are assigned to the BK, NB must ensure as of the deactivation date that no market location is assigned to the BK for this LF.
  3. ### First message **BKV** sends “Deactivation of the allocation authorization” (step 1). From here on, it is the turn of the party involved on this page.
  4. ### Objective The NB has received the deactivation 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-deaktivierung-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)