Master data change initiated by LF (responsible) — View MSB
The process describes the transmission of changed values of master data from the responsible party to the authorised parties. The authorised party checks the data and gives the responsible party a quality response message on the content of the data. If the authorised party expects a different data content, it states this in the response message. In this case the responsible party informs the authorised party of the processing status of that response message.
Process flow from the perspective of the MSB
Process steps
2 Response message on change
NB LF
This step runs between other market partners and is not relevant for this view.
Check identifiers
Response per decision tree
55137,55232,55694→ E_0410 · NB · Check change from the LF (Based on EBD: E_0408_Check change from the NB)
Change from the LF to MSB
MSB LFZ10E_0578 Check change from the LF (Based on EBD: E_0408_Check change from the NB)55136Check identifiers
- 55110 — Change data of the MaLo · AS4
Flow
Message from LF · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic
- Read market location
APERAK checks
55110→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
Decision tree
55110→ E_0578 — Check change from the LF (Based on EBD: E_0408_Check change from the NB)
Load data for processing
- Read market location
GET /getMarketLocationBasic
- Read market location
Trigger follow-up process
- 55136 — Response message/request data of the MaLo
After processing, the MACO APP starts this follow-up process itself.
Response message on change
MSB LF55110Check identifiers
- 55136 — Response message/request data of the MaLo · AS4
Flow
Triggered by incoming message
- 55110 — Change data of the MaLo
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Load data for processing
- Read market location
GET /getMarketLocationBasic
- Read market location
Message to LF · AS4
Response per decision tree
55136→ E_0578 · MSB · Check change from the LF (Based on EBD: E_0408_Check change from the NB)
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
Processing status of the response message
MSB LFZ33Check identifiers
- 21047 — Processing status message · AS4
Flow
Message from LF · AS4
Response per decision tree
21047→ E_0630 · LF · Check response message to the change (Based on EBD: E_0626_Check response message to the change)
APERAK checks
21047→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
Load data for processing
LESEN_STATUSMITTEILUNG_BASIS
8 Change from the LF to ÜNB
LF ÜNB
This step runs between other market partners and is not relevant for this view.
9 Response message on change
ÜNB LF
This step runs between other market partners and is not relevant for this view.
10 Processing status of the response message
LF ÜNB
This step runs between other market partners and is not relevant for this view.
Decision trees of this process
| EBD | Name |
|---|---|
| E_0578 | Check change from the LF (Based on EBD: E_0408_Check change from the NB) |
| E_0630 | Check response message to the change (Based on EBD: E_0626_Check response message to the change) |
| E_0410 | Check change from the LF (Based on EBD: E_0408_Check change from the NB) |
| E_0629 | Check response message to the change (Based on EBD: E_0626_Check response message to the change) |
Process information
Wording of the consolidated version, profile ch. 1.4.1, p. 5.
Preconditions
- A current or future agreed assignment of the market partners in the respective role to the location exists.
Results
- The follow-up processes build on reconciled and synchronous master data values from the change date onwards.
- The change carried out in this use case may, among other things, result in a transmission of values from MSB being required. The order issuance for the transmission of values results from the values of the corresponding master data item. No further order issuance is made towards MSB.
Error case
Result in the error case
The responsible party must enter into bilateral clearing with the parties involved and, where applicable, trigger the process again.
Error cases
The response message leads to the conclusion that the data are not held in sync across the market.
Further requirements
- In the case of the SD “Master data change originating from MSB (responsible)” the following applies: The responsible MSB of a metering location is always the MSB that is assigned to the metering location at the point in time at which the value of the master data item is changed. The following exception applies: If the use case “Device takeover” (WiM Part 1) takes place at the metering location, then in addition to the aforementioned MSB (referred to as MSBA in the use case “Device takeover”), MSBN is also entitled to apply the SD “Master data change originating from MSB (responsible)” for this metering location as the responsible MSB.
Trigger
- The party responsible for a master data item has a new value for that master data item. The responsible party obtains this information, for example, from preceding processes or messages that cause the value of a master data item to change for one or more authorised parties.
- The responsible party assumes there is a data discrepancy between the authorised parties and the responsible party.
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.
First message
LF sends “Change from LF to MSB” (step 4). From here on, the party involved on this page has the next move.
Objective
The responsible party and the authorized parties have the same master data values.
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. The numbers are those of the source; where one is missing, it is missing there.
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: 6
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.
Applies to: 6