Master data change initiated by NB (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
1 Change from the NB to LF
NB LF
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 55615 — Change of NeLo data · AS4
- 55620 — Change of MeLo data · AS4
- 55175 — Change to the location bundle structure · AS4
- 55225 — Change reactive bill. data of the NeLo · AS4
- 55616 — Change of MaLo data · AS4
- 55617 — Change of TR data · AS4
- 55618 — Change of SR data · AS4
- 55619 — Change of tranche data · AS4
- 55691 — Change of MaLo package ID · AS4
2 Response message on change
LF NB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 55621 — Response message/request NeLo data · AS4
- 55180 — Response message/request location bundle structure · AS4
- 55227 — Response message/request reactive bill. data of the NeLo · AS4
- 55622 — Response message/request MaLo data · AS4
- 55623 — Response message/request TR data · AS4
- 55624 — Response message/request SR data · AS4
- 55625 — Response message/request tranche data · AS4
- 55626 — Response message/request MeLo data · AS4
- 55692 — Response message/request MaLo package ID · AS4
Response per decision tree
55621,55180,55227,55622,55623,55624,55625,55626,55692→ E_0408 · LF · Check change from the NB
Change from the NB to MSB
MSB NBZ10Z44E_0409 Check change from the NB (Based on EBD: E_0408_Check change from the NB)551775563355634556355563655638+1 moreCheck identifiers
Flow
Message from NB · AS4
Load data for the incoming check
- Read grid location
GET /getGridLocationBasic - Read market location
GET /getMarketLocationBasic - Read technical resource
GET /getTechnicalResourceBasic - Read controllable resource
GET /getControllableResourceBasic - Read metering location
GET /getMeterLocationBasic
- Read grid location
APERAK checks
55627,55173,55628,55629,55630,55632,55691→Z1055628→Z44— APERAK check: Does object property match?
Write endpoint
55627,55628,55629,55630,55632→ Transaction updated — Update process dataPOST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
Write endpoint
55173→ Transaction created — Create process dataPOST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
Write endpoint
55691→ Transaction created — Create process dataPOST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
Decision tree
55627,55173,55628,55629,55630,55632,55691→ E_0409 — Check change from the NB (Based on EBD: E_0408_Check change from the NB)
Trigger follow-up process
- 55177 — Response message/request location bundle structure
- 55633 — Response message/request NeLo data
- 55634 — Response message/request MaLo data
- 55635 — Response message/request TR data
- 55636 — Response message/request SR data
- 55638 — Response message/request MeLo data
- 55692 — Response message/request MaLo package ID
After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
Response message on change
MSB NB551735562755628556295563055632+1 moreCheck identifiers
- 55633 — Response message/request NeLo data · AS4
- 55177 — Response message/request location bundle structure · AS4
- 55634 — Response message/request MaLo data · AS4
- 55635 — Response message/request TR data · AS4
- 55636 — Response message/request SR data · AS4
- 55638 — Response message/request MeLo data · AS4
- 55692 — Response message/request MaLo package ID · AS4
Flow
Triggered by incoming message
- 55173 — Change to the location bundle structure
- 55627 — Change of NeLo data
- 55628 — Change of MaLo data
- 55629 — Change of TR data
- 55630 — Change of SR data
- 55632 — Change of MeLo data
- 55691 — Change of MaLo package ID
The MACO APP sends this message itself, as a follow-up process after one of these incoming messages.
Load data for processing
- Read grid location
GET /getGridLocationBasic - Read market location
GET /getMarketLocationBasic - Read technical resource
GET /getTechnicalResourceBasic - Read controllable resource
GET /getControllableResourceBasic - Read metering location
GET /getMeterLocationBasic
- Read grid location
Message to NB · AS4
Response per decision tree
55633,55177,55634,55635,55636,55638,55692→ E_0409 · MSB · Check change from the NB (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 NBZ33Check identifiers
- 21047 — Processing status message · AS4
Flow
Message from NB · AS4
Response per decision tree
21047→ E_0627 · NB · 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
9 Response message on change
ÜNB NB
This step runs between other market partners and is not relevant for this view.
Check identifiers
Response per decision tree
55689,55692→ E_0572 · ÜNB · Check change from the NB (Based on EBD: E_0408_Check change from the NB)
Decision trees of this process
| EBD | Name |
|---|---|
| E_0409 | Check change from the NB (Based on EBD: E_0408_Check change from the NB) |
| E_0627 | Check response message to the change (Based on EBD: E_0626_Check response message to the change) |
| E_0408 | Check change from the NB |
| E_0572 | Check change from the NB (Based on EBD: E_0408_Check change from the NB) |
| E_0626 | Check response message to the change |
| E_0628 | 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: Billing data for balancing group settlement, 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, End of supply from NB to LF, Creation, Transmission of the calculation formula — these processes name the one shown here in their result.
First message
NB sends “Change from NB 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 process begins for the own role with their message, so the transaction is created.
Applies to: 4
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