Location bundle structure and DB from NBA to NBN — NBN view
Process flow from the perspective of the NB (NBN)
Process steps
Location bundle structure and DB
NB (corresponds to NBN) NB (corresponds to NBA)Z10Z16Check identifiers
- 55690 — Location bundle structure and DB · AS4
Flow
Message from NB (corresponds to NBA) · AS4
APERAK checks
55690→Z1055690→Z16
Write endpoint
- Transaction created — Create process data
POST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created — Create process data
Process information
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 — the transferring grid operator · market role NB
Notes on this page
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.
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