# Transmission of data status for the monthly curtailed energy transfer time series (AAÜZ) — BIKO view The BIKO transmits the data status to the NB and the BKV (of the LF) for the AAÜZ - after receipt of the AAÜZ from the NB or - after receipt of the validation notification from the BKV (of the LF) or - after use of the AAÜZ for the BKA (without KBKA) or the KBKA. ## Process flow from the perspective of the BIKO \nSystem diagram: Übermittlung Datenstatus für die monatliche Ausfallarbeitsüberführungszeitreihe (AAÜZ) — view of BIKO\n\n\nCustomer backend system\n\nMACO APP · BIKO\n\nMarket partner\n\n\n\n1. Datenstatus für die\nmonatliche AAÜZ\n\nBKV (des LF)\n\nAS4\n21004\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Datenstatus für die\nmonatliche AAÜZ\n\n\nNB (ANB)\n\nAS4\n21003\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Übermittlung Datenstatus für die monatliche Ausfallarbeitsüberführungszeitreihe (AAÜZ) — view of BIKO\n\n\nBackend (customer)\n\n\nMACO APP · BIKO\n\n\nBKV (des LF)\n\n\nNB (ANB)\n\n\n1. Datenstatus für die monatliche AAÜZ\nAS4 · PI 21004 · E_0075, E_0076…\nE_0075 — Datenstatus AAÜZ nach erfolgter BKA vergeben\nE_0076 — Datenstatus nach Eingang einer AAÜZ vergeben\nE_0077 — Datenstatus nach Vorliegen einer Prüfmitteilung zur AAÜZ verge…\n\nUpdate transaction\nUpdate process data\n\n2. Datenstatus für die monatliche AAÜZ\nAS4 · PI 21003 · E_0075, E_0076…\nE_0075 — Datenstatus AAÜZ nach erfolgter BKA vergeben\nE_0076 — Datenstatus nach Eingang einer AAÜZ vergeben\nE_0077 — Datenstatus nach Vorliegen einer Prüfmitteilung zur AAÜZ verge…\n\nUpdate transaction\nUpdate process data\n"} titel="BIKO" /> ## Process steps ### Data status for the monthly AAÜZ
**Check identifiers** - [21004](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21004) — Status message · AS4
**Flow**
  1. Message to **BKV (of the LF)** · AS4
    **Response per decision tree** - `21004` → [E_0075](/en/referenz/202610/ebd/E_0075) · BIKO · Assign data status AAÜZ after completed BKA - `21004` → [E_0076](/en/referenz/202610/ebd/E_0076) · BIKO · Assign data status after receipt of a AAÜZ - `21004` → [E_0077](/en/referenz/202610/ebd/E_0077) · BIKO · Assign data status once a validation notification for the AAÜZ is available
  2. **Write endpoint** - Transaction updated — `AKTUALISIEREN_PROZESSDATEN` Updates the existing transaction in the backend once the message has been created.
### Data status for the monthly AAÜZ
**Check identifiers** - [21003](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21003) — Status message · AS4
**Flow**
  1. Message to **NB (ANB)** · AS4
    **Response per decision tree** - `21003` → [E_0075](/en/referenz/202610/ebd/E_0075) · BIKO · Assign data status AAÜZ after completed BKA - `21003` → [E_0076](/en/referenz/202610/ebd/E_0076) · BIKO · Assign data status after receipt of a AAÜZ - `21003` → [E_0077](/en/referenz/202610/ebd/E_0077) · BIKO · Assign data status once a validation notification for the AAÜZ is available
  2. **Write endpoint** - Transaction updated — `AKTUALISIEREN_PROZESSDATEN` Updates the existing transaction in the backend once the message has been created.
Decision trees of this process | EBD | Name | |---|---| | [E_0075](/referenz/202610/ebd/E_0075) | Assign data status AAÜZ after completed BKA | | [E_0076](/referenz/202610/ebd/E_0076) | Assign data status after receipt of a AAÜZ | | [E_0077](/referenz/202610/ebd/E_0077) | Assign data status once a validation notification for the AAÜZ is available |
## Process information Wording of the consolidated version, profile ch. 17.3.3.5.1, pp. 262–263.
  1. ### Results All systems of BKV, BIKO and NB hold the same data status for a version of the AAÜZ.
  2. ### Error case #### Result in the error case The BIKO informs all affected market participants and, after the error has been corrected, ensures that the correct data status is assigned to all affected AAÜZ. #### Error cases The algorithm applied by the BIKO for assigning the data status is faulty.
  3. ### Further requirements The BKV (of the LF) is contacted by the NB to clarify the errors. The BKV (of the LF) can also contact the NB.
  4. ### First message The party involved on this page is itself the sender of: „Data status for the monthly AAÜZ“ to **BKV (of the LF)** (step 1).
  5. ### Objective The data status managed by the BIKO is available at the NB, at the BKV (of the LF) for the AAÜZ.
## 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 ANB](/en/prozessdoku/202610/NB/MaBiS-uebermittlung-datenstatus-fuer-die-monatliche-ausfallarbeitsueberfuehrungszeitreihe-aauez) — connecting grid operator · market role NB - [View BKV-LF](/en/prozessdoku/202610/BKV/MaBiS-uebermittlung-datenstatus-fuer-die-monatliche-ausfallarbeitsueberfuehrungszeitreihe-aauez) — balance responsible party of the supplier · market role BKV *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), [2](#schritt-2) For this market role there is no write catalog; the step therefore shows only the command of the write call, without address and without button. Applies to: [1](#schritt-1), [2](#schritt-2)