Setup of the configurations following an assignment of a LF to a market location or tranche — MSB view
The NB informs the MSB of the directly affected location (here: market location) of the configurations to be set up at market location and metering location level. If metering locations are affected by the configurations for which the MSB of the directly affected location does not perform the metering point operation, it involves the respective further MSB for these metering locations.
Process flow from the perspective of the MSB
Process steps
Setup of the configurations
MSB NBZ1017135datenSchreibenCheck identifiers
- 17134 — Setup configuration assignment LF of NB · AS4
Flow
Message from NB · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic
- Read market location
APERAK checks
17134→Z10
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
Load data for the check
- Read metering location
GET /getMeterLocationBasic
- Read metering location
Trigger follow-up process
- 17135 — Setup configuration assignment LF of MSB
datenSchreiben
After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
Setup of the configurations
MSB further MSB17134Check identifiers
- 17135 — Setup configuration assignment LF of MSB · AS4
Flow
Triggered by incoming message
- 17134 — Setup configuration assignment LF of NB
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Load data for processing
LESEN_ANFRAGE_BASISLESEN_AUFTRAG_BASIS- Read market location
GET /getMarketLocationBasic - Read metering location
GET /getMeterLocationBasic
Message to further MSB · 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. 1.3.7.1, pp. 80–81.
Preconditions
- These are not chargeable configurations.
- These are configurations with transmission of values according to type 1.
- The ÜNB knows the MP-ID of the MSB of the market location, provided the set-up of the configurations should be relevant for the ÜNB.
Results
- If a master data change is required for the respective location due to the setup of the configurations, MSB of the respective affected location carries out the use case “Master data change” (here: SD “Master data change originating from MSB (responsible)”) (GPKE Part 4).
- The MSB of the respective affected location (here: metering location) executes the SD „Processing and transmission of values from the MSB of the metering location“ (WiM part 2). It is executed either as a consequence of the master data change (see first bullet point) or, if no master data change is required, directly within the use case described here. Note: in the table „Presentation of the values to be transmitted" (chapter 2.5.5. WiM part 2), besides no. 1 of the table, no. 2 and 3 in particular are to be observed.
Further requirements
- Note: The allocation start of LF for the market location or tranche of the triggering use case (“Start of supply”, “Creation”, “Start of replacement supply / default supply”, “Establishing a 100% LF assignment to a generating market location”) corresponds to the start of the effective period of the configurations. The start of the effective period is the same for all affected locations.
- This use case also applies if LFN and LFA are identical.
Trigger
- Execution after the process step (GPKE part 2)
- for assigning the LFN to the market location or tranche as part of the use case „Start of supply“.
- for assigning the LF to the market location or tranche as part of the use case „Creation“.
- for assigning the E/G to the consuming market location as part of the use case „Start of replacement supply / default supply“.
- 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“.
Runs beforehand: Start of replacement supply / default supply, 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, Creation — these processes name the one shown here in their result.
- Execution after the process step (GPKE part 2)
First message
NB sends “Setup of the configurations” (step 1). From here on, it is the turn of the party involved on this page.
Objective
The configurations (e.g. metering products) are set up at market location and metering location level.
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.
These read accesses are not listed in the API catalogue of this format version; the step therefore shows only their command, without address and without button.
Applies to: 2