Supplementary data on the location bundle from NBA to NBN — NBA view
Process flow from the perspective of the NB (NBA)
Process steps
supplementary data on the location bundle
NB (corresponds to NBA) NB (corresponds to NBN)START_ABR_BKSTART_ABR_NNSTART_BERECHNUNGSFORMELSTART_VERSAND_SDAECheck identifiers
- 55691 — Change of MaLo package ID · AS4
- 55126 — Bill. data BG bill. cons. MaLo · AS4
- 55672 — Bill. data BG settl. gen.. MaLo · AS4
- 55615 — Change of NeLo data · AS4
- 55616 — Change of MaLo data · AS4
- 55619 — Change of tranche data · AS4
- 55617 — Change of TR data · AS4
- 55618 — Change of SR data · AS4
- 55620 — Change of MeLo data · AS4
- 55225 — Change reactive bill. data of the NeLo · AS4
- 55218 — Bill. data NNA · AS4
- 25001 — Calculation formula · AS4
Flow
Process trigger
The backend triggers this step with one of these events.
Load data for processing
- Read balancing
GET /getAccountingBasic - Read market location
GET /getMarketLocationBasic
- Read balancing
Message to NB (corresponds to NBN) · AS4
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend once the message has been created.
- Transaction updated — Update 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 NBN — the receiving 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.