# Complaint about a definition of NB from MSB to NB — view NB The LF or MSB determines that a - Metering time period definition of NB or - Switching time definition of NB or - Power curve definition of NB is not available or appears implausible to it. It submits a complaint about this to NB. The latter checks the incoming complaint and, if the complaint is unfounded, states that the definition is valid. ## Process flow from the perspective of the NB \nSystem diagram: Reklamation einer Definition des NB vom MSB an NB — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\n1. Reklamation einer\nDefinition des NB\n\nMSB\n\nAS4\n17122\n\nAPERAK check: Z33\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\nLoad data for processing\n\n\n6 read APIs called\n\nAPI\nlisted at the step\n\nLoad data for processing\n\n\n6 read APIs called\n\nAPI\nlisted at the step\n\n2. Ablehnung der\nReklamation\n\n\nMSB\n\nAS4\n19123\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Reklamation einer Definition des NB vom MSB an NB — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB\n\n\nMSB\n\n\n1. Reklamation einer Definition des NB\nAS4 · PI 17122\n\nCreate transaction\nCreate process data\n\n2. Ablehnung der Reklamation\nAS4 · PI 19123 · E_0549\nE_0549 — Reklamation prüfen\n\nUpdate transaction\nUpdate process data\n"} titel="NB" /> ## Process steps ### Complaint about a definition of the NB
**Check identifiers** - [17122](/en/schnittstellen/202610/pruefi/ORDERS/PI_17122) — Complaint about a definition · AS4
**Flow**
  1. Message from **MSB** · AS4
  2. **APERAK checks** - `17122` → `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.
  4. **Load data for processing** - `LESEN_ANFRAGE_BASIS` - `LESEN_AUFTRAG_BASIS` - `LESEN_LEISTUNGSKURVENDEFINITION_BASIS` - `LESEN_REKLAMATION_BASIS` - `LESEN_SCHALTZEITDEFINITION_BASIS` - `LESEN_ZAEHLZEITDEFINITION_BASIS`
### Rejection of the complaint
**Check identifiers** - [19123](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19123) — Rejection of complaint about a definition · AS4
**Flow**
  1. **Load data for processing** - `LESEN_ANFRAGE_BASIS` - `LESEN_AUFTRAG_BASIS` - `LESEN_LEISTUNGSKURVENDEFINITION_BASIS` - `LESEN_REKLAMATION_BASIS` - `LESEN_SCHALTZEITDEFINITION_BASIS` - `LESEN_ZAEHLZEITDEFINITION_BASIS`
  2. Message to **MSB** · AS4
    **Response per decision tree** - `19123` → [E_0549](/en/referenz/202610/ebd/E_0549) · NB · Check complaint
  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.
Decision trees of this process | EBD | Name | |---|---| | [E_0549](/referenz/202610/ebd/E_0549) | Check complaint |
## Process information Wording of the consolidated version, profile ch. 1.2.7.1, p. 28.
  1. ### Preconditions - The LF or MSB is missing a definition or - a definition appears implausible to the LF or MSB.
  2. ### Results - If a definition subject to complaint has to be corrected, the use case “[Transmission of a definition of NB by NB](/en/prozessdoku/202610/NB/GPKE-Teil3-uebermittlung-einer-definition-des-nb-durch-den-nb)” must be carried out for the definition subject to complaint to all LF and MSB to which the definition to be corrected was transmitted. - If a definition subject to complaint was not transmitted, the use case “[Transmission of a definition of NB by NB](/en/prozessdoku/202610/NB/GPKE-Teil3-uebermittlung-einer-definition-des-nb-durch-den-nb)” must be carried out for the definition subject to complaint to all LF and MSB to which the definition was not transmitted.
  3. ### Further requirements In the case of the metering time period definition of the NB: A metering time period definition of the NB can also be complained about by the final customer in his role as LF to the NB if, within the scope of grid usage settlement, the final customer assumes the role of the LF, insofar as these rules apply to him accordingly.
  4. ### First message **MSB** sends “Complaint about a definition of the NB” (step 1). From here on, it is the turn of the party involved on this page.
  5. ### Objective The LF or MSB has an implausible or missing - Metering time period definition of NB or - Switching time definition of NB or - Power curve definition of NB has been the subject of a complaint.
## 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-definition-des-nb-vom-msb-an-nb) — 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.* 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), [2](#schritt-2) 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)