Complaint about a configuration from NB to MSB — View MSB
- 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 MSB
Process steps
Complaint about a configuration
MSB NBZ33Check identifiers
- 17128 — Complaint about a configuration · AS4
Flow
Message from NB · AS4
APERAK checks
17128→Z33
Write endpoint
- Transaction created — Create process data
POST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created — Create process data
Processing status for the complaint
MSB NBCheck identifiers
- 19130 — Processing status of complaint configuration · AS4
Flow
Message to NB · AS4
Response per decision tree
19130→ E_0552 · MSB · Check complaint
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend once the message has been created.
- Transaction updated — Update process data
Decision trees of this process
| EBD | Name |
|---|---|
| E_0552 | Check complaint |
Process information
Wording of the consolidated version, profile ch. 1.3.4.1, p. 63.
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.
Results
The configuration takes effect correctly.
Error case
Error cases
For a complaint about values: This is the transmission of values according to type 1.
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).
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).
First message
NB sends “Complaint about a configuration” (step 1). From here on, it is the turn of the party involved on this page.
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 NB — NB
Notes on this page
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
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