Order placement for a master data change to the ÜNB (responsible) — ÜNB 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 ÜNB
Process steps
Order placement of a change of master data from the NB to ÜNB
ÜNB NBFlow
Message from NB
Write endpoint
- Transaction created —
ERSTELLEN_PROZESSDATEN
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created —
Processing status of the order placement
ÜNB NBFlow
Message to NB
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Order placement of a change of master data from the LF to ÜNB
ÜNB LFFlow
Message from LF
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated —
Processing status of the order placement
ÜNB LFFlow
Message to LF
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Order placement of a change of master data from the MSB to ÜNB
ÜNB MSBFlow
Message from MSB
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated —
Processing status of the order placement
ÜNB MSBFlow
Message to MSB
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
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 NB to ÜNB” (step 1). From here on, the party involved on this page has the next move.
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.
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: 1
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.
For this market role there is no write catalog; the step therefore shows only the command of the write call, without address and without button.