Complaint about a definition of LF from NB to LF — view LF
- The MSB finds that a metering time period definition of the LF is not available to it or appears implausible to it, or
- the NB or MSB determines that a switching time definition of the LF is not available to it or appears implausible to it or
- the NB or MSB determines that a power curve definition of the LF is not available to it or appears implausible to it. It submits a complaint about this to the LF. The latter checks the incoming complaint and, if the complaint is unfounded, notifies that the definition is valid.
Process flow from the perspective of the LF
Process steps
Complaint about a definition of the LF
LF NBZ33E_0547 Check complaintE_0546 Check complaintE_0550 Check complaintE_0551 Check complaint191232500Check identifiers
- 17122 — Complaint about a definition · AS4
Flow
Message from NB · AS4
APERAK checks
17122→Z33— APERAK check: Is referenced message known ?
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
Load data for the check
LESEN_DEFINITION_LEISTUNGSKURVEN- Read switching time definition
GET /getDefinitionSwitch - Read metering time period definition
GET /getDefinitionCounting
Decision tree
Trigger follow-up process
- 19123 — Rejection of complaint about a definition
2500
After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
Rejection of the complaint
LF NB17122Check identifiers
- 19123 — Rejection of complaint about a definition · AS4
Flow
Triggered by incoming message
- 17122 — Complaint about a definition
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to NB · AS4
Response per decision tree
19123→ E_0550 · LF · 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_0550 | Check complaint |
Process information
Wording of the consolidated version, profile ch. 1.2.8.1, p. 31.
Preconditions
- The MSB is missing a metering time period definition of the LF or
- a metering time period definition of the LF appears implausible to the MSB or
- the NB or MSB is missing a switching time definition of the LF or
- a switching time definition of the LF appears implausible to the NB or MSB, or
- the NB or MSB is missing a power curve definition of the LF or
- a power curve definition of the LF appears implausible to the NB or MSB.
Results
- If a definition subject to complaint has to be corrected, the use case “Transmission of a definition of LF by LF” must be carried out for the definition subject to complaint to all authorized parties 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 LF by LF” must be carried out for the definition subject to complaint to all authorized parties to which the definition was not transmitted.
First message
NB sends “Complaint about a definition of the LF” (step 1). From here on, it is the turn of the party involved on this page.
Objective
- The MSB has complained about an implausible or missing metering time period definition of the LF, or
- the NB or MSB has submitted a complaint about an implausible or missing switching time definition of the LF or
- the NB or MSB has submitted a complaint about an implausible or missing power curve definition of the LF.
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.
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