Billing of grid usage — NB view
Process flow from the perspective of the NB
Process steps
ongoing meter reading values
NB LF17103Check identifiers
Flow
Triggered by incoming message
The MACO APP sends this message itself, as a follow-up process after this incoming message. In addition, the backend can trigger this step with an event — the next item.
Prozessauslöser
START_ERHEBUNG_MESSWERTEThe backend triggers this step with this event.
Message to LF · 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
Grid usage invoice
NB LFFlow
Message to LF · 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
Response
NB LFZ33Flow
Message from LF · AS4
Response per decision tree
33002→ E_3018 · Check grid usage settlement
APERAK checks
33001,33002→Z33
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
Notification that the original grid usage invoice was correct
NB LFCheck identifiers
- 29001 — Rejection of REMADV · AS4
Flow
Message to LF · AS4
Response per decision tree
29001→ E_3035 · Check of other data relevant to the billing period and/or retroactive notifications
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
Response
NB LFZ33Flow
Message from LF · AS4
Response per decision tree
33002→ E_3036 · Check grid usage invoice again
APERAK checks
33001,33002→Z33
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
Cancellation of the original invoice
NB LFCheck identifiers
- 31004 — Cancellation invoice · AS4
Flow
Message to LF · 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
Response
NB LFZ33Flow
Message from LF · AS4
Response per decision tree
33002→ E_3038 · LF · Check whether a response to the cancellation is required (Based on electricity EBD: E_0459_Check whether a response to the cancellation is required)
APERAK checks
33001,33002→Z33
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
Decision trees of this process
| EBD | Name |
|---|---|
| E_3018 | Check grid usage settlement |
| E_3035 | Check of other data relevant to the billing period and/or retroactive notifications |
| E_3036 | Check grid usage invoice again |
| E_3038 | Check whether a response to the cancellation is required (Based on electricity EBD: E_0459_Check whether a response to the cancellation is required) |
Process information
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 LF — LF
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.
The source does not yet name the event that triggers these steps.
Applies to: 2
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.
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: 6