# Transmission of gas values to NB — View NBN ## Process flow from the perspective of the NB (NBN) \nSystem diagram: Werteübermittlung Gas an NB — view of NB\n\n\nCustomer backend system\n\nMACO APP · NBN\n\nMarket partner\n\n\n\n1. Werte Messlokation\n\nNBA\n\nAS4\n13002\n\nLoad data for the incoming\ncheck\n\n\n2 read APIs called\n\nAPI\nlisted at the step\n\nAPERAK check: MSCONS\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Werteübermittlung Gas an NB — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NBN\n\n\nNBA\n\n\n1. Werte Messlokation\nAS4 · PI 13002\n\nCreate transaction\nCreate process data\n"} titel="NBN" /> ## Process steps ### Values metering location
**Check identifiers** - [13002](/en/schnittstellen/202610/pruefi/MSCONS/PI_13002) — Meter reading (gas) · AS4
**Flow**
  1. Message from **NBA** · AS4
  2. **Load data for the incoming check** - [Read metering location](/en/api/202610/backend-lesen/getmeterlocationbasic#messlokation-lesen) `GET /getMeterLocationBasic` Try it - [Read meter](/en/api/202610/backend-lesen/getcounterbasic#zahler-lesen) `GET /getCounterBasic` Try it
  3. **APERAK checks** - `13002` → `MSCONS`
  4. **Write endpoint** - Transaction created — [Create process data](/en/api/202610/backend-schreiben-nb/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 **NBA** sends “Values of the metering location” (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 NBA](/en/prozessdoku/202610/NB--NBA/leitfaden-marktprozesse-netzbetreiberwechsel-werteubermittlung-gas-an-nb) — the transferring grid operator · market role 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. :::