# Transmission of values according to type 2 from MSB to NB or LF — MSB view For the transmission of values from the back-end system: The MSB of the directly affected location transmits the values of the ordered configuration for the directly affected location to the NB or LF. If further locations of the directly affected location are affected by the configuration, the MSB of the directly affected location also transmits the values for the further affected locations to the NB or LF. For the transmission of values directly from the iMS to the NB or LF: The MSB of the directly affected location (here the iMS) transmits the values of the ordered configuration for the directly affected location to the NB or LF. ## Process flow from the perspective of the MSB \nSystem diagram: Übermittlung von Werten nach Typ 2 vom MSB an NB oder LF — view of MSB\n\n\nCustomer backend system\n\nMACO APP · MSB\n\nMarket partner\n\n\n\nProcess trigger received\n\nSTART_ERHEBUNG_MESSWE\nRTE\n\nAPI\n\n1. Werte an NB\n\n\nNB\n\nAS4\n13027\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nProcess trigger received\n\n\nSTART_ERHEBUNG_MESSWE\nRTE\n\nAPI\n\n2. Werte an LF\n\n\nLF\n\nAS4\n13027\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Übermittlung von Werten nach Typ 2 vom MSB an NB oder LF — view of MSB\n\n\nBackend (customer)\n\n\nMACO APP · MSB\n\n\nNB\n\n\nLF\n\n\nSTART_ERHEBUNG_MESSWERTE\nTrigger event\n\n1. Werte an NB\nAS4 · PI 13027\n\nUpdate transaction\nUpdate process data\n\nSTART_ERHEBUNG_MESSWERTE\nTrigger event\n\n2. Werte an LF\nAS4 · PI 13027\n\nUpdate transaction\nUpdate process data\n"} titel="MSB" /> ## Process steps ### Values to NB
**Check identifiers** - [13027](/en/schnittstellen/202610/pruefi/MSCONS/PI_13027) — Values according to type 2 · AS4
**Flow**
  1. **Prozessauslöser** [`START_ERHEBUNG_MESSWERTE`](/en/api/202610/ausloeser-msb/start-erhebung-messwerte) \"\n ],\n \"lokationsId\": \"\"\n }\n ],\n \"ZAEHLER\": [\n {\n \"zaehlernummer\": \"\"\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"anfrageReferenz\": \"\",\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"lokationsTyp\": \"\",\n \"sparte\": \"\",\n \"typ\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_ERHEBUNG_MESSWERTE\",\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-msb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Values to LF
**Check identifiers** - [13027](/en/schnittstellen/202610/pruefi/MSCONS/PI_13027) — Values according to type 2 · AS4
**Flow**
  1. **Prozessauslöser** [`START_ERHEBUNG_MESSWERTE`](/en/api/202610/ausloeser-msb/start-erhebung-messwerte) \"\n ],\n \"lokationsId\": \"\"\n }\n ],\n \"ZAEHLER\": [\n {\n \"zaehlernummer\": \"\"\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"anfrageReferenz\": \"\",\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"lokationsTyp\": \"\",\n \"sparte\": \"\",\n \"typ\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_ERHEBUNG_MESSWERTE\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. Message to **LF** · AS4
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-msb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
## Process information Wording of the consolidated version, profile ch. 3.2.1, pp. 66–67.
  1. ### Preconditions - The metering point operation is carried out at all affected locations by the same MSB; i.e. the MSB of the directly affected location is the MSB of all further affected locations, where applicable. - Towards NB the following applies: NB has ordered a configuration via the use case „Order placement of a configuration from NB or LF to MSB“ (GPKE part 3) and the order placement has been confirmed by MSB. - Towards LF the following applies: LF has ordered a configuration via the use case „Order placement of a configuration from NB or LF to MSB“ (GPKE part 3) and the order placement has been confirmed by MSB.
  2. ### Results The billing via the use case “Billing of services of price sheet A of the MSB” (GPKE part 3) can take place towards the NB or LF, provided the configuration is chargeable.
  3. ### Error case #### Result in the error case The transmission of values cannot be provided.
  4. ### Further requirements A complaint about the configuration is possible via the use case „Complaint about a configuration“ (GPKE part 3).
  5. ### Trigger - Start of the effective period of the ordered configuration.
  6. ### First message The party involved on this page is itself the sender of: „Values to NB“ to **NB** (step 1).
  7. ### Objective The NB or LF receives the values of the ordered configuration for the affected locations (e.g. metering location, 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 LF](/en/prozessdoku/202610/LF/WiM-Teil2-uebermittlung-von-werten-nach-typ-2-vom-msb-an-nb-oder-lf) — LF - [View NB](/en/prozessdoku/202610/NB/WiM-Teil2-uebermittlung-von-werten-nach-typ-2-vom-msb-an-nb-oder-lf) — 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.*