# Location bundle structure and DB from NBA to NBN — NBN view ## Process flow from the perspective of the NB (NBN) \nSystem diagram: Lokationsbündelstruktur und DB von NBA an NBN — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB (entspricht…\n\nMarket partner\n\n\n\n1. Lokationsbündelstruktur\nund DB\n\nNB (entspricht NBA)\n\nAS4\n55690\n\nAPERAK check: Z10, Z16\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Lokationsbündelstruktur und DB von NBA an NBN — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB (entspricht…\n\n\nNB (entspricht NBA)\n\n\n1. Lokationsbündelstruktur und DB\nAS4 · PI 55690\n\nCreate transaction\nCreate process data\n"} titel="NBN" /> ## Process steps ### Location bundle structure and DB
**Check identifiers** - [55690](/en/schnittstellen/202610/pruefi/UTILMD/PI_55690) — Location bundle structure and DB · AS4
**Flow**
  1. Message from **NB (corresponds to NBA)** · AS4
  2. **APERAK checks** - `55690` → `Z10` - `55690` → `Z16`
  3. **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 **NB (corresponds to NBA)** sends “Location bundle structure and DB” (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/awh-netzbetreiberwechsel-lokationsbundelstruktur-und-db-von-nba-an-nbn) — 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. ::: 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: [1](#schritt-1)