# Transmission of the energy and power values measured so far — LF view ## Process flow from the perspective of the LF \nSystem diagram: Übermittlung der bisher gemessenen Arbeits- und Leistungswerte — view of LF\n\n\nCustomer backend system\n\nMACO APP · LF\n\nMarket partner\n\n\n\n1. Bisher gemessene\nArbeits- und Leistungswerte\n\nNB\n\nAS4\n13009\n\nAPERAK check: Z10, Z18,\nZ27, Z33\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Übermittlung der bisher gemessenen Arbeits- und Leistungswerte — view of LF\n\n\nBackend (customer)\n\n\nMACO APP · LF\n\n\nNB\n\n\n1. Bisher gemessene Arbeits- und Leistungswerte\nAS4 · PI 13009\n\nCreate transaction\nCreate process data\n"} titel="LF" /> ## Process steps ### Energy and demand values measured so far
**Check identifiers** - [13009](/en/schnittstellen/202604/pruefi/MSCONS/PI_13009) — Energy quantity (gas) · AS4
**Flow**
  1. Message from **NB** · AS4
  2. **APERAK checks** - `13009` → `Z10` — APERAK check: Is location known ? - `13009` → `Z18` - `13009` → `Z27` - `13009` → `Z33` — APERAK check: Is referenced message known ?
  3. **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.
## Process information
  1. ### First message **NB** sends “Previously measured energy and demand values” (step 1). From here on, it is the turn of the party involved on this page.
## 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/geli-gas-2-0-ubermittlung-der-bisher-gemessenen-arbeits-und-leistungswerte) — NB *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. :::