# Order placement for a master data change to the ÜNB (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 \nSystem diagram: Bestellung zur Stammdatenänderung an ÜNB (verantwortlich) — view of LF\n\n\nCustomer backend system\n\nMACO APP · LF\n\nMarket partner\n\n\n\n3. Bestellung einer Änderung\nvon Stammdaten vom LF an\nÜNB\n\nÜNB\n\nMessage\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n4. Bearbeitungsstand zur\nBestellung\n\n\nÜNB\n\nMessage\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Bestellung zur Stammdatenänderung an ÜNB (verantwortlich) — view of LF\n\n\nBackend (customer)\n\n\nMACO APP · LF\n\n\nNB\n\n\nÜNB\n\n\nMSB\n\n\n1. Bestellung einer Änderung von Stammdaten vom…\n\n2. Bearbeitungsstand zur Bestellung\n\n3. Bestellung einer Änderung von Stammdaten vom…\n\nUpdate transaction\nUpdate process data\n\n4. Bearbeitungsstand zur Bestellung\n\nUpdate transaction\nUpdate process data\n\n5. Bestellung einer Änderung von Stammdaten vom…\n\n6. Bearbeitungsstand zur Bestellung\n"} titel="LF" /> ## Process steps ### Order placement of a change of master data from the NB to ÜNB This step runs between other market partners and is not relevant for this view. ### Processing status of the order placement This step runs between other market partners and is not relevant for this view. ### Order placement of a change of master data from the LF to ÜNB **Flow**
  1. Message to **ÜNB**
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-lf/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Processing status of the order placement **Flow**
  1. Message from **ÜNB**
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-lf/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend with the data of the incoming message.
### Order placement of a change of master data from the MSB to ÜNB This step runs between other market partners and is not relevant for this view. ### Processing status of the order placement This step runs between other market partners and is not relevant for this view. ## Process information Wording of the consolidated version, profile ch. 1.5.1, pp. 18–19.
  1. ### Preconditions - A current or future agreed assignment of the market partners in the respective role to the location exists.
  2. ### 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.
  3. ### Error case #### Error cases - A processing status for the order placement is not available on time.
  4. ### Further requirements - In the case of the SD “[Order placement for a master data change to MSB (responsible)](/en/prozessdoku/202610/LF/GPKE-Teil4-bestellung-zur-stammdatenaenderung-an-msb-verantwortlich)” 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](/en/prozessdoku/202610/MSB--MSBA/WiM-Teil1-geraeteuebernahme)” (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](/en/prozessdoku/202610/MSB--MSBA/WiM-Teil1-geraeteuebernahme)”), MSBN is also entitled to apply the SD “[Master data change originating from MSB (responsible)](/en/prozessdoku/202610/LF/GPKE-Teil4-stammdatenaenderung-vom-msb-verantwortlich-ausgehend)” 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.
  5. ### 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.
  6. ### First message The party involved on this page is itself the sender of: „Order placement for a change of master data from the LF to ÜNB“ to **ÜNB** (step 3).
  7. ### 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. - [View NB](/en/prozessdoku/202610/NB/GPKE-Teil4-bestellung-zur-stammdatenaenderung-an-uenb-verantwortlich) — NB - [View MSB](/en/prozessdoku/202610/MSB/GPKE-Teil4-bestellung-zur-stammdatenaenderung-an-uenb-verantwortlich) — MSB - [View ÜNB](/en/prozessdoku/202610/UENB/GPKE-Teil4-bestellung-zur-stammdatenaenderung-an-uenb-verantwortlich) — ÜNB · market role UENB *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 source does not yet name the event that triggers these steps. Applies to: [3](#schritt-3) 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](#schritt-4) 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. Applies to: [3](#schritt-3), [4](#schritt-4)