# Business data request — LF view The process describes the request for master data on a market or metering location between the NB and a further market partner and the request for values (excluding complaints about missing or implausible values – see under “further requirements”) on a market or metering location or tranche between the MSB and a further market partner. The business data request is addressed to the NB or MSB of the market location that was assigned to the market location for the time period for which the master data or values are required. Either master data for the point in time of the request or values for a point in time or a time period can be requested. The requesting party submits a business data request to the NB or MSB. The NB or MSB checks the request. In the case of an authorised request and a successful identification of the market or metering location, the NB or MSB transmits the requested information to the requesting party. Otherwise the NB or MSB sends the requesting party a rejection of the business data request. The data exchange within the use case “[start of supply](/en/prozessdoku/202610/LF--LFA/GPKE-Teil2-lieferbeginn)” (GPKE part 2) remains unaffected by the option of requesting this data via the use case “business data request” ahead of the start of supply. The process can also be used when the gas MSB wants to ask the electricity NB whether a SMGW is already installed at an address. If a SMGW is installed, the NB names to the gas-MSB the responsible MSB for the SMGW. ## Process flow from the perspective of the LF \nSystem diagram: Geschäftsdatenanfrage — view of LF\n\n\nCustomer backend system\n\nMACO APP · LF\n\nMarket partner\n\n\n\nProcess trigger received\n\nSTART_GESCHAEFTSDATEN\nANFRAGE\n\nAPI\n\n1. Geschäftsdatenanfrage\n\n\nNB\n\nAS4\n17132, 17132, 17104\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Antwort\n\n\nNB\n\nAS4\n55035, 55060, 55095…\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\nPI 55095\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\nPI 55035\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\nPI 55060, 55194, 19104, 19101\n\nProcess trigger received\n\n\n2 alternative events\n\nAPI\n\n3. Geschäftsdatenanfrage\n\n\nMSB\n\nAS4\n17102\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n4. Antwort\n\n\nMSB\n\nAS4\n19102, 13018, 13017…\n\nLoad data for the incoming\ncheck\n\n\n5 read APIs called\n\nAPI\nlisted at the step\n\nAPERAK check: Z33,\nMSCONS, Z30\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\nPI 13018, 13017, 13019, 13016, 13…\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\nPI 19102\n\nLoad data for the check\n\n\n2 read APIs called\n\nAPI\nlisted at the step\n\nEBD check: E_0456\nLieferschein prüfen\n\n"} gesamt={"\nSequence diagram: Geschäftsdatenanfrage — view of LF\n\n\nBackend (customer)\n\n\nMACO APP · LF\n\n\nNB\n\n\nMSB\n\n\nSTART_GESCHAEFTSDATENANFRAGE\nTrigger event\n\n1. Geschäftsdatenanfrage\nAS4 · PI 17132, 17132, 17104\n\nUpdate transaction\nUpdate process data\n\n2. Antwort\nAS4 · PI 55035, 55060, 55095… · E_0441, E_0443\nE_0441 — Geschäftsdatenanfrage zu Stammdaten prüfen\nE_0443 — Geschäftsdatenanfrage zu Stammdaten prüfen\n\nUpdate transaction\nUpdate process data · PI 55095\n\nUpdate transaction\nUpdate process data · PI 55035\n\nUpdate transaction\nUpdate process data · PI 55060, 55194, 19104, 19101\n\n2 alternative events\nTrigger event\n\n3. Geschäftsdatenanfrage\nAS4 · PI 17102\n\nUpdate transaction\nUpdate process data\n\n4. Antwort\nAS4 · PI 19102, 13018, 13017… · E_0442\nE_0442 — Geschäftsdatenanfrage zu Werten prüfen\n\nCreate transaction\nCreate process data · PI 13018, 13017, 13019, 13016, 13…\n\nUpdate transaction\nUpdate process data · PI 19102\n"} titel="LF" /> ## Process steps ### Business data request
**Check identifiers** - [17132](/en/schnittstellen/202610/pruefi/ORDERS/PI_17132) — Request master data (electricity) · AS4 - [17104](/en/schnittstellen/202610/pruefi/ORDERS/PI_17104) — Request from MSB gas · AS4
**Flow**
  1. **Prozessauslöser** [`START_GESCHAEFTSDATENANFRAGE`](/en/api/202610/ausloeser-lf/start-geschaeftsdatenanfrage) \",\n \"lokationsId\": \"\"\n }\n ],\n \"AUFTRAG\": [\n {\n \"positionsdaten\": [\n \"\"\n ]\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_GESCHAEFTSDATENANFRAGE\",\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.
### Response
**Check identifiers** - [55035](/en/schnittstellen/202610/pruefi/UTILMD/PI_55035) — Response to GDA cons. MaLo · AS4 - [55060](/en/schnittstellen/202610/pruefi/UTILMD/PI_55060) — Response to GDA · AS4 - [55095](/en/schnittstellen/202610/pruefi/UTILMD/PI_55095) — Response to GDA gen. MaLo · AS4 - [55194](/en/schnittstellen/202610/pruefi/UTILMD/PI_55194) — Response to GDA (electricity to gas) · AS4 - [19104](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19104) — Rejection of the request from MSB gas · AS4 - [19101](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19101) — Rejection of the request master data · AS4
**Flow**
  1. Message from **NB** · AS4
    **Response per decision tree** - `19104`, `19101` → [E_0443](/en/referenz/202610/ebd/E_0443) · NB · Check business data request for master data - `19101` → [E_0441](/en/referenz/202610/ebd/E_0441) · NB · Check business data request for master data
  2. **APERAK checks** - `55035`, `55095`, `19101` → `Z33` — APERAK check: Is referenced message known ?
  3. **Write endpoint** - `55095` → Transaction updated — `AKTUALISIEREN_PROZESSDATEN_BASIS` Updates the existing transaction in the backend with the data of the incoming message.
  4. **Write endpoint** - `55035` → 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.
  5. **Write endpoint** - `55060`, `55194`, `19104`, `19101` → 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.
### Business data request
**Check identifiers** - [17102](/en/schnittstellen/202610/pruefi/ORDERS/PI_17102) — Request for values · AS4
**Flow**
  1. **Process trigger** - [`START_ANFRAGE_MESSWERTE`](/en/api/202610/ausloeser-lf/start-anfrage-messwerte) \",\n \"lokationsId\": \"\"\n }\n ],\n \"AUFTRAG\": [\n {\n \"positionsdaten\": [\n \"\"\n ]\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_ANFRAGE_MESSWERTE\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren - [`START_GESCHAEFTSDATENANFRAGE`](/en/api/202610/ausloeser-lf/start-geschaeftsdatenanfrage) \",\n \"lokationsId\": \"\"\n }\n ],\n \"AUFTRAG\": [\n {\n \"positionsdaten\": [\n \"\"\n ]\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_GESCHAEFTSDATENANFRAGE\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with one of these events.
  2. Message to **MSB** · 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.
### Response
**Check identifiers** - [19102](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19102) — Rejection of the request values · AS4 - [13018](/en/schnittstellen/202610/pruefi/MSCONS/PI_13018) — Load curve metering location, grid coupling point, grid location · AS4 - [13017](/en/schnittstellen/202610/pruefi/MSCONS/PI_13017) — Meter reading (electricity) · AS4 - [13019](/en/schnittstellen/202610/pruefi/MSCONS/PI_13019) — Energy quantity (electricity) · AS4 - [13016](/en/schnittstellen/202610/pruefi/MSCONS/PI_13016) — Energy quantity and max. power (electricity) · AS4 - [13025](/en/schnittstellen/202610/pruefi/MSCONS/PI_13025) — Load curve market location, tranche · AS4
**Flow**
  1. Message from **MSB** · AS4
    **Response per decision tree** - `19102` → [E_0442](/en/referenz/202610/ebd/E_0442) · MSB · Check business data request for values
  2. **Load data for the incoming check** - [Read metering location](/en/api/202610/backend-lesen/getmeterlocationbasic#messlokation-lesen) `GET /getMeterLocationBasic` Try it - [Read grid location](/en/api/202610/backend-lesen/getgridlocationbasic#netzlokation-lesen) `GET /getGridLocationBasic` Try it - [Read meter](/en/api/202610/backend-lesen/getcounterbasic#zahler-lesen) `GET /getCounterBasic` Try it - [Read market location](/en/api/202610/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it - [Read tranche](/en/api/202610/backend-lesen/gettranchebasic#tranche-lesen) `GET /getTrancheBasic` Try it
  3. **APERAK checks** - `19102`, `13018`, `13019`, `13016`, `13025` → `Z33` — Aperak Prüfung: Ist referenzierte Nachricht bekannt ? - `13018`, `13017`, `13019`, `13016`, `13025` → `MSCONS` - `13018`, `13025` → `Z30`
  4. **Write endpoint** - `13018`, `13017`, `13019`, `13016`, `13025` → Transaction created — [Create process data](/en/api/202610/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.
  5. **Write endpoint** - `19102` → 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.
  6. **Load data for the check** - [Read energy quantities from billing context](/en/api/202610/backend-lesen/getenergyamount#energiemengen-aus-abrechnungskontext-lesen) `GET /getEnergyAmount` Try it - [Read grid usage contract](/en/api/202610/backend-lesen/getgridusagecontractbasic#netznutzungsvertrag-lesen) `GET /getGridUsageContractBasic` Try it
  7. **Decision tree** - `13019`, `13016` → [E_0456](/en/referenz/202610/ebd/E_0456) — Check delivery note
Decision trees of this process | EBD | Name | |---|---| | [E_0441](/referenz/202610/ebd/E_0441) | Check business data request for master data | | [E_0442](/referenz/202610/ebd/E_0442) | Check business data request for values | | [E_0443](/referenz/202610/ebd/E_0443) | Check business data request for master data |
## Process information Wording of the consolidated version, profile ch. 3.1, pp. 29–30.
  1. ### Preconditions - The requesting party is assigned to the market or metering location throughout the requested time period or at the point in time of the request and is therefore authorised to receive the requested data, or - If the requesting party is not assigned to the market or the metering location for the entire requested time period or is not legally entitled, an authorisation to receive the requested information must be demonstrated by the requesting party to the requested NB or MSB. The existence of corresponding contractual powers of attorney (e.g. within the metering point operator framework contract between MSB and NB or the grid usage contract between LF and NB) can be assured. - For requests at market location level, the ID of the market location is known. - For requests at metering location level, the ID of the metering location is known.
  2. ### Results The requesting party has received the data and can use it for the subsequent processes.
  3. ### Error case #### Error cases - The requesting party is not authorised. - The requested party does not have the data.
  4. ### Further requirements - In justified individual cases, the NB or MSB may request proof of authorization. - Implausible or missing values are to be complained about, depending on the preconditions, via the use case “Complaint about values” (WiM Part 2) or the use case “Complaint about a configuration” (GPKE Part 3).
  5. ### Trigger **Runs beforehand:** [Determination of the MaLo ID of the market location](/en/prozessdoku/202610/LF/GPKE-Teil2-ermittlung-der-malo-id-der-marktlokation) — these processes name the one shown here in their result.
  6. ### First message The party involved on this page is itself the sender of: „Business data request“ to **NB** (step 1).
  7. ### Objective The requesting party has received the requested business data.
## 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-Teil4-geschaeftsdatenanfrage) — NB - [View MSB](/en/prozessdoku/202610/MSB/GPKE-Teil4-geschaeftsdatenanfrage) — 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.* The connector table lists no write call for these steps. Derived from the process flow: the own role was already involved in this process, so the transaction already exists. Applies to: [2](#schritt-2), [4](#schritt-4) These write calls 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: [2](#schritt-2)