Billing data for balancing group settlement — NB view
The NB transmits the billing data for the balancing group settlement to the LF and, where applicable, to the ÜNB. The LF or ÜNB checks the data and gives the NB a quality response message on the content of the data. If the LF or ÜNB expects different data content, it states this in the response message. In this case the NB informs the LF or ÜNB of the processing status of its response message.
Process flow from the perspective of the NB
Process steps
Billing data balancing group settlement from the NB to LF
NB LFCheck identifiers
Flow
Prozessauslöser
START_ABR_BKThe backend triggers this step with this event.
Load data for processing
- Read balancing
GET /getAccountingBasic - Read market location
GET /getMarketLocationBasic
- Read balancing
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 LFZ10Z16Z43Z33E_0595 Check order placementE_0619 Check response message (Based on EBD: E_0626_Check response message to the change)21047Check identifiers
Flow
Message from LF · AS4
Response per decision tree
55156,55673→ E_0611 · LF · Check billing data for balancing group 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
55156,55673→Z1055156,55673→Z1655156,55673→Z43— APERAK check: Does object property match?55156,55673→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
Decision tree
Trigger follow-up process
- 21047 — Processing status message
After processing, the MACO APP starts this follow-up process itself.
Processing status of the response message
NB LF5515655614START_VERSAND_BEARB_MELDUNGSTART_VERSAND_STATUSMELDUNGCheck identifiers
- 21047 — Processing status message · AS4
Flow
Triggered by incoming message
- 55156 — Response message/request bill. data BG bill. cons. MaLo
- 55614 — Response message/request bill. data BG settl. consum. MaLo
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_0619 · 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
Billing data balancing group settlement from the NB to ÜNB
NB ÜNBCheck identifiers
Flow
Prozessauslöser
START_ABR_BKThe backend triggers this step with this event.
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
Response message on billing data
NB ÜNBZ10Z16Z43Z33E_0618 Process response message (Based on EBD: E_0626_Check response message to the change)E_0613 Check order placement (Based on EBD: E_0573_Check order placement for master data change)21047Check identifiers
Flow
Message from ÜNB · AS4
Response per decision tree
55614,55675→ E_0612 · ÜNB · Check billing data for balancing group settlement
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic
- Read market location
APERAK checks
55614,55675→Z1055614,55675→Z1655614,55675→Z43— APERAK check: Does object property match?55614,55675→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
55614→ Transaction updated — Update process dataPOST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
Decision tree
Trigger follow-up process
- 21047 — Processing status message
After processing, the MACO APP starts this follow-up process itself.
Processing status of the response message
NB ÜNB5515655614START_VERSAND_BEARB_MELDUNGSTART_VERSAND_STATUSMELDUNGCheck identifiers
- 21047 — Processing status message · AS4
Flow
Triggered by incoming message
- 55156 — Response message/request bill. data BG bill. cons. MaLo
- 55614 — Response message/request bill. data BG settl. consum. MaLo
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 ÜNB · AS4
Response per decision tree
21047→ E_0618 · NB · Process 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_0611 | Check billing data for balancing group settlement (Based on EBD: E_0408_Check change from the NB) |
| E_0612 | Check billing data for balancing group settlement |
| E_0618 | Process response message (Based on EBD: E_0626_Check response message to the change) |
| E_0619 | 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.2.1, pp. 69–70.
Preconditions
- The following applies to the transmission of the billing data for the balancing group settlement to ÜNB: transmission, provided that the aggregation responsibility
- passes from the NB to the ÜNB or
- lies with the ÜNB and the data is relevant for the ÜNB or
- passes from the ÜNB to the NB.
- The following applies to the transmission of the billing data for the balancing group settlement to ÜNB: transmission, provided that the aggregation responsibility
Results
- The activation of MaBiS metering points may be required for the transmission of aggregated time series according to MaBiS.
- If a master data change is required, NB carries out the use case "master data change" (here: SD “Master data change originating from NB (responsible)”) (GPKE Part 4).
- If it is a market location or tranche with balancing on the basis of quarter-hour values: NB carries out the use case “Master data for balancing group integrity” (GPKE Part 4).
Trigger
- Execution after the process step
- for assigning the LFN to the market location or tranche as part of the use case „Start of supply“ (case a).
- for assigning the LF to the market location or tranche as part of the use case „Creation“ (case a).
- for assigning the E/G to the consuming market location as part of the use case „Start of replacement supply / default supply“ (case a).
- for assigning the LFN to the generating market location or to the tranche as part of the use case „Establishing a 100% LF assignment to a generating market location“ (case a).
- for ending the assignment of the LF to the market location or tranche 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 or tranche 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 balancing group settlement is to be made (case b).
- on the processing status of the order placement as part of the SD „Order placement of a change of billing data for the balancing group settlement from ÜNB to NB“, provided a change of the billing data for the balancing group settlement is to be made (case b).
- Execution independent of the processes above,
- provided the NB itself determines that billing data for the balancing group settlement has changed (case b) (e.g. change of the annual consumption forecast). This does not apply to a change of the MSB as part of the WiM part 1.
- provided the NB assumes that there is a data discrepancy between NB and LF or between NB and ÜNB (case b).
- provided the NB transfers the aggregation responsibility to the ÜNB (case b).
- provided the NB transfers the aggregation responsibility to the NB (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, Case 1: LF assignment for EEG market location without DV obligation or KWKG market location without DV obligation, Case 2: LF assignment for EEG market location with DV obligation, Case 3: LF assignment for KWKG market location with DV obligation or non-EEG / non-KWKG market location and the market location is mapped without tranches, Case 4: LF assignment for KWKG market location with DV obligation or non-EEG / non-KWKG market location and the market location is mapped with tranches, 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 balancing group settlement from the NB to the LF” to LF (step 1).
Objective
The billing data for the balancing group 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.
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.