# Creation — LF view A LF registers an assignment of the LF to a market location or tranche with the NB. ## Process flow from the perspective of the LF \nSystem diagram: Neuanlage — view of LF\n\n\nCustomer backend system\n\nMACO APP · LF\n\nMarket partner\n\n\n\nProcess trigger received\n\nSTART_LIEFERBEGINN\n\nAPI\n\n1. Anmeldung einer\nZuordnung des LF zur\nMarktlokation bzw. Tra…\n\n\nNB\n\nAS4\n55600, 55601\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Zuordnung des LF zur\nMarktlokation bzw. Tranche\n\n\nNB\n\nAS4\n55602, 55603\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n3. Ablehnung der Anmeldung\neiner Zuordnung des LF zur\nMarktlok…\n\n\nNB\n\nAS4\n55604, 55605\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Neuanlage — view of LF\n\n\nBackend (customer)\n\n\nMACO APP · LF\n\n\nNB\n\n\nSTART_LIEFERBEGINN\nTrigger event\n\n1. Anmeldung einer Zuordnung des LF zur Marktlok…\nAS4 · PI 55600, 55601\n\nUpdate transaction\nUpdate process data\n\n2. Zuordnung des LF zur Marktlokation bzw. Tranc…\nAS4 · PI 55602, 55603 · E_0608\nE_0608 — Anmeldung einer Zuordnung\n\nUpdate transaction\nUpdate process data\n\n3. Ablehnung der Anmeldung einer Zuordnung des L…\nAS4 · PI 55604, 55605 · E_0608\nE_0608 — Anmeldung einer Zuordnung\n\nUpdate transaction\nUpdate process data\n"} titel="LF" /> ## Process steps ### Registration of an assignment of the LF to the market location or tranche
**Check identifiers** - [55600](/en/schnittstellen/202610/pruefi/UTILMD/PI_55600) — Registration of new cons. MaLo · AS4 - [55601](/en/schnittstellen/202610/pruefi/UTILMD/PI_55601) — Registration of new gen. MaLo · AS4
**Flow**
  1. **Prozessauslöser** [`START_LIEFERBEGINN`](/en/api/202610/ausloeser-lf/start-lieferbeginn) \"\n ]\n }\n ],\n \"ENERGIELIEFERVERTRAG\": [\n {\n \"korrespondenzpartner\": {\n \"name1\": \"\"\n },\n \"vertragskonditionen\": {\n \"abrechnungsintervall\": \"\"\n },\n \"vertragspartner2\": [\n \"\"\n ]\n }\n ],\n \"MESSLOKATION\": [\n {\n \"ablesekartenempfaenger\": {\n \"name1\": \"\"\n }\n }\n ],\n \"NETZNUTZUNGSVERTRAG\": [\n {\n \"gemeinderabatt\": null,\n \"vertragskonditionen\": {\n \"haushaltskunde\": \"\",\n \"netznutzungsvertrag\": \"\",\n \"netznutzungszahler\": \"\"\n }\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"marktrolle\": \"\",\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"sparte\": \"\",\n \"transaktionsgrund\": \"\",\n \"transaktionsgrundergaenzung\": \"\",\n \"vertragsbeginn\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_LIEFERBEGINN\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. Message to **NB** · AS4
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-lf/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Assignment of the LF to the market location or tranche
**Check identifiers** - [55602](/en/schnittstellen/202610/pruefi/UTILMD/PI_55602) — Confirmation registration of new cons. MaLo · AS4 - [55603](/en/schnittstellen/202610/pruefi/UTILMD/PI_55603) — Confirmation registration of new gen. MaLo · AS4
**Flow**
  1. Message from **NB** · AS4
    **Response per decision tree** - `55602`, `55603` → [E_0608](/en/referenz/202610/ebd/E_0608) · NB · Registration of an assignment
  2. **APERAK checks** - `55602`, `55603` → `Z33` — APERAK check: Is referenced message known ?
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-lf/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend with the data of the incoming message.
### Rejection of the registration of an assignment of the LF to the market location or tranche
**Check identifiers** - [55604](/en/schnittstellen/202610/pruefi/UTILMD/PI_55604) — Rejection registration of new cons. MaLo · AS4 - [55605](/en/schnittstellen/202610/pruefi/UTILMD/PI_55605) — Rejection registration of new gen. MaLo · AS4
**Flow**
  1. Message from **NB** · AS4
    **Response per decision tree** - `55604`, `55605` → [E_0608](/en/referenz/202610/ebd/E_0608) · NB · Registration of an assignment
  2. **APERAK checks** - `55604`, `55605` → `Z33` — APERAK check: Is referenced message known ?
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-lf/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend with the data of the incoming message.
Decision trees of this process | EBD | Name | |---|---| | [E_0608](/referenz/202610/ebd/E_0608) | Registration of an assignment |
## Process information Wording of the consolidated version, profile ch. 2.2.1, pp. 25–27.
  1. ### Preconditions - In the case of a consuming market location: Conclusion of an energy supply contract between LF and the final customer. - In the case of a generating market location or a tranche: - Conclusion of an electricity purchase agreement between LF and the EZ. Two business transactions are considered here: - Business transaction A: LF is fully assigned to a market location. - Business transaction B: LF is assigned to a tranche (according to the requested tranche size). - 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. - This is the initial commissioning of a market location (creation). This means - in the case of a consuming market location or in the case of business transaction A: A LF is not yet assigned to the newly created market location. - in the case of business transaction B: A 100% LF assignment to the newly created market location has not yet been established. - An allocation authorization according to the processes of MaBiS for the BK used by LF is available to NB.
  2. ### Results - In the case of a consuming market location: NB carries out the use cases “[Billing data for grid usage settlement](/en/prozessdoku/202610/LF/GPKE-Teil2-abrechnungsdaten-netznutzungsabrechnung)” and “[Billing data for balancing group settlement](/en/prozessdoku/202610/LF/GPKE-Teil2-abrechnungsdaten-bilanzkreisabrechnung)”. - In the case of a generating market location or a tranche: NB carries out the use case “[Billing data for balancing group settlement](/en/prozessdoku/202610/LF/GPKE-Teil2-abrechnungsdaten-bilanzkreisabrechnung)”. - The NB carries out the use case „Master data change“ (here: SD „[Master data change initiated by the NB (responsible)](/en/prozessdoku/202610/LF/GPKE-Teil4-stammdatenaenderung-vom-nb-verantwortlich-ausgehend)“) (GPKE part 4). - The NB sends the calculation formula to the LF. - 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/202610/MSB/GPKE-Teil3-einrichtung-der-konfigurationen-aufgrund-einer-zuordnung-eines-lf-zu-einer-marktlokation-bzw-tranche)“ (GPKE part 3). - In the case of a tranche: Any allocation gaps that arise are closed by NB within the use case “Establishing a 100% LF assignment to a generating market location”. - The LF carries out the use case „Master data change“ (here: SD „[Master data change initiated by the LF (responsible)](/en/prozessdoku/202610/LF/GPKE-Teil4-stammdatenaenderung-vom-lf-verantwortlich-ausgehend)“) (GPKE part 4).
  3. ### Error case #### Result in the error case - The LF has not been assigned to the market location or tranche. - If the market location cannot be identified: the LF enters into bilateral clearing with the final customer or the EZ. - If required, the LF restarts the use case „Creation“, or - the LF starts the use case „[Start of supply](/en/prozessdoku/202610/LF--LFA/GPKE-Teil2-lieferbeginn)“ where required, provided the LF was informed in the rejection that - in the case of a consuming market location or in the case of business transaction A, a LF is already assigned to the market location. - in the case of business transaction B, a 100% LF assignment to the market location has already been established. - In the case of a consuming market location: NB carries out the use case “[Start of replacement supply / default supply](/en/prozessdoku/202610/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. #### Error cases - This is not an initial commissioning of a market location (creation). This means - in the case of a consuming market location or in the case of business transaction A: A LF (this includes an E/G) is already assigned to the market location. - in the case of business transaction B: A 100% LF assignment to the market location has already been established (whereby a LF can also be the grid operator company in its role as LF). - The market location cannot be identified, or cannot be identified unambiguously, by the NB. - In the case of a generating market location or a tranche: - 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 LF is not available to NB.
  4. ### Further requirements - 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 LF, the final customer or the EZ with MSB. LF can commission the change of the device technology via the WiM use case for the metering location change (WiM Part 1). - Note: In the case of a generating market location or a tranche: The form set out in Annex 4 to Decision BK6-16-200 may continue to be used for clearing cases.
  5. ### First message The party involved on this page is itself the sender of: „Registration of an assignment of the LF to the market location or tranche“ to **NB** (step 1).
  6. ### Objective The LF is assigned to the market location or tranche as of the commissioning date of the market location.
## 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 NB](/en/prozessdoku/202610/NB/GPKE-Teil2-neuanlage) — 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.*