# Master data change initiated by ÜNB (responsible) — View MSB 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 MSB \nSystem diagram: Stammdatenänderung vom ÜNB (verantwortlich) ausgehend — view of MSB\n\n\nCustomer backend system\n\nMACO APP · MSB\n\nMarket partner\n\n\n\n7. Änderung vom ÜNB an\nMSB\n\nÜNB\n\nMessage\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\n8. Rückmeldung auf\nÄnderung\n\n\nÜNB\n\nMessage\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n9. Bearbeitungsstand zur\nRückmeldung\n\n\nÜNB\n\nMessage\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Stammdatenänderung vom ÜNB (verantwortlich) ausgehend — view of MSB\n\n\nBackend (customer)\n\n\nMACO APP · MSB\n\n\nÜNB\n\n\nNB\n\n\nLF\n\n\n1. Änderung vom ÜNB an NB\n\n2. Rückmeldung auf Änderung\n\n3. Bearbeitungsstand zur Rückmeldung\n\n4. Änderung vom ÜNB an LF\n\n5. Rückmeldung auf Änderung\n\n6. Bearbeitungsstand zur Rückmeldung\n\n7. Änderung vom ÜNB an MSB\n\nCreate transaction\nCreate process data\n\n8. Rückmeldung auf Änderung\n\nUpdate transaction\nUpdate process data\n\n9. Bearbeitungsstand zur Rückmeldung\n\nUpdate transaction\nUpdate process data\n"} titel="MSB" /> ## Process steps ### Change from the ÜNB to NB This step runs between other market partners and is not relevant for this view. ### Response message on change This step runs between other market partners and is not relevant for this view. ### Processing status of the response message This step runs between other market partners and is not relevant for this view. ### Change from the ÜNB to LF This step runs between other market partners and is not relevant for this view. ### Response message on change This step runs between other market partners and is not relevant for this view. ### Processing status of the response message This step runs between other market partners and is not relevant for this view. ### Change from the ÜNB to MSB **Flow**
  1. Message from **ÜNB**
  2. **Write endpoint** - Transaction created — [Create process data](/en/api/202610/backend-schreiben-msb/createprocessdata#prozessdaten-erstellen) `POST /createProcessData` Try it out Creates a new transaction in the backend with the data of the incoming message.
### Response message on change **Flow**
  1. Message to **ÜNB**
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-msb/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 response message **Flow**
  1. Message from **ÜNB**
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-msb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend with the data of the incoming message.
## Process information Wording of the consolidated version, profile ch. 1.4.1, p. 5.
  1. ### Preconditions - A current or future agreed assignment of the market partners in the respective role to the location exists.
  2. ### 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.
  3. ### 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.
  4. ### Further requirements - In the case of the SD “[Master data change originating from MSB (responsible)](/en/prozessdoku/202610/MSB/GPKE-Teil4-stammdatenaenderung-vom-msb-verantwortlich-ausgehend)” 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/MSB/GPKE-Teil4-stammdatenaenderung-vom-msb-verantwortlich-ausgehend)” for this metering location as the responsible MSB.
  5. ### 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.
  6. ### First message **ÜNB** sends “Change from ÜNB to MSB” (step 7). From here on, it is the turn of the party involved on this page.
  7. ### 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](/en/prozessdoku/202610/LF/GPKE-Teil4-stammdatenaenderung-vom-uenb-verantwortlich-ausgehend) — LF - [View NB](/en/prozessdoku/202610/NB/GPKE-Teil4-stammdatenaenderung-vom-uenb-verantwortlich-ausgehend) — NB - [View ÜNB](/en/prozessdoku/202610/UENB/GPKE-Teil4-stammdatenaenderung-vom-uenb-verantwortlich-ausgehend) — Ü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 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: [7](#schritt-7) 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: [9](#schritt-9) 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: [7](#schritt-7), [8](#schritt-8), [9](#schritt-9)