Complaint from ÜNB — View MSB-MALO
The NB, LF or ÜNB raises a complaint about implausible or missing values (market location / metering location) with the MSB of the market location that was assigned to the market location for the time period for which the values are to be complained about, or the MSB of the market location raises a complaint about implausible or missing values of the metering location with the MSB of the metering location that was assigned to the metering location for the time period for which the values are to be complained about, or the MSB of the market location or the MSB of the metering location identifies that values were not sent by it or have to be corrected by it, without a complaint having been received from another market role. The respective MSB checks the complaint about the affected values. In line with the check results, the MSB transmits values (including binding information giving the reason for the change of the values), provided these have not yet been transmitted (for values that do not exist), or corrected values (for erroneous values), and cancels erroneous values where necessary or rejects the complaint.
Process flow from the perspective of the MSB (MSB-MALO)
Process steps
Complaint value
MSB (corresponds to MSB at the market location object) ÜNBCheck identifiers
- 17113 — Complaint about values · AS4
Flow
Message from ÜNB · AS4
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 at termination of the process
MSB (corresponds to MSB at the market location object) ÜNBCheck identifiers
- 19114 — Rejection of complaint · AS4
Flow
Message to ÜNB · AS4
Response per decision tree
19114→ E_0230 · 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
Complaint value of a metering location
MSB (corresponds to MSB at the market location object) MSB (corresponds to MSB at the metering location object)Check identifiers
- 17113 — Complaint about values · AS4
Flow
Message to MSB (corresponds to MSB at the metering location object) · AS4
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
Processing status at termination of the process
MSB (corresponds to MSB at the market location object) MSB (corresponds to MSB at the metering location object)Check identifiers
- 19114 — Rejection of complaint · AS4
Flow
Message from MSB (corresponds to MSB at the metering location object) · AS4
Response per decision tree
19114→ E_0231 · Check complaint
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated — Update process data
Processing status at termination of the process
MSB (corresponds to MSB at the market location object) ÜNBCheck identifiers
- 19114 — Rejection of complaint · AS4
Flow
Message to ÜNB · AS4
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
Process information
Wording of the consolidated version, profile ch. 2.7.1, pp. 44–45.
Preconditions
- The MSB knows the metering locations and market location
- The MSB knows the calculation rules for forming the values of the market location.
- LF, NB, ÜNB or MSB is entitled to submit a complaint about values.
Results
Transmission of the values to the authorised parties.
Further requirements
- If MSB of the market location determines, in the case of missing values, that these values were not sent only to individual authorised parties, the values also only have to be transmitted to those authorised parties.
- The GPKE use case "business data request" (GPKE part 4) must not be used for the complaint about implausible or missing values.
- A complaint about missing values is only possible once the deadline for the values to be transmitted from table 2.5.5 has been exceeded. The following situation is excluded from this: if a delivery note from NB is received by LF and LF has not yet received any energy quantities for the delivery note period from the MSB of the market location, a complaint about missing values must be made immediately by LF to the MSB of the market location, irrespective of the deadlines in table 2.5.5.
Trigger
- A value on hand appears implausible to the LF, NB, ÜNB or MSB, or
- the LF, NB, ÜNB or MSB does not have the required values in the corresponding quality on time or
- the LF has no energy quantities available for checking the delivery note for the market location concerned.
First message
ÜNB sends “Complaint about value” (step 1). From here on, it is the turn of the party involved on this page.
Objective
The NB, LF or ÜNB has raised a complaint about implausible or missing values with the MSB of the market location, or the MSB of the market location has raised a complaint about implausible or missing values with the MSB of the metering location, or the MSB of the market location or the MSB of the metering location has identified that values were not sent by it or have to be corrected by it, without a complaint having been received from another market role.
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-MELO — MSB at the metering location object · market role MSB
- View ÜNB — ÜNB · market role UENB
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 numbers are those of the source; where one is missing, it is missing there.
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
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: 6