# Complaint about a configuration from NB to MSB — View NB - The NB or LF files a complaint with the MSB of the directly affected location about a configuration that does not take effect or only takes partial effect. The latter checks the incoming complaint and informs the NB or LF of the processing status, or - the MSB of the directly affected location submits a complaint to the further MSB about a configuration that does not take effect or takes effect only partially. The latter checks the incoming complaint and informs the MSB of the directly affected location of the processing status. ## Process flow from the perspective of the NB \nSystem diagram: Reklamation einer Konfiguration vom NB an MSB — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\nLoad data for processing\n\n4 read APIs called\n\nAPI\nlisted at the step\n\n1. Reklamation einer\nKonfiguration\n\n\nMSB\n\nAS4\n17128\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Bearbeitungsstand zur\nReklamation\n\n\nMSB\n\nAS4\n19130\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Reklamation einer Konfiguration vom NB an MSB — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB\n\n\nMSB\n\n\n1. Reklamation einer Konfiguration\nAS4 · PI 17128\n\nUpdate transaction\nUpdate process data\n\n2. Bearbeitungsstand zur Reklamation\nAS4 · PI 19130 · E_0552\nE_0552 — Reklamation prüfen\n\nUpdate transaction\nUpdate process data\n"} titel="NB" /> ## Process steps ### Complaint about a configuration
**Check identifiers** - [17128](/en/schnittstellen/202610/pruefi/ORDERS/PI_17128) — Complaint about a configuration · AS4
**Flow**
  1. **Load data for processing** - `LESEN_ANFRAGE_BASIS` - `LESEN_AUFTRAG_BASIS` - `LESEN_REKLAMATION_BASIS` - `LESEN_SCHALTZEITDEFINITION_BASIS`
  2. Message to **MSB** · AS4
  3. **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 once the message has been created.
### Processing status for the complaint
**Check identifiers** - [19130](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19130) — Processing status of complaint configuration · AS4
**Flow**
  1. Message from **MSB** · AS4
    **Response per decision tree** - `19130` → [E_0552](/en/referenz/202610/ebd/E_0552) · MSB · Check complaint
  2. **APERAK checks** - `19130` → `Z33`
  3. **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.
Decision trees of this process | EBD | Name | |---|---| | [E_0552](/referenz/202610/ebd/E_0552) | Check complaint |
## Process information Wording of the consolidated version, profile ch. 1.3.4.1, p. 63.
  1. ### Preconditions - The configuration was ordered via the use case „Order placement of a configuration from the NB or LF to MSB“ and the order placement was confirmed. - The start of the effective period has already been reached and, where applicable, the end of the effective period has not yet been reached. - In the case of a complaint about values: this concerns the transmission of values of type 2.
  2. ### Results The configuration takes effect correctly.
  3. ### Error case #### Error cases For a complaint about values: This is the transmission of values according to type 1.
  4. ### Further requirements Note: The transmission of values according to type 1 is to be complained about via the use case „Complaint about values at the MSB“ (WiM part 2).
  5. ### Trigger - The configuration does not take effect or only takes partial effect (e.g. an ordered tax permit was not set up, or an ordered configuration containing a power curve definition was not set up, or ordered values of type 2 are not transmitted according to the ordered specifications).
  6. ### First message The party involved on this page is itself the sender of: „Complaint about a configuration“ to **MSB** (step 1).
  7. ### Objective The processing status of the configuration disputed by the NB or LF is available to the NB or LF from the MSB of the directly affected location, or the processing status of the configuration disputed by the MSB of the directly affected location is available to the MSB of the directly affected location from the further MSB.
## 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 MSB](/en/prozessdoku/202610/MSB/GPKE-Teil3-reklamation-einer-konfiguration-vom-nb-an-msb) — 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 source does not yet name the event that triggers these steps. Applies to: [1](#schritt-1) 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) 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 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: [2](#schritt-2)