# Fault rectification at the metering location — View LF ## Process flow from the perspective of the LF \nSystem diagram: Störungsbehebung in der Messlokation — view of LF\n\n\nCustomer backend system\n\nMACO APP · LF\n\nMarket partner\n\n\n\nProcess trigger received\n\nSTART_VERSAND_STOERUN\nGSMELDUNG\n\nAPI\n\n1. Meldung einer Störung\n\n\nMSB\n\nMessage\n23001, 23001\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Antwort\n\n\nMSB\n\nMessage\n23003, 23003, 23004…\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n4. Mitteilung Ergebnis\n\n\nMSB\n\nMessage\n23008, 23008\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Störungsbehebung in der Messlokation — view of LF\n\n\nBackend (customer)\n\n\nMACO APP · LF\n\n\nMSB\n\n\nNB\n\n\nSTART_VERSAND_STOERUNGSMELDUNG\nTrigger event\n\n1. Meldung einer Störung\nPI 23001, 23001\n\nUpdate transaction\nUpdate process data\n\n2. Antwort\nPI 23003, 23003, 23004…\n\nUpdate transaction\nUpdate process data\n\n3. Information über Störung an Messlokation\nPI 23005\n\n4. Mitteilung Ergebnis\nPI 23008, 23008\n\nUpdate transaction\nUpdate process data\n\n5. Informationsmeldung über Behebung\nPI 23009\n"} titel="LF" /> ## Process steps ### Notification of a fault
**Check identifiers** - [23001](/en/schnittstellen/202604/pruefi/INSRPT/PI_23001) — Fault notification
**Flow**
  1. **Prozessauslöser** [`START_VERSAND_STOERUNGSMELDUNG`](/en/api/202604/ausloeser-lf/start-versand-stoerungsmeldung) \"\n ]\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_VERSAND_STOERUNGSMELDUNG\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. Message to **MSB**
  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
**Check identifiers** - [23003](/en/schnittstellen/202604/pruefi/INSRPT/PI_23003) — Rejection - [23004](/en/schnittstellen/202604/pruefi/INSRPT/PI_23004) — Confirmation
**Flow**
  1. Message from **MSB**
  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.
### Information about fault at metering location This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [23005](/en/schnittstellen/202604/pruefi/INSRPT/PI_23005) — Information notification
### Result notification
**Check identifiers** - [23008](/en/schnittstellen/202604/pruefi/INSRPT/PI_23008) — Result report
**Flow**
  1. Message from **MSB**
  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.
### Information notification on rectification This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [23009](/en/schnittstellen/202604/pruefi/INSRPT/PI_23009) — Information notification
## Process information
  1. ### First message The party involved on this page is itself the sender of: „Report of a fault“ to **MSB** (step 1).
## 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/awh-wim-gas-2-0-storungsbehebung-in-der-messlokation) — NB - [View MSB](/en/prozessdoku/202604/MSB/awh-wim-gas-2-0-storungsbehebung-in-der-messlokation) — MSB *The source provides no use case profile for this process — objective, precondition and result are not recorded there.* *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.* :::caution{title="Step sequence reconstructed"} For this process, the BNetzA consolidated version carries no sequence diagram. The steps are reconstructed from the BDEW check identifier table: grouped by the designation, ordered by the process step. The method agrees with the consolidated version in 200 of 200 cases that can be cross-checked — the individual line is nevertheless not editorially reviewed. Check it against the rulebook before adopting it into an implementation specification. ::: 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: [2](#schritt-2), [4](#schritt-4)