# Start of supply — LFZ view A LFN registers an assignment of the LFN to a market location or tranche with the NB. In the course of the process - the NB terminates, where applicable, the assignment of the LFA to the market location or tranche. - the NB cancels, where applicable, the assignment of the LFZ to the market location or tranche. ## Process flow from the perspective of the LF (LFZ) \nSystem diagram: Lieferbeginn — view of LF\n\n\nCustomer backend system\n\nMACO APP · LFZ\n\nMarket partner\n\n\n\n13. Aufhebung der\nZuordnung des LFZ zur\nMarklokation bzw. Tranc…\n\nNB\n\nAS4\n55038\n\nLoad data for the incoming\ncheck\n\n\n2 read APIs called\n\nAPI\nlisted at the step\n\nAPERAK check: Z10, Z44\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Lieferbeginn — view of LF\n\n\nBackend (customer)\n\n\nMACO APP · LFZ\n\n\nLFN\n\n\nNB\n\n\nLFA\n\n\n1. Anmeldung einer Zuordnung des LFN zur Marktlo…\nAS4 · PI 55001, 55077\n\n2. Information über existierende Zuordnung\nAS4 · PI 55036\n\n3. Anfrage zur Beendigung der Zuordnung des LFA…\nAS4 · PI 55010\n\n4. Antwort auf Anfrage zur Beendigung der Zuordn…\nAS4 · PI 55011, 55012 · E_0624\nE_0624 — Anfrage zur Beendigung der Zuordnung prüfen\n\n5. Zuordnung des LFN zur Marktlokation bzw. Tran…\nAS4 · PI 55002, 55078 · E_0623\nE_0623 — Lieferbeginn prüfen\n\n6. Ablehnung der Anmeldung einer Zuordnung des L…\nAS4 · PI 55003, 55080 · E_0622, E_0623\nE_0622 — Prüfen, ob Anmeldung direkt ablehnbar\nE_0623 — Lieferbeginn prüfen\n\n10. Beendigung der Zuordnung des LFA zur Marktlok…\nAS4 · PI 55037\n\n13. Aufhebung der Zuordnung des LFZ zur Marklokat…\nAS4 · PI 55038\n\nCreate transaction\nCreate process data\n"} titel="LFZ" /> ## Process steps ### Registration of an assignment of the LFN to the market location or tranche This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [55001](/en/schnittstellen/202604/pruefi/UTILMD/PI_55001) — Registration cons. MaLo · AS4 - [55077](/en/schnittstellen/202604/pruefi/UTILMD/PI_55077) — Registration gen. MaLo · AS4
### Information about existing assignment This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [55036](/en/schnittstellen/202604/pruefi/UTILMD/PI_55036) — Existing assignment · AS4
### Request for termination of the assignment of the LFA to the market location or tranche This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [55010](/en/schnittstellen/202604/pruefi/UTILMD/PI_55010) — Request for termination of the assignment · AS4
### Response to request for termination of the assignment of the LFA to the market location or tranche This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [55011](/en/schnittstellen/202604/pruefi/UTILMD/PI_55011) — Confirmation termination of the assignment · AS4 - [55012](/en/schnittstellen/202604/pruefi/UTILMD/PI_55012) — Rejection termination of the assignment · AS4
**Response per decision tree** - `55011`, `55012` → [E_0624](/en/referenz/202604/ebd/E_0624) · LF · Check request for termination of the assignment
### Assignment of the LFN to the market location or tranche This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [55002](/en/schnittstellen/202604/pruefi/UTILMD/PI_55002) — Confirmation registration cons. MaLo · AS4 - [55078](/en/schnittstellen/202604/pruefi/UTILMD/PI_55078) — Confirmation registration gen. MaLo · AS4
**Response per decision tree** - `55002`, `55078` → [E_0623](/en/referenz/202604/ebd/E_0623) · NB · Check start of supply
### Rejection of the registration of an assignment of the LFN to the market location or tranche This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [55003](/en/schnittstellen/202604/pruefi/UTILMD/PI_55003) — Rejection registration cons. MaLo · AS4 - [55080](/en/schnittstellen/202604/pruefi/UTILMD/PI_55080) — Rejection registration gen. MaLo · AS4
**Response per decision tree** - `55003`, `55080` → [E_0622](/en/referenz/202604/ebd/E_0622) · NB · Check whether the registration can be rejected directly - `55003`, `55080` → [E_0623](/en/referenz/202604/ebd/E_0623) · NB · Check start of supply
### Termination of the assignment of the LFA to the market location or tranche This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [55037](/en/schnittstellen/202604/pruefi/UTILMD/PI_55037) — Termination of the assignment · AS4
### Cancellation of the assignment of the LFZ to the market location or tranche
**Check identifiers** - [55038](/en/schnittstellen/202604/pruefi/UTILMD/PI_55038) — Cancellation of a fut. assignment · AS4
**Flow**
  1. Message from **NB** · AS4
  2. **Load data for the incoming check** - [Read market location](/en/api/202604/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it - [Read tranche](/en/api/202604/backend-lesen/gettranchebasic#tranche-lesen) `GET /getTrancheBasic` Try it
  3. **APERAK checks** - `55038` → `Z10` — APERAK check: Is location known ? - `55038` → `Z44` — APERAK check: Does object property match?
  4. **Write endpoint** - Transaction created — [Create process data](/en/api/202604/backend-schreiben-lf/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 the other parties involved | EBD | Name | |---|---| | [E_0622](/referenz/202604/ebd/E_0622) | Check whether the registration can be rejected directly | | [E_0623](/referenz/202604/ebd/E_0623) | Check start of supply | | [E_0624](/referenz/202604/ebd/E_0624) | Check request for termination of the assignment |
## Process information Wording of the consolidated version, profile ch. 2.1.1, pp. 12–15.
  1. ### Preconditions - In the case of a consuming market location: - Conclusion of an energy supply contract between LFN and the final customer. - In the case of a generating market location or a tranche: - Conclusion of an electricity purchase agreement between LFN and the EZ. Three business transactions are considered here: - Business transaction 1: LFN is fully assigned to a market location (complete (100%) assignment). This business transaction is also to be applied for the change from a tranched market location to a non-tranched market location. - Business transaction 2: LFN is fully assigned to an existing tranche (complete (100%) assignment). This business transaction is to be applied in the case of a direct transition, i.e. a seamless allocation end and allocation start and while retaining the tranche. - Business transaction 3: LFN is assigned to a tranche to be newly formed (partial assignment procedure with formation of new tranches). In addition, a change of the tranche size assigned to LF must be reported with this process/business transaction 3. - The previous and the new EZ must be identical. - The energy of a market location that is to be assigned in full or in part to the marketing type of a DV must be measured with a quarter-hourly resolution. - The use case is not to be started by the grid operator company in its role as LF. - An allocation authorization according to the processes of MaBiS for the BK used by LFN is available to NB. - This is not the initial commissioning of a market location (creation). - The MaLo-ID of the market location is known or, in business transaction 2, the MaLo-ID of the tranche is known.
  2. ### Results - In the case of a consuming market location: - The NB executes the use cases „[Billing data grid usage settlement](/en/prozessdoku/202604/LF/GPKE-Teil2-abrechnungsdaten-netznutzungsabrechnung)“ and „[Billing data balancing group settlement](/en/prozessdoku/202604/LF/GPKE-Teil2-abrechnungsdaten-bilanzkreisabrechnung)“. - Any allocation gaps that arise are closed by NB by assigning the E/G to the market location, applying the use case „[Start of the replacement supply / default supply](/en/prozessdoku/202604/LF/GPKE-Teil2-beginn-der-ersatz-grundversorgung)“. - If the market location is disconnected, NB carries out the use case “[Restoration of grid connection use at start of supply](/en/prozessdoku/202604/MSB/GPKE-Teil2-wiederherstellung-der-anschlussnutzung-bei-lieferbeginn)”. - In the case of a generating market location or a tranche: - The NB executes the use case „[Billing data balancing group settlement](/en/prozessdoku/202604/LF/GPKE-Teil2-abrechnungsdaten-bilanzkreisabrechnung)“. - Any allocation gaps that arise are closed by NB within the use case „Establishing a 100% LF assignment to a generating market location“. - The NB carries out the use case „Master data change“ (here: SD „[Master data change initiated by the NB (responsible)](/en/prozessdoku/202604/LF/GPKE-Teil4-stammdatenaenderung-vom-nb-verantwortlich-ausgehend)“) (GPKE part 4). - The NB sends the calculation formula to the LFN. - The NB executes the use case „[Set-up of the configurations due to an assignment of a LF to a market location or tranche](/en/prozessdoku/202604/MSB/GPKE-Teil3-einrichtung-der-konfigurationen-aufgrund-einer-zuordnung-eines-lf-zu-einer-marktlokation-bzw-tranche)“ (GPKE part 3). - The LFN carries out the use case „Master data change“ (here: SD „[Master data change initiated by the LF (responsible)](/en/prozessdoku/202604/LF/GPKE-Teil4-stammdatenaenderung-vom-lf-verantwortlich-ausgehend)“) (GPKE part 4).
  3. ### Error case #### Result in the error case - The LFN has not been assigned to the market location or tranche. - The LFA remains assigned to the market location or tranche, provided that its assignment has not already been ended as part of another use case (e.g. „End of supply from LF to NB). - In the case of a consuming market location: NB carries out the use case “[Start of replacement supply / default supply](/en/prozessdoku/202604/LF/GPKE-Teil2-beginn-der-ersatz-grundversorgung)” if necessary. - In the case of a generating market location or a tranche: NB carries out the use case “Establishing a 100% LF assignment to a generating market location” if necessary. - If required, the LFN sends a registration to the NB again. #### Error cases - This is the initial commissioning of a market location (creation). - In the case of a generating market location or a tranche: - The previous and the new EZ are not identical. - The energy of a market location that is to be assigned in full or in part to the marketing type of a DV cannot be measured with a quarter-hourly resolution. - The use case is started by the grid operator company in its role as LF. - An allocation authorization according to the processes of MaBiS for the BK used by LFN is not available to NB.
  4. ### Further requirements - Gaps in assignment must be avoided by coordinating registration and deregistration in time. - Note: A change of generator at a generating market location or a change of plant operator at a technical resource is not handled within the processes described here. Their bilateral handling between NB and EZ takes place in accordance with the relevant provisions of NB. - Note: The assignment of LF to the market location or tranche when a market location is commissioned (creation) takes place via the use case “[Creation](/en/prozessdoku/202604/LF/GPKE-Teil2-neuanlage)”, “[Start of replacement supply / default supply](/en/prozessdoku/202604/LF/GPKE-Teil2-beginn-der-ersatz-grundversorgung)” or “Establishing a 100% LF assignment to a generating market location”. - Note: If the device technology available at the allocation start does not permit the registration, a corresponding change of the device technology must be arranged by LFN, the final customer or the EZ with MSB. LFN can commission the change of the device technology via the WiM use case for the metering location change (WiM Part 1). - Note on generating market locations and on tranches: for a change of the marketing type (without a simultaneous assignment of LF to the generating market location or to the tranche), LF applies the use case "Order placement of a change of billing data".
  5. ### Trigger - In the case of a consuming market location: - Supplier switch without simultaneous move-in of the final customer - Supplier switch with simultaneous move-in of the final customer - Assignment of the previous LF without simultaneous move-in of the final consumer (after a termination of the assignment of LF to the market location, e.g. due to the use case "End of supply from LF to NB") - Assignment of the previous LF with simultaneous move-in of the final consumer. - In the case of a generating market location or a tranche: - Supplier switch without change of generator - Assignment of the previous LF without a change of producer (after a termination of the assignment of LF to the market location or tranche, e.g. due to the use case "End of supply from LF to NB"). **Runs beforehand:** [Billing data for grid usage settlement](/en/prozessdoku/202604/LF/GPKE-Teil2-abrechnungsdaten-netznutzungsabrechnung), [Determination of the MaLo ID of the market location](/en/prozessdoku/202604/LF/GPKE-Teil2-ermittlung-der-malo-id-der-marktlokation), [Creation](/en/prozessdoku/202604/LF/GPKE-Teil2-neuanlage) — these processes name the one shown here in their result.
  6. ### First message **NB** sends “Revocation of the assignment of the LFZ to the market location or tranche” (step 13). From here on, the party involved on this page has the next move.
  7. ### Objective The LFN is assigned to the market location or tranche.
## 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 LFA](/en/prozessdoku/202604/LF--LFA/GPKE-Teil2-lieferbeginn) — the transferring supplier · market role LF - [View LFN](/en/prozessdoku/202604/LF--LFN/GPKE-Teil2-lieferbeginn) — the receiving supplier · market role LF - [View NB](/en/prozessdoku/202604/NB/GPKE-Teil2-lieferbeginn) — NB *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 numbers are those of the source; where one is missing, it is missing there.*