Order placement for a master data change to the NB (responsible) — MSB view
The process describes the request/ order placement of values of master data by an authorised party from the party responsible for the master data. The responsible party checks the order placement and informs the authorised party of the processing status.
Process flow from the perspective of the MSB
Process steps
1 Order placement of a change of master data from the LF to NB
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
Order placement of a change of master data from the MSB to NB
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
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
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 order placement
MSB NBZ33Check identifiers
- 21047 — Processing status message · AS4
Flow
Message from NB · AS4
Response per decision tree
21047→ E_0576 · NB · Check order placement for master data change (Based on EBD: E_0573_Check order placement for master data 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
Decision trees of this process
| EBD | Name |
|---|---|
| E_0576 | Check order placement for master data change (Based on EBD: E_0573_Check order placement for master data change) |
| E_0573 | Check order placement for master data change |
| E_0577 | Check order placement for master data change (Based on EBD: E_0573_Check order placement for master data change) |
Process information
Wording of the consolidated version, profile ch. 1.5.1, pp. 18–19.
Preconditions
- A current or future agreed assignment of the market partners in the respective role to the location exists.
Results
- If the responsible party must assume that the ordered values of master data are not available to one or more authorised parties, it transmits them to those parties within the use case “Master data change”, so that all authorised parties have the same values of the master data.
- If the responsible party can assume that the technical result is available to every authorised party: The subsequent processes are based on reconciled and synchronous values of the master data.
Error case
Error cases
- A processing status for the order placement is not available on time.
Further requirements
- In the case of the SD “Order placement for a master data change to 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. Accordingly, the authorised parties can in turn send an order placement for a master data change to MSBN.
Trigger
- The authorised party has a new value for a master data item.
- The authorised party assumes there is a data discrepancy between the authorised parties and the responsible party.
First message
The party involved on this page is itself the sender of: „Order placement for a change of master data from the MSB to NB“ to NB (step 3).
Objective
The processing status of the order placement of the authorized party is available to the authorized party from the responsible party.
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: 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: 4