# Transmission of a definition of LF by LF — NB view - All MSB always receive the current metering time definitions of the LF or - all NB and MSB always receive the current switching time definitions of the LF or - all NB and MSB always receive the current power curve definitions of the LF. If a definition of the LF changes, it is transmitted to the authorised parties. ## Process flow from the perspective of the NB \nSystem diagram: Übermittlung einer Definition des LF durch den LF — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\n1. Definition des LF\n\nLF\n\nAS4\n25008, 25009\n\nAPERAK check: Z10, Z17,\nZ18\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\nLoad data for processing\n\n\n2 read APIs called\n\nAPI\nlisted at the step\n"} gesamt={"\nSequence diagram: Übermittlung einer Definition des LF durch den LF — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB\n\n\nLF\n\n\nMSB\n\n\n1. Definition des LF\nAS4 · PI 25008, 25009\n\nCreate transaction\nCreate process data\n\n2. Definition des LF\nAS4 · PI 25005, 25008, 25009\n"} titel="NB" /> ## Process steps ### Definition of the LF
**Check identifiers** - [25008](/en/schnittstellen/202610/pruefi/UTILTS/PI_25008) — Transmission of a rolled-out switching time definition · AS4 - [25009](/en/schnittstellen/202610/pruefi/UTILTS/PI_25009) — Transmission of a rolled-out power curve definition · AS4
**Flow**
  1. Message from **LF** · AS4
  2. **APERAK checks** - `25008`, `25009` → `Z10` - `25008`, `25009` → `Z17` - `25008`, `25009` → `Z18`
  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.
  4. **Load data for processing** - `LESEN_SCHALTZEITDEFINITION_BASIS` - `LESEN_LEISTUNGSKURVENDEFINITION_BASIS`
### Definition of the LF This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [25005](/en/schnittstellen/202610/pruefi/UTILTS/PI_25005) — Transmission of a rolled-out metering time period definition · AS4 - [25008](/en/schnittstellen/202610/pruefi/UTILTS/PI_25008) — Transmission of a rolled-out switching time definition · AS4 - [25009](/en/schnittstellen/202610/pruefi/UTILTS/PI_25009) — Transmission of a rolled-out power curve definition · AS4
## Process information Wording of the consolidated version, profile ch. 1.2.4.1, pp. 18–19.
  1. ### Preconditions - The - Overview of the metering time definitions of the LF or - Overview of the switching time definitions of the LF or - Overview of the power curve definition of the LF is available to the authorised parties.
  2. ### Results - In the case of the transmission of a switching time definition of LF or a power curve definition of LF: NB can trace a definition assigned to a location. - The MSB can set up a configuration for a location for which a definition is required. - In the case of the order placement of a configuration for which a definition is required: LF can carry out the use case “Order placement of a configuration from NB or LF to MSB” (e.g. for the order placement of a configuration for which a metering time period definition of LF is required).
  3. ### Further requirements - The LF transmits definitions with the highest version number for each time period. - For a time period, the definition with the highest version number is valid. - On first transmission, all definitions used are to be sent in their respective valid version. This also applies when they are rolled out for the following years for the first time. - The definition must always be specified for a complete calendar year. In the case of corrections, only the corrected definition for the entire calendar year is to be sent.
  4. ### Trigger - A definition already transmitted has changed or - a definition has been newly added to the corresponding overview or - the LF has created definitions for the following year. **Runs beforehand:** [Complaint about a definition of the LF from MSB to LF](/en/prozessdoku/202610/LF/GPKE-Teil3-reklamation-einer-definition-des-lf-vom-msb-an-lf), [Complaint about a definition of the LF from NB to LF](/en/prozessdoku/202610/NB/GPKE-Teil3-reklamation-einer-definition-des-lf-vom-nb-an-lf), [Transmission of the overview of the definitions of the LF by the LF](/en/prozessdoku/202610/NB/GPKE-Teil3-uebermittlung-der-uebersicht-der-definitionen-des-lf-durch-den-lf) — these processes name the one shown here in their result.
  5. ### First message **LF** sends “Definition of the LF” (step 1). From here on, it is the turn of the party involved on this page.
  6. ### Objective - The MSB know the metering time definitions of LF or - the NB and MSB know the switching time definitions of the LF or - the NB and MSB know the power curve definitions of the LF.
## 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 LF](/en/prozessdoku/202610/LF/GPKE-Teil3-uebermittlung-einer-definition-des-lf-durch-den-lf) — LF - [View MSB](/en/prozessdoku/202610/MSB/GPKE-Teil3-uebermittlung-einer-definition-des-lf-durch-den-lf) — MSB *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.* These read accesses are not listed in the API catalogue of this format version; the step therefore shows only their command, without address and without button. Applies to: [1](#schritt-1) 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](#schritt-1)