Billing data for grid usage settlement — NB view
The NB transmits the billing data for grid usage settlement to the LF. The LF checks the data and gives the NB a quality response message on the content of the data. If the LF expects different data content, it states this in the response message. In this case, the NB informs the LF of the processing status of its response message.
Process flow from the perspective of the NB
Process steps
Billing data for grid usage settlement
NB LFCheck identifiers
- 55218 — Bill. data NNA · AS4
Flow
Prozessauslöser
START_ABR_NNThe 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
Response message on billing data
NB LFZ10Z16Z43Z33Check identifiers
- 55220 — Response message/request bill. data NNA · AS4
Flow
Message from LF · AS4
Response per decision tree
55220→ E_0610 · LF · Check billing data for grid usage settlement (Based on EBD: E_0408_Check change from the NB)
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic
- Read market location
APERAK checks
55220→Z1055220→Z1655220→Z43— APERAK check: Does object property match?55220→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
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 of the response message
NB LF210475517755180552275561455621+13 moreSTART_VERSAND_BEARB_MELDUNGSTART_VERSAND_STATUSMELDUNGCheck identifiers
- 21047 — Processing status message · AS4
Flow
Triggered by incoming message
- 21047 — Processing status message
- 55177
- 55180
- 55227
- 55614
- 55621
- 55622
- 55623
- 55624
- 55625
- 55626
- 55633
- 55634
- 55635
- 55636
- 55638
- 55671
- 55689
- 55692
The MACO APP sends this message itself, as a follow-up process after one of these incoming messages. In addition, the backend can trigger this step with an event — the next item.
Process trigger
The backend triggers this step with one of these events.
Message to LF · AS4
Response per decision tree
21047→ E_0620 · NB · Check response message (Based on EBD: E_0626_Check response message to the change)
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_0610 | Check billing data for grid usage settlement (Based on EBD: E_0408_Check change from the NB) |
| E_0620 | Check response message (Based on EBD: E_0626_Check response message to the change) |
Process information
Wording of the consolidated version, profile ch. 3.1.1.1, pp. 65–66.
Preconditions
- This is a consuming market location.
Results
If grid usage settlement takes place towards the LF, the NB carries out the use case "Transmission of the energy and demand values measured so far" in the event of an intra-year assignment of the LFN or E/G to the market location (via the use case „Start of supply“ or „Start of replacement supply / default supply“) and if the market location is billed with an energy price and a demand price as part of grid usage settlement.
Error case
Error cases
This is a generating market location or a tranche.
Further requirements
Note: There are situations in which an invoice correction can occur because of the exchange of the billing data for grid usage settlement. This is the case, for example, when a change (case b) into the past affects the period of an invoice.
Trigger
- Execution after the process step
- for assigning the LFN to the market location as part of the use case „Start of supply“ (case a).
- for assigning the LF to the market location as part of the use case „Creation“ (case a).
- for assigning the E/G to the market location as part of the use case „Start of replacement supply / default supply“ (case a).
- for ending the assignment of the LF to the market location as part of the use case „End of supply from LF to NB“ (case a).
- for ending the assignment of the LF to the market location as part of the use case „End of supply from NB to LF“ (case a).
- on the processing status of the order placement as part of the SD „Order placement of a change of billing data from LF to NB“, provided a change of the billing data for the grid usage settlement is to be made (case b).
- Execution independent of the processes above,
- provided the NB itself determines that billing data for the grid usage settlement towards the LF has changed (case b) (e.g. change of the grid usage settlement model from energy price/base price to energy price/demand price).
- provided the NB assumes that there is a data discrepancy between NB and LF (case b).
Runs beforehand: Start of replacement supply / default supply, Order placement for a change of billing data from LF to NB, Order placement for a change of billing data for balancing group settlement from ÜNB to NB, Start of supply, End of supply from LF to NB, End of supply from NB to LF, Creation — these processes name the one shown here in their result.
- Execution after the process step
First message
The party involved on this page sends this itself: “Billing data grid usage settlement” to LF (step 1).
Objective
The billing data for the grid usage settlement have been exchanged.
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 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.
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: 3