Process flow from the perspective of the LF (WLF)
System diagram — view of WLF 100 % 150 % 200 % Overview
System diagram: Anfrage zur Stammdatenänderung vom LF an MSB (verantwortlich) — view of LF
Customer backend system
MACO APP · LF (weiterer L…
Market partner
5. Ggf. Änderung vom MSB
NB (Verteiler)
AS4
44160, 44117
Load data for the incoming
check
Messlokation lesen
API
APERAK check: Z10
Create transaction
Create process data
API
EBD check: G_0030, G_0027
G_0030 — Antwort auf
Änderung vom MSB
G_0027 — Antwort auf
Änderung vom MSB
Trigger follow-up process:
44119, 44161
Triggered by incoming
message: 44117, 44160
6. Antwort auf Änderung vom
MSB
NB (Verteiler)
AS4
44161, 44119
Update transaction
Update process data
API
Overview — all roles of this process 100 % 150 % 200 % Close
Sequence diagram: Anfrage zur Stammdatenänderung vom LF an MSB (verantwortlich) — view of LF
Backend (customer)
MACO APP · LF (weiterer L…
LF (Berechtigter)
NB (Verteiler)
MSB (Berechtigter)
1. Anfrage an MSB
AS4 · PI 44162, 44143
2. Anfrage an MSB (Weiterleitung)
AS4 · PI 44165, 44147
3. Antwort auf Anfrage an MSB
AS4 · PI 44167, 44149 · E_3016
E_3016 — Anfrage an MSB prüfen
4. Antwort auf Anfrage an MSB
AS4 · PI 44163, 44164, 44145… · E_3017, E_3031
E_3017 — Antwort auf Anfrage an MSB (Weiterleitung) prüfen
E_3031 — Weiterleitung der Anfrage an MSB prüfen
5. Ggf. Änderung vom MSB
AS4 · PI 44160, 44117
Create transaction
Create process data
6. Antwort auf Änderung vom MSB
AS4 · PI 44161, 44119 · E_3032
E_3032 — Änderung vom MSB prüfen
Update transaction
Update process data
Process steps
1 Request to MSB LF (authorised party) → NB (distributor) This step runs between other market partners and is not relevant for this view.
Check identifiers
44162 — Request to MSB without dependencies · AS444143 — Request to MSB with dependencies · AS4 2 Request to MSB (forwarding) NB (distributor) → MSB (authorised party) This step runs between other market partners and is not relevant for this view.
Check identifiers
44165 — Not bal.-rel. request to MSB without dependencies · AS444147 — Request to MSB with dependencies · AS4 3 Response to request to MSB MSB (authorised party) → NB (distributor) This step runs between other market partners and is not relevant for this view.
Check identifiers
44167 — Response to request · AS444149 — Response to request · AS4 Response per decision tree
44167, 44149 → E_3016 · Check request to MSB 4 Response to request to MSB NB (distributor) → LF (authorised party) This step runs between other market partners and is not relevant for this view.
Check identifiers
44163 — Response to request · AS444164 — Rejection of request · AS444145 — Response to request · AS444146 — Rejection of the request · AS4 Response per decision tree
44163 → E_3031 · Check forwarding of the request to MSB44163, 44164, 44145, 44146 → E_3017 · Check response to request to MSB (forwarding) 5 Change from MSB, if applicable LF (further LF as authorised party) ← NB (distributor) Backend
MACO APP · WLF
Market partner
Receive one of these messages 44160 — Change from MSB without dependencies 44117 — Change from MSB with dependencies
AS4 44160, 44117
NB (distributor)
Backend Read metering location
API
Load data for the incoming check
APERAK check Z10
Create process data
API
Create transaction
Decision tree G_0030 Response to change from the MSBG_0027 Response to change from the MSB
Trigger follow-up process 4411944161
Check identifiers
44160 — Change from MSB without dependencies · AS444117 — Change from MSB with dependencies · AS4 Flow
Message from NB (distributor) · AS4
Load data for the incoming check
APERAK checks
44160, 44117 → Z10 — APERAK check: Is location known ? Write endpoint
Creates a new transaction in the backend with the data of the incoming message.
Decision tree
44160 → G_0030 — Response to change from the MSB44117 → G_0027 — Response to change from the MSB Trigger follow-up process
44119 — Response to change from MSB44161 — Response to change After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
6 Response to change from the MSB LF (further LF as authorised party) → NB (distributor) Backend
MACO APP · WLF
Market partner
Triggered by incoming message 4411744160
Send one of these messages 44161 — Response to change 44119 — Response to change from the MSB
AS4 44161, 44119
NB (distributor)
Update process data
API
Update transaction
Check identifiers
44161 — Response to change · AS444119 — Response to change from MSB · AS4 Flow
Triggered by incoming message
44117 — Change from MSB with dependencies44160 — Change from MSB without dependencies The MACO APP sends this message itself, as a follow-up process after one of these incoming messages.
Message to NB (distributor) · AS4
Response per decision tree
44161, 44119 → E_3032 · Check change from the MSB Write endpoint
Updates the existing transaction in the backend once the message has been created.
Decision trees of this process
EBD Name E_3032 Check change from the MSB E_3016 Check request to MSB E_3017 Check response to request to MSB (forwarding) E_3031 Check forwarding of the request to MSB
Process information
First message NB (distributor) sends “If applicable, change from MSB” (step 5). From here on, it is the turn of the party involved on this page.
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 BER — the authorised party in this process step · market role LFView NB — NBView BER — the authorised party in this process step · market role MSB
Notes on this page The source provides no use case profile for this process — objective, precondition and result are not recorded there.
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.
Step sequence reconstructed
For this process, the BNetzA consolidated version carries no sequence diagram. The steps are reconstructed from the BDEW check identifier table: grouped by the designation, ordered by the process step. The method agrees with the consolidated version in 200 of 200 cases that can be cross-checked — the individual line is nevertheless not editorially reviewed. Check it against the rulebook before adopting it into an implementation specification.