# Master data change initiated by LF (responsible) — View LF 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 LF \nSystem diagram: Stammdatenänderung vom LF (verantwortlich) ausgehend — view of LF\n\n\nCustomer backend system\n\nMACO APP · LF\n\nMarket partner\n\n\n\nProcess trigger received\n\nSTART_VERSAND_SDAE\n\nAPI\n\n1. Änderung vom LF an NB\n\n\nNB\n\nAS4\n55109, 55230, 55693\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Rückmeldung auf\nÄnderung\n\n\nNB\n\nAS4\n55137, 55232, 55694\n\nLoad data for the incoming\ncheck\n\n\n3 read APIs called\n\nAPI\nlisted at the step\n\nAPERAK check: Z10, Z44,\nZ33\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\nPI 55137, 55232\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nLoad data for the check\n\n\n4 read APIs called\n\nAPI\nlisted at the step\n\nEBD check: E_0629, E_0588\nE_0629 — Rückmeldung auf\nÄnderung prüfen (Basiert auf\nEBD: E_0626_Rückmeldung\nauf Änderung prüfen)\nE_0588 — Bestellung zur\nStammdatenänderung prüfen\n(Basiert auf EBD:\nE_0573_Bestellung zur\nStammdatenänderung\nprüfen)\n\n\nTrigger follow-up process:\n21047\n\n\nTriggered by incoming\nmessage: 55136, 55137,\n55232, 55694\n\n\n3. Bearbeitungsstand zur\nRückmeldung\n\n\nNB\n\nAS4\n21047\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nProcess trigger received\n\n\nSTART_VERSAND_SDAE\n\nAPI\n\n4. Änderung vom LF an MSB\n\n\nMSB\n\nAS4\n55110\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n5. Rückmeldung auf\nÄnderung\n\n\nMSB\n\nAS4\n55136\n\nLoad data for the incoming\ncheck\n\n\nMarktlokation lesen\n\nAPI\n\nAPERAK check: Z10, Z17,\nZ33\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nLoad data for the check\n\n\n5 read APIs called\n\nAPI\nlisted at the step\n\nEBD check: E_0630, E_0589\nE_0630 — Rückmeldung auf\nÄnderung prüfen (Basiert auf\nEBD: E_0626_Rückmeldung\nauf Änderung prüfen)\nE_0589 — Bestellung zur\nStammdatenänderung prüfen\n(Basiert auf EBD:\nE_0573_Bestellung zur\nStammdatenänderung\nprüfen)\n\n\nTrigger follow-up process:\n21047\n\n\nTriggered by incoming\nmessage: 55136, 55137,\n55232, 55694\n\n\n6. Bearbeitungsstand zur\nRückmeldung\n\n\nMSB\n\nAS4\n21047\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n8. Änderung vom LF an ÜNB\n\n\nÜNB\n\nMessage\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n9. Rückmeldung auf\nÄnderung\n\n\nÜNB\n\nMessage\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n10. 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 LF (verantwortlich) ausgehend — view of LF\n\n\nBackend (customer)\n\n\nMACO APP · LF\n\n\nNB\n\n\nMSB\n\n\nÜNB\n\n\nSTART_VERSAND_SDAE\nTrigger event\n\n1. Änderung vom LF an NB\nAS4 · PI 55109, 55230, 55693\n\nUpdate transaction\nUpdate process data\n\n2. Rückmeldung auf Änderung\nAS4 · PI 55137, 55232, 55694 · E_0410\nE_0410 — Änderung vom LF prüfen\n\nCreate transaction\nCreate process data · PI 55137, 55232\n\nUpdate transaction\nUpdate process data\n\n3. Bearbeitungsstand zur Rückmeldung\nAS4 · PI 21047 · E_0629\nE_0629 — Rückmeldung auf Änderung prüfen\n\nUpdate transaction\nUpdate process data\n\nSTART_VERSAND_SDAE\nTrigger event\n\n4. Änderung vom LF an MSB\nAS4 · PI 55110\n\nUpdate transaction\nUpdate process data\n\n5. Rückmeldung auf Änderung\nAS4 · PI 55136 · E_0578\nE_0578 — Änderung vom LF prüfen\n\nCreate transaction\nCreate process data\n\nUpdate transaction\nUpdate process data\n\n6. Bearbeitungsstand zur Rückmeldung\nAS4 · PI 21047 · E_0630\nE_0630 — Rückmeldung auf Änderung prüfen\n\nUpdate transaction\nUpdate process data\n\n8. Änderung vom LF an ÜNB\n\nUpdate transaction\nUpdate process data\n\n9. Rückmeldung auf Änderung\n\nUpdate transaction\nUpdate process data\n\n10. Bearbeitungsstand zur Rückmeldung\n\nUpdate transaction\nUpdate process data\n"} titel="LF" /> ## Process steps ### Change from the LF to NB
**Check identifiers** - [55109](/en/schnittstellen/202604/pruefi/UTILMD/PI_55109) — Change data of the MaLo · AS4 - [55230](/en/schnittstellen/202604/pruefi/UTILMD/PI_55230) — Change reactive bill. data of the NeLo · AS4 - `55693` — Change of data of the TR · AS4
**Flow**
  1. **Prozessauslöser** [`START_VERSAND_SDAE`](/en/api/202604/ausloeser-lf/start-versand-sdae) \"\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"marktrolle\": \"\",\n \"rollencodenummer\": \"\"\n },\n \"gueltigAb\": \"\",\n \"kategorie\": \"\",\n \"sparte\": \"\",\n \"transaktionsgrund\": \"\",\n \"transaktionsgrundergaenzung\": \"\",\n \"vertragsbeginn\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_VERSAND_SDAE\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. Message to **NB** · AS4
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-lf/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Response message on change
**Check identifiers** - [55137](/en/schnittstellen/202604/pruefi/UTILMD/PI_55137) — Response message/request data of the MaLo · AS4 - [55232](/en/schnittstellen/202604/pruefi/UTILMD/PI_55232) — Response message/request reactive bill. data of the NeLo · AS4 - `55694` — Response message/ request data of the TR · AS4
**Flow**
  1. Message from **NB** · AS4
    **Response per decision tree** - `55137`, `55232`, `55694` → [E_0410](/en/referenz/202604/ebd/E_0410) · NB · Check change from the LF (Based on EBD: E_0408_Check change from the NB)
  2. **Load data for the incoming check** - [Read market location](/en/api/202604/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it - [Read grid location](/en/api/202604/backend-lesen/getgridlocationbasic#netzlokation-lesen) `GET /getGridLocationBasic` Try it - [Read technical resource](/en/api/202604/backend-lesen/gettechnicalresourcebasic#technische-ressource-lesen) `GET /getTechnicalResourceBasic` Try it
  3. **APERAK checks** - `55137`, `55232`, `55694` → `Z10` — APERAK check: Is location known ? - `55137` → `Z44` — APERAK check: Does object property match? - `55137`, `55232`, `55694` → `Z33` — APERAK check: Is referenced message known ?
  4. **Write endpoint** - `55137`, `55232` → Transaction created — [Create process data](/en/api/202604/backend-schreiben-lf/createprocessdata#prozessdaten-erstellen) `POST /createProcessData` Try it out Creates a new transaction in the backend with the data of the incoming message.
  5. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/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.
  6. **Load data for the check** - [Read market location](/en/api/202604/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it - [Read grid usage contract](/en/api/202604/backend-lesen/getgridusagecontractbasic#netznutzungsvertrag-lesen) `GET /getGridUsageContractBasic` Try it - `LESEN_VERWENDUNGSZEITRAUM_BASIS` - [Read grid location](/en/api/202604/backend-lesen/getgridlocationbasic#netzlokation-lesen) `GET /getGridLocationBasic` Try it
  7. **Decision tree** - `55137`, `55232`, `55694` → [E_0629](/en/referenz/202604/ebd/E_0629) — Check response message to the change (Based on EBD: E_0626_Check response message to the change) - `55137`, `55232`, `55694` → [E_0588](/en/referenz/202604/ebd/E_0588) — Check order placement for master data change (Based on EBD: E_0573_Check order placement for master data change)
  8. **Trigger follow-up process** - [21047](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21047) — Processing status message After processing, the MACO APP starts this follow-up process itself.
### Processing status of the response message
**Check identifiers** - [21047](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21047) — Processing status message · AS4
**Flow**
  1. **Triggered by incoming message** - [55136](/en/schnittstellen/202604/pruefi/UTILMD/PI_55136) — Response message/request data of the MaLo - [55137](/en/schnittstellen/202604/pruefi/UTILMD/PI_55137) — Response message/request data of the MaLo - [55232](/en/schnittstellen/202604/pruefi/UTILMD/PI_55232) — Response message/request reactive bill. data of the NeLo - `55694` — Response message/ request data of the TR The MACO APP sends this message itself, as a follow-up process after one of these incoming messages.
  2. Message to **NB** · AS4
    **Response per decision tree** - `21047` → [E_0629](/en/referenz/202604/ebd/E_0629) · LF · Check response message to the change (Based on EBD: E_0626_Check response message to the change)
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-lf/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Change from the LF to MSB
**Check identifiers** - [55110](/en/schnittstellen/202604/pruefi/UTILMD/PI_55110) — Change data of the MaLo · AS4
**Flow**
  1. **Prozessauslöser** [`START_VERSAND_SDAE`](/en/api/202604/ausloeser-lf/start-versand-sdae) \"\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"marktrolle\": \"\",\n \"rollencodenummer\": \"\"\n },\n \"gueltigAb\": \"\",\n \"kategorie\": \"\",\n \"sparte\": \"\",\n \"transaktionsgrund\": \"\",\n \"transaktionsgrundergaenzung\": \"\",\n \"vertragsbeginn\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_VERSAND_SDAE\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. Message to **MSB** · AS4
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-lf/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Response message on change
**Check identifiers** - [55136](/en/schnittstellen/202604/pruefi/UTILMD/PI_55136) — Response message/request data of the MaLo · AS4
**Flow**
  1. Message from **MSB** · AS4
    **Response per decision tree** - `55136` → [E_0578](/en/referenz/202604/ebd/E_0578) · MSB · Check change from the LF (Based on EBD: E_0408_Check change from the NB)
  2. **Load data for the incoming check** - [Read market location](/en/api/202604/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it
  3. **APERAK checks** - `55136` → `Z10` — APERAK check: Is location known ? - `55136` → `Z17` - `55136` → `Z33` — APERAK check: Is referenced message known ?
  4. **Write endpoint** - Transaction created — [Create process data](/en/api/202604/backend-schreiben-lf/createprocessdata#prozessdaten-erstellen) `POST /createProcessData` Try it out Creates a new transaction in the backend with the data of the incoming message.
  5. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/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.
  6. **Load data for the check** - [Read balancing](/en/api/202604/backend-lesen/getaccountingbasic#bilanzierung-lesen) `GET /getAccountingBasic` Try it - [Read energy supply contract](/en/api/202604/backend-lesen/getenergysupplycontractbasic#energieliefervertrag-lesen) `GET /getEnergySupplyContractBasic` Try it - [Read market location](/en/api/202604/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it - [Read grid usage contract](/en/api/202604/backend-lesen/getgridusagecontractbasic#netznutzungsvertrag-lesen) `GET /getGridUsageContractBasic` Try it - `LESEN_VERWENDUNGSZEITRAUM_BASIS`
  7. **Decision tree** - `55136` → [E_0630](/en/referenz/202604/ebd/E_0630) — Check response message to the change (Based on EBD: E_0626_Check response message to the change) - `55136` → [E_0589](/en/referenz/202604/ebd/E_0589) — Check order placement for master data change (Based on EBD: E_0573_Check order placement for master data change)
  8. **Trigger follow-up process** - [21047](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21047) — Processing status message After processing, the MACO APP starts this follow-up process itself.
### Processing status of the response message
**Check identifiers** - [21047](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21047) — Processing status message · AS4
**Flow**
  1. **Triggered by incoming message** - [55136](/en/schnittstellen/202604/pruefi/UTILMD/PI_55136) — Response message/request data of the MaLo - [55137](/en/schnittstellen/202604/pruefi/UTILMD/PI_55137) — Response message/request data of the MaLo - [55232](/en/schnittstellen/202604/pruefi/UTILMD/PI_55232) — Response message/request reactive bill. data of the NeLo - `55694` — Response message/ request data of the TR The MACO APP sends this message itself, as a follow-up process after one of these incoming messages.
  2. Message to **MSB** · AS4
    **Response per decision tree** - `21047` → [E_0630](/en/referenz/202604/ebd/E_0630) · LF · Check response message to the change (Based on EBD: E_0626_Check response message to the change)
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-lf/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Change from the LF to ÜNB **Flow**
  1. Message to **ÜNB**
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-lf/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Response message on change **Flow**
  1. Message from **ÜNB**
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/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.
### Processing status of the response message **Flow**
  1. Message to **ÜNB**
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-lf/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
Decision trees of this process | EBD | Name | |---|---| | [E_0410](/referenz/202604/ebd/E_0410) | Check change from the LF (Based on EBD: E_0408_Check change from the NB) | | [E_0578](/referenz/202604/ebd/E_0578) | Check change from the LF (Based on EBD: E_0408_Check change from the NB) | | [E_0629](/referenz/202604/ebd/E_0629) | Check response message to the change (Based on EBD: E_0626_Check response message to the change) | | [E_0630](/referenz/202604/ebd/E_0630) | Check response message to the change (Based on EBD: E_0626_Check response message to the change) |
## 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/202604/LF/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/202604/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/202604/MSB--MSBA/WiM-Teil1-geraeteuebernahme)”), MSBN is also entitled to apply the SD “[Master data change originating from MSB (responsible)](/en/prozessdoku/202604/LF/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. **Runs beforehand:** [Start of replacement supply / default supply](/en/prozessdoku/202604/LF/GPKE-Teil2-beginn-der-ersatz-grundversorgung), [Case 1: LF assignment for EEG market location without DV obligation or KWKG market location without DV obligation](/en/prozessdoku/202604/LF/GPKE-Teil2-fall-1-lf-zuordnung-bei-eeg-marktlokation-ohne-dv-pflicht-bzw-kwkg-marktlokation-ohne-dv-pflicht), [Case 2: LF assignment for EEG market location with DV obligation](/en/prozessdoku/202604/LF--LFA/GPKE-Teil2-fall-2-lf-zuordnung-bei-eeg-marktlokation-mit-dv-pflicht), [Case 3: LF assignment for KWKG market location with DV obligation or non-EEG / non-KWKG market location and the market location is mapped without tranches](/en/prozessdoku/202604/LF--LFA/GPKE-Teil2-fall-3-lf-zuordnung-bei-kwkg-marktlokation-mit-dv-pflicht-bzw-nicht-eeg-nicht-kwkg-marktlokation-und-marktlokation-wird-nicht-tranchiert-abgebildet), [Case 4: LF assignment for KWKG market location with DV obligation or non-EEG / non-KWKG market location and the market location is mapped with tranches](/en/prozessdoku/202604/LF--LFA/GPKE-Teil2-fall-4-lf-zuordnung-bei-kwkg-marktlokation-mit-dv-pflicht-bzw-nicht-eeg-nicht-kwkg-marktlokation-und-marktlokation-wird-tranchiert-abgebildet), [Start of supply](/en/prozessdoku/202604/LF--LFA/GPKE-Teil2-lieferbeginn), [Creation](/en/prozessdoku/202604/LF/GPKE-Teil2-neuanlage) — these processes name the one shown here in their result.
  6. ### First message The party involved on this page is itself the sender of: „Change from the LF to NB“ to **NB** (step 1).
  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 NB](/en/prozessdoku/202604/NB/GPKE-Teil4-stammdatenaenderung-vom-lf-verantwortlich-ausgehend) — NB - [View MSB](/en/prozessdoku/202604/MSB/GPKE-Teil4-stammdatenaenderung-vom-lf-verantwortlich-ausgehend) — MSB - [View ÜNB](/en/prozessdoku/202604/UENB/GPKE-Teil4-stammdatenaenderung-vom-lf-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 numbers are those of the source; where one is missing, it is missing there.* 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: [2](#schritt-2), [5](#schritt-5) 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: [8](#schritt-8), [9](#schritt-9), [10](#schritt-10)