# Transmission of data status for the monthly curtailed energy transfer time series (AAÜZ) — ANB 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 NB (ANB) \nSystem diagram: Übermittlung Datenstatus für die monatliche Ausfallarbeitsüberführungszeitreihe (AAÜZ) — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB (ANB)\n\nMarket partner\n\n\n\n2. Datenstatus für die\nmonatliche AAÜZ\n\nBIKO\n\nAS4\n21003\n\nAPERAK check: Z33\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Übermittlung Datenstatus für die monatliche Ausfallarbeitsüberführungszeitreihe (AAÜZ) — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB (ANB)\n\n\nBIKO\n\n\nBKV (des LF)\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\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\nCreate transaction\nCreate process data\n"} titel="ANB" /> ## Process steps ### Data status for the monthly AAÜZ This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [21004](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21004) — Status message · 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
### Data status for the monthly AAÜZ
**Check identifiers** - [21003](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21003) — Status message · AS4
**Flow**
  1. Message from **BIKO** · 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. **APERAK checks** - `21003` → `Z33`
  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.
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 **BIKO** sends “Data status for the monthly AAÜZ” (step 2). From here on, it is the turn of the party involved on this page.
  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 BIKO](/en/prozessdoku/202610/BIKO/MaBiS-uebermittlung-datenstatus-fuer-die-monatliche-ausfallarbeitsueberfuehrungszeitreihe-aauez) — BIKO - [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 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: [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: [2](#schritt-2)