Order placement for a master data change to the LF (responsible) — LF 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 LF
Process steps
Order placement of a change of master data from the NB to LF
LF NBZ10Z44Z33E_0629 Check response message to the change (Based on EBD: E_0626_Check response message to the change)E_0588 Check order placement for master data change (Based on EBD: E_0573_Check order placement for master data change)21047Check identifiers
Flow
Message from NB · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic - Read grid location
GET /getGridLocationBasic
- Read market location
APERAK checks
55137,55232→Z10— APERAK check: Is location known ?55137→Z44— APERAK check: Does object property match?55137,55232→Z33— APERAK check: Is referenced message known ?
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
- 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 the check
- Read market location
GET /getMarketLocationBasic - Read grid usage contract
GET /getGridUsageContractBasic LESEN_VERWENDUNGSZEITRAUM_BASIS- Read grid location
GET /getGridLocationBasic
- Read market location
Decision tree
Trigger follow-up process
- 21047 — Processing status message
After processing, the MACO APP starts this follow-up process itself.
Processing status of the order placement
LF NB551365513755232Check identifiers
- 21047 — Processing status message · AS4
Flow
Triggered by incoming message
- 55136 — Response message/request data of the MaLo
- 55137 — Response message/request data of the MaLo
- 55232 — Response message/request reactive bill. data of the NeLo
The MACO APP sends this message itself, as a follow-up process after one of these incoming messages.
Message to NB · AS4
Response per decision tree
21047→ E_0588 · LF · Check order placement for master data change (Based on EBD: E_0573_Check order placement for master data change)
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
Order placement of a change of master data from the MSB to LF
LF MSBZ10Z43Z33E_0630 Check response message to the change (Based on EBD: E_0626_Check response message to the change)E_0589 Check order placement for master data change (Based on EBD: E_0573_Check order placement for master data change)21047Check identifiers
- 55136 — Response message/request data of the MaLo · AS4
Flow
Message from MSB · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic
- Read market location
APERAK checks
55136→Z10— APERAK check: Is location known ?55136→Z43— APERAK check: Does object property match?55136→Z33— APERAK check: Is referenced message known ?
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
- 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 the check
- Read balancing
GET /getAccountingBasic - Read energy supply contract
GET /getEnergySupplyContractBasic - Read market location
GET /getMarketLocationBasic - Read grid usage contract
GET /getGridUsageContractBasic LESEN_VERWENDUNGSZEITRAUM_BASIS
- Read balancing
Decision tree
Trigger follow-up process
- 21047 — Processing status message
After processing, the MACO APP starts this follow-up process itself.
Processing status of the order placement
LF MSB551365513755232Check identifiers
- 21047 — Processing status message · AS4
Flow
Triggered by incoming message
- 55136 — Response message/request data of the MaLo
- 55137 — Response message/request data of the MaLo
- 55232 — Response message/request reactive bill. data of the NeLo
The MACO APP sends this message itself, as a follow-up process after one of these incoming messages.
Message to MSB · AS4
Response per decision tree
21047→ E_0589 · LF · Check order placement for master data change (Based on EBD: E_0573_Check order placement for master data change)
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
Order placement of a change of master data from the ÜNB to LF
LF ÜNBFlow
Message from ÜNB
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
Processing status of the order placement
LF ÜNBFlow
Message to Ü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
Decision trees of this process
| EBD | Name |
|---|---|
| E_0588 | Check order placement for master data change (Based on EBD: E_0573_Check order placement for master data change) |
| E_0589 | 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
NB sends “Order placement for a change of master data from the NB to LF” (step 1). From here on, it is the turn of the party involved on this page.
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.
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: 5
For the check identifiers of these steps there is no test case in the test data set; the »Try it out« button of the write interface therefore offers no body.