# Termination of a configuration from the MSB — NB view The MSB of the directly affected location informs the NB or LF about the termination of the configuration for the directly affected location. If further locations of the directly affected location are affected by the termination of the configuration, the MSB also states these further affected locations in the information. If further locations of the directly affected location are affected by the termination of the configuration for which the MSB of the directly affected location does not perform metering point operation, it involves the respective further MSB of the further affected locations. ## Process flow from the perspective of the NB \nSystem diagram: Beendigung einer Konfiguration vom MSB — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\n1. Information über die\nBeendigung einer\nKonfiguration\n\nMSB\n\nAS4\n21044\n\nAPERAK check: Z33\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Beendigung einer Konfiguration vom MSB — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB\n\n\nMSB\n\n\nLF\n\n\nweiterer MSB\n\n\n1. Information über die Beendigung einer Konfigu…\nAS4 · PI 21044\n\nCreate transaction\nCreate process data\n\n2. Information über die Beendigung einer Konfigu…\nAS4 · PI 21044\n\n3. Beendigung einer Konfiguration für weiter bet…\nAS4 · PI 17129\n\n4. Antwort\nAS4 · PI 19131 · E_0539\nE_0539 — Beendigung prüfen\n"} titel="NB" /> ## Process steps ### Information about the termination of a configuration
**Check identifiers** - [21044](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21044) — Order termination · AS4
**Flow**
  1. Message from **MSB** · AS4
  2. **APERAK checks** - `21044` → `Z33`
  3. **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.
### Information about the termination of a configuration This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [21044](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21044) — Order termination · AS4
### Termination of a configuration for further affected locations This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [17129](/en/schnittstellen/202610/pruefi/ORDERS/PI_17129) — Order placement termination of a configuration · AS4
### Response This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [19131](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19131) — Notification of configuration termination · AS4
**Response per decision tree** - `19131` → [E_0539](/en/referenz/202610/ebd/E_0539) · MSB · Check termination
Decision trees of the other parties involved | EBD | Name | |---|---| | [E_0539](/referenz/202610/ebd/E_0539) | Check termination |
## Process information Wording of the consolidated version, profile ch. 1.3.6.1, pp. 75–77.
  1. ### Preconditions - The configuration to be terminated is a configuration that - was successfully ordered via the use case “Order placement of a configuration from the NB or LF to the MSB” and - is to be terminated via this use case (e.g. a tax permit or a configuration that contains a metering time period definition of the LF). - The order placement of the termination of a configuration contains only the locations that were contained in the order placement of the NB or LF to the MSB for this configuration now to be terminated. - From the point of view of the MSB of the directly affected location, the termination of the configuration is generally possible for the affected locations.
  2. ### Results - The MSB of the respective affected location carries out the use case „Master data change“ (here: SD „[Master data change initiated by the MSB (responsible)](/en/prozessdoku/202610/NB/GPKE-Teil4-stammdatenaenderung-vom-msb-verantwortlich-ausgehend)“) (GPKE part 4), provided that a master data change is required for the respective location due to the termination of the configuration. - In the case of a chargeable configuration: The final invoice can be issued via the use case “Billing of services of price sheet A of MSB" by MSB to NB or LF.
  3. ### Error case #### Error cases - The configuration to be terminated is a configuration that - was not successfully ordered via the use case „Order placement of a configuration from the NB or LF to MSB“ or - is not to be ended via this use case. - The order placement of the termination of a configuration does not contain exactly the locations contained in the order placement of the NB or LF to the MSB. From the point of view of the MSB of the directly affected location, the termination of the configuration is not possible for the affected locations. - The market partner is not assigned to the affected location at the ordered end of the effective period. - The termination of the configuration has already been successfully ordered by the NB or LF or a further MSB via the use case „Order placement of the termination of a configuration to MSB“ for the end of the effective period envisaged by the MSB or for an earlier end. - Not all parameters or incorrect parameters are available for the termination of the configuration.
  4. ### Further requirements - The termination of the configuration of an affected location must be carried out without delay; the termination of the configuration must, however, be set up before the end of the effective period. Note: the end of the effective period is the same for all affected locations. - Note: In the case in which a further MSB wishes to end a configuration, it orders the termination of the configuration from MSB of the directly affected location via the use case “Order placement of the termination of a configuration to MSB”. - On termination of a transmission of values: if values are received by the MSB of the directly affected location or by NB or LF after the end of the effective period, these values are not to be processed.
  5. ### Trigger - The MSB of the directly affected location needs a configuration to be ended that is to be ended in the course of this use case. These triggers can be, for example: - The existing device technology will no longer permit the configuration in future. - Within the use case „[Start of metering point operation](/en/prozessdoku/202610/NB/WiM-Teil1-beginn-messstellenbetrieb)“ or the use case „[Obligation gMSB](/en/prozessdoku/202610/NB/WiM-Teil1-verpflichtung-gmsb)“ (WiM part 1), the MSB receives from the NB the information about the reassignment of the metering location to another MSB at a specific point in time, or - the contract for performing the metering point operation between the MSB and AN or ANN has been terminated. - In the case of the termination of a configuration that was ordered by LF: The LF assigned to the directly affected location changes. - In the case of the termination of a configuration that was ordered by NB: The NB assigned to the directly affected location changes. **Runs beforehand:** [Start of metering point operation](/en/prozessdoku/202610/NB/WiM-Teil1-beginn-messstellenbetrieb), [Obligation gMSB](/en/prozessdoku/202610/NB/WiM-Teil1-verpflichtung-gmsb) — these processes name the one shown here in their result.
  6. ### First message **MSB** sends “Information on the end of a configuration” (step 1). From here on, it is the turn of the party involved on this page.
  7. ### Objective The configuration (e.g. metering product, tax permit) of the affected locations (e.g. metering location, market location, controllable resource, grid location) has ended.
## 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 LF](/en/prozessdoku/202610/LF/GPKE-Teil3-beendigung-einer-konfiguration-vom-msb) — LF - [View MSB](/en/prozessdoku/202610/MSB/GPKE-Teil3-beendigung-einer-konfiguration-vom-msb) — MSB - [View WMSB](/en/prozessdoku/202610/MSB--WMSB/GPKE-Teil3-beendigung-einer-konfiguration-vom-msb) — further metering point operator · market role MSB *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 connector table lists no write call for these steps. Derived from the process flow: the process begins for the own role with their message, so the transaction is created. 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)