Master data change initiated by MSB (responsible) — View NB
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 NB
Process steps
Change from the MSB to NB
NB MSBZ10Z16Z33E_0415 Check change from the MSB (Based on EBD: E_0408_Check change from the NB)555555555955644556455564655647+1 moreCheck identifiers
Flow
Message from MSB · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic - Read grid location
GET /getGridLocationBasic - Read controllable resource
GET /getControllableResourceBasic - Read tranche
GET /getTrancheBasic - Read metering location
GET /getMeterLocationBasic
- Read market location
APERAK checks
55557,55639,55640,55641,55642,55643→Z1055557,55639,55640,55641,55642,55643→Z1655553→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
55553→ Transaction updated —AKTUALISIEREN_PROZESSDATEN_BASIS
Updates the existing transaction in the backend with the data of the incoming message.
Decision tree
55557,55553,55639,55640,55641,55642,55643→ E_0415 — Check change from the MSB (Based on EBD: E_0408_Check change from the NB)
Trigger follow-up process
- 55555 — Request data of the individual order placement
- 55559 — Response message/request MSB bill. data of the MaLo
- 55644 — Response message/request NeLo data
- 55645 — Response message/request MaLo data
- 55646 — Response message/request SR data
- 55647 — Response message/request tranche data
- 55648 — Response message/request MeLo data
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
NB MSB555535555755639556405564155642+1 moreCheck identifiers
- 55559 — Response message/request MSB bill. data of the MaLo · AS4
- 55555 — Request data of the individual order placement · AS4
- 55644 — Response message/request NeLo data · AS4
- 55645 — Response message/request MaLo data · AS4
- 55646 — Response message/request SR data · AS4
- 55647 — Response message/request tranche data · AS4
- 55648 — Response message/request MeLo data · AS4
Flow
Triggered by incoming message
- 55553 — Data on individual order placement
- 55557 — Change MSB bill. data of the MaLo
- 55639 — Change of NeLo data
- 55640 — Change of MaLo data
- 55641 — Change of SR data
- 55642 — Change of tranche data
- 55643 — Change of MeLo data
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.
Prozessauslöser
START_BESTELLUNG_SDAEThe backend triggers this step with this event.
Load data for processing
- Read market location
GET /getMarketLocationBasic - Read grid location
GET /getGridLocationBasic - Read controllable resource
GET /getControllableResourceBasic - Read tranche
GET /getTrancheBasic - Read metering location
GET /getMeterLocationBasic
- Read market location
Message to MSB · AS4
Response per decision tree
55559,55555,55644,55645,55646,55647,55648→ E_0415 · NB · Check change from the MSB (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
NB MSBZ3321047Check identifiers
- 21047 — Processing status message · AS4
Flow
Message from MSB · AS4
Response per decision tree
21047→ E_0632 · MSB · 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
Trigger follow-up process
- 21047 — Processing status message
After processing, the MACO APP starts this follow-up process itself.
4 Change from the MSB to LF
MSB LF
This step runs between other market partners and is not relevant for this view.
5 Response message on change
LF MSB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 55654 — Response message/request NeLo data · AS4
- 55555 — Request data of the individual order placement · AS4
- 55655 — Response message/request MaLo data · AS4
- 55656 — Response message/request SR data · AS4
- 55657 — Response message/request tranche data · AS4
- 55658 — Response message/request MeLo data · AS4
Response per decision tree
55654,55555,55655,55656,55657,55658→ E_0412 · LF · Check change from the MSB (Based on EBD: E_0408_Check change from the NB)
7 Change from the MSB to further MSB
MSB further MSB
This step runs between other market partners and is not relevant for this view.
8 Response message on change
further MSB MSB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 55664 — Response message/request NeLo data · AS4
- 55555 — Request data of the individual order placement · AS4
- 55665 — Response message/request MaLo data · AS4
- 55666 — Response message/request SR data · AS4
- 55667 — Response message/request tranche data · AS4
- 55669 — Response message/request MeLo data · AS4
Response per decision tree
55664,55555,55665,55666,55667,55669→ E_0583 · MSB · Check change from the MSB (Based on EBD: E_0408_Check change from the NB)
12 Response message on change
ÜNB MSB
This step runs between other market partners and is not relevant for this view.
Check identifiers
Response per decision tree
55685,55687→ E_0639 · ÜNB · Check change from the MSB (Based on EBD: E_0408_Check change from the NB)
Decision trees of this process
| EBD | Name |
|---|---|
| E_0415 | Check change from the MSB (Based on EBD: E_0408_Check change from the NB) |
| E_0632 | Check response message to the change (Based on EBD: E_0626_Check response message to the change) |
| E_0412 | Check change from the MSB (Based on EBD: E_0408_Check change from the NB) |
| E_0583 | Check change from the MSB (Based on EBD: E_0408_Check change from the NB) |
| E_0633 | Check response message to the change (Based on EBD: E_0626_Check response message to the change) |
| E_0634 | Check response message to the change (Based on EBD: E_0626_Check response message to the change) |
| E_0635 | Check response message to the change (Based on EBD: E_0626_Check response message to the change) |
| E_0639 | Check change from the MSB (Based on EBD: E_0408_Check change from the NB) |
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: Termination of a configuration from MSB, Order placement for the termination of a configuration from LF to MSB, Order placement for the termination of a configuration from NB to MSB, Order placement for the termination of a configuration from the further MSB to MSB, Order placement for a configuration from LF to MSB, Order placement for a configuration from NB to MSB, Setup of the configurations on the basis of an assignment of a LF to a market location or tranche — these processes name the one shown here in their result.
First message
MSB sends “Change from MSB to NB” (step 1). From here on, it is the turn of the party involved on this page.
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.
- View LF — LF
- View MSB — MSB
- View WMSB — further metering point operator · market role MSB
- View ÜNB — ÜNB · market role UENB
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 write calls 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: 1