System diagram: Übermittlung Prüfmitteilung für die Bilanzierungsgebietssummenzeitreihe an ÜNB

# Transmission of validation notification for the balancing area aggregate time series to ÜNB — NB view The NB checks an available version of the BG-SZR (category B) and transmits the corresponding validation notification to the BIKO. In doing so, the NB can indicate to the ÜNB by means of a negative validation notification, even beyond the end of the clearing deadline of the BKA (without KBKA), that it considers the data used for the BKA (without KBKA) to be in need of correction and therefore expects the transmission of corrected data for the KBKA. A positive validation notification from the NB for a version of the BG-SZR (category B) that is received by the BIKO after the clearing deadline of the BKA (without KBKA) has expired is passed on to the ÜNB and the data status is set to “billing data KBKA”. A negative validation notification from the NB for a version of the BG-SZR (category B) that is received by the BIKO after the clearing deadline of the BKA (without KBKA) has expired is passed on to the ÜNB but does not cause any change to the existing data status. The BIKO forwards the validation notification to the ÜNB, provided it is not rejected because the clearing deadline of the KBKA has been exceeded. ## Process flow from the perspective of the NB \nSystem diagram: Übermittlung Prüfmitteilung für die Bilanzierungsgebietssummenzeitreihe an ÜNB — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\n1. Prüfmitteilung BG-SZR\n(Kategorie B)\n\nBIKO\n\nAS4\n21005\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Abweisung der\nPrüfmitteilung BG-SZR\n(Kategorie B)\n\n\nBIKO\n\nAS4\n21004\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={""} titel="NB" /> ## Process steps ### Validation notification BG-SZR (category B)

**Check identifiers** - [21005](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21005) — Status message · AS4

**Flow**

Message to **BIKO** · AS4
**Response per decision tree** - `21005` → [E_0062](/en/referenz/202604/ebd/E_0062) · NB · Check BG-SZR (category B)
**Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.

### Refusal of the validation notification BG-SZR (category B)

**Check identifiers** - [21004](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21004) — Status message · AS4

**Flow**

Message from **BIKO** · AS4
**Response per decision tree** - `21004` → [E_0019](/en/referenz/202604/ebd/E_0019) · BIKO · Check validation notification
**Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend with the data of the incoming message.

### Forwarding of validation notification BG-SZR (category B) This step runs between other market partners and is not relevant for this view.

**Check identifiers** - [21003](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21003) — Status message · AS4

**Response per decision tree** - `21003` → [E_0062](/en/referenz/202604/ebd/E_0062) · NB · Check BG-SZR (category B)

Decision trees of this process

| EBD | Name | |---|---| | [E_0019](/referenz/202604/ebd/E_0019) | Check validation notification | | [E_0062](/referenz/202604/ebd/E_0062) | Check BG-SZR (category B) |

## Process information Wording of the consolidated version, profile ch. 9.8.1, pp. 114–115.

### Preconditions - The ÜNB has formed the BG-SZR (category B) and transmitted it successfully to the BIKO. - The BIKO has forwarded the BG-SZR (category B) along the chain to the NB.
### Results - On receipt of a negative validation notification, the ÜNB transmits a corrected BG-SZR (category B) where applicable. - The BIKO can form the data status and transmit it to the NB and ÜNB.
### First message The party involved on this page is itself the sender of: „Validation notification BG-SZR (category B)“ to **BIKO** (step 1).
### Objective - The NB has checked the BG-SZR (category B) against its data and has transmitted its check result to the BIKO. - The BIKO has forwarded this to the ÜNB. - The ÜNB knows the expectation (need for correction or acceptance) of the NB for the BG-SZR (category B) of the time period under consideration.

## 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 BIKO](/en/prozessdoku/202604/BIKO/MaBiS-uebermittlung-pruefmitteilung-fuer-die-bilanzierungsgebietssummenzeitreihe-an-uenb) — BIKO - [View ÜNB](/en/prozessdoku/202604/UENB/MaBiS-uebermittlung-pruefmitteilung-fuer-die-bilanzierungsgebietssummenzeitreihe-an-uenb) — ÜNB · market role UENB *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.* The source does not yet name the event that triggers these steps. Applies to: [1](#schritt-1) The connector table lists no write call for these steps. Derived from the process flow: the own role was already involved in this process, so the transaction already exists. Applies to: [2](#schritt-2) For the check identifiers of these steps there is no test case in the test data set; the »Try it out« button of the write interface therefore offers no body. Applies to: [1](#schritt-1), [2](#schritt-2)