# Order placement for a configuration from the LF to the MSB — WMSB view The NB or LF orders a configuration for the directly affected location from the MSB of the directly affected location. If further locations of the directly affected location are affected by the configuration, the NB or LF also states these further affected locations in the order placement (for example, in the order placement for the change of the balancing procedure at market location level, the NB has to order not only the market location but also all metering locations of the market location from the MSB of the market location). Before a chargeable order placement can be made, the NB or LF has to request a quotation from the MSB of the directly affected location for setting up the configuration. The MSB checks the order placement and informs the NB or LF of the further procedure for the order placement. If further locations of the directly affected location are affected by the configuration for which the MSB of the directly affected location does not perform the metering point operation, it involves the respective further MSB for these further affected locations. ## Process flow from the perspective of the MSB (WMSB) \nSystem diagram: Bestellung einer Konfiguration vom LF an MSB — view of MSB\n\n\nCustomer backend system\n\nMACO APP · weiterer MSB\n\nMarket partner\n\n\n\n6. Bestellung einer\nKonfiguration für weiter\nbetroffene Lokati…\n\nMSB\n\nAS4\n17130, 17118\n\nLoad data for the incoming\ncheck\n\n\n4 read APIs called\n\nAPI\nlisted at the step\n\nAPERAK check: Z10, Z17,\nZ18, Z33\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\nPI 17130\n\nCreate transaction\n\n\nCreate process data\n\nAPI\nPI 17118\n\nLoad data for the check\n\n\n4 read APIs called\n\nAPI\nlisted at the step\n\nEBD check: E_0526\nBestellung prüfen\n\n\nTrigger follow-up process:\n19132\n\n\nTriggered by incoming\nmessage: 17130\n\n\n7. Mitteilung zum weiteren\nVorgehen zur Bestellung\n\n\nMSB\n\nAS4\n19132, 19127\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n8. Antwort auf Bestellung\n\n\nMSB\n\nAS4\n21043\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n10. Mitteilung über\nGesamtvorgang\n\n\nMSB\n\nAS4\n21043\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Bestellung einer Konfiguration vom LF an MSB — view of MSB\n\n\nBackend (customer)\n\n\nMACO APP · weiterer MSB\n\n\nLF\n\n\nMSB\n\n\n1. Anfrage einer Konfiguration auf Ebene der dir…\nAS4 · PI 35004\n\n2. Angebot zur / Ablehnung der Anfrage\nAS4 · PI 15004, 21033 · E_0531\nE_0531 — Anfrage prüfen\n\n3. Bestellung einer Konfiguration auf Ebene der…\nAS4 · PI 17131\n\n4. Bestellung einer Konfiguration auf Ebene der…\nAS4 · PI 17130, 17123\n\n5. Mitteilung zum weiteren Vorgehen zur Bestellu…\nAS4 · PI 19132, 19124 · E_0533\nE_0533 — Bestellung prüfen\n\n6. Bestellung einer Konfiguration für weiter bet…\nAS4 · PI 17130, 17118\n\nCreate transaction\nCreate process data · PI 17130\n\nCreate transaction\nCreate process data · PI 17118\n\n7. Mitteilung zum weiteren Vorgehen zur Bestellu…\nAS4 · PI 19132, 19127 · E_0527\nE_0527 — Bestellung\n\nUpdate transaction\nUpdate process data\n\n8. Antwort auf Bestellung\nAS4 · PI 21043 · E_0535\nE_0535 — Umsetzung der Konfiguration prüfen\n\nUpdate transaction\nUpdate process data\n\n9. Antwort auf Bestellung\nAS4 · PI 21043 · E_0536\nE_0536 — Bewertung des Gesamtvorgangs\n\n10. Mitteilung über Gesamtvorgang\nAS4 · PI 21043 · E_0536\nE_0536 — Bewertung des Gesamtvorgangs\n\nUpdate transaction\nUpdate process data\n"} titel="WMSB" /> ## Process steps ### Request for a configuration at the level of the directly affected location This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [35004](/en/schnittstellen/202610/pruefi/REQOTE/PI_35004) — Request for a configuration · AS4
### Quotation for / rejection of the request This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [15004](/en/schnittstellen/202610/pruefi/QUOTES/PI_15004) — Quotation for a configuration · AS4 - [21033](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21033) — Rejection of the request · AS4
**Response per decision tree** - `21033` → [E_0531](/en/referenz/202610/ebd/E_0531) · MSB · Check request
### Order placement for a configuration at the level of the directly affected location This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [17131](/en/schnittstellen/202610/pruefi/ORDERS/PI_17131) — Order placement quotation for a configuration · AS4
### Order placement for a configuration at the level of the directly affected location This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [17130](/en/schnittstellen/202610/pruefi/ORDERS/PI_17130) — Order placement of a configuration · AS4 - [17123](/en/schnittstellen/202610/pruefi/ORDERS/PI_17123) — Order placement change of metering time period definition · AS4
### Notification on the further procedure for the order placement This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [19132](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19132) — Notification of configuration order placement · AS4 - [19124](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19124) — Notification of change of metering time period definition · AS4
**Response per decision tree** - `19132`, `19124` → [E_0533](/en/referenz/202610/ebd/E_0533) · MSB · Check order placement
### Order placement for a configuration for further affected locations
**Check identifiers** - [17130](/en/schnittstellen/202610/pruefi/ORDERS/PI_17130) — Order placement of a configuration · AS4 - [17118](/en/schnittstellen/202610/pruefi/ORDERS/PI_17118) — Order placement of a configuration change · AS4
**Flow**
  1. Message from **MSB** · AS4
  2. **Load data for the incoming check** - [Read market location](/en/api/202610/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it - [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 controllable resource](/en/api/202610/backend-lesen/getcontrollableresourcebasic#steuerbare-ressource-lesen) `GET /getControllableResourceBasic` Try it
  3. **APERAK checks** - `17130`, `17118` → `Z10` - `17130`, `17118` → `Z17` - `17130`, `17118` → `Z18` - `17130` → `Z33`
  4. **Write endpoint** - `17130` → Transaction created — [Create process data](/en/api/202610/backend-schreiben-msb/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** - `17118` → Transaction created — [Create process data](/en/api/202610/backend-schreiben-msb/createprocessdata#prozessdaten-erstellen) `POST /createProcessData` Try it out Creates a new transaction in the backend with the data of the incoming message.
  6. **Load data for the check** - `LESEN_DEFINITION_LST_KURVEN` - [Read switching time definition](/en/api/202610/backend-lesen/getdefinitionswitch#schaltzeitdefinition-lesen) `GET /getDefinitionSwitch` Try it - [Read metering time period definition ](/en/api/202610/backend-lesen/getdefinitioncounting#zaehlzeitdefinition-lesen) `GET /getDefinitionCounting` Try it - [Read price sheet](/en/api/202610/backend-lesen/getpricesheetbasic#preisblatt-lesen) `GET /getPriceSheetBasic` Try it
  7. **Decision tree** - `17130` → [E_0526](/en/referenz/202610/ebd/E_0526) — Check order placement
  8. **Trigger follow-up process** - [19132](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19132) — Notification of configuration order placement After processing, the MACO APP starts this follow-up process itself.
### Notification on the further procedure for the order placement
**Check identifiers** - [19132](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19132) — Notification of configuration order placement · AS4 - [19127](/en/schnittstellen/202610/pruefi/ORDRSP/PI_19127) — Notification of configuration change · AS4
**Flow**
  1. **Triggered by incoming message** - [17130](/en/schnittstellen/202610/pruefi/ORDERS/PI_17130) — Order placement of a configuration The MACO APP sends this message itself, as a follow-up process after this incoming message.
  2. Message to **MSB** · AS4
    **Response per decision tree** - `19132`, `19127` → [E_0527](/en/referenz/202610/ebd/E_0527) · MSB · Order placement
  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.
### Response to order placement
**Check identifiers** - [21043](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21043) — Order response / notification · AS4
**Flow**
  1. Message to **MSB** · AS4
    **Response per decision tree** - `21043` → [E_0535](/en/referenz/202610/ebd/E_0535) · Check implementation of the configuration
  2. **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.
### Response to order placement This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [21043](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21043) — Order response / notification · AS4
**Response per decision tree** - `21043` → [E_0536](/en/referenz/202610/ebd/E_0536) · MSB · Assessment of the overall process
### Notification of the overall transaction
**Check identifiers** - [21043](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21043) — Order response / notification · AS4
**Flow**
  1. Message from **MSB** · AS4
    **Response per decision tree** - `21043` → [E_0536](/en/referenz/202610/ebd/E_0536) · MSB · Assessment of the overall process
  2. **APERAK checks** - `21043` → `Z33`
  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 with the data of the incoming message.
Decision trees of this process | EBD | Name | |---|---| | [E_0527](/referenz/202610/ebd/E_0527) | Order placement | | [E_0535](/referenz/202610/ebd/E_0535) | Check implementation of the configuration | | [E_0536](/referenz/202610/ebd/E_0536) | Assessment of the overall process | | [E_0531](/referenz/202610/ebd/E_0531) | Check request | | [E_0533](/referenz/202610/ebd/E_0533) | Check order placement |
## Process information Wording of the consolidated version, profile ch. 1.3.3.1, pp. 42–46.
  1. ### Preconditions - In the case in which the order placement is preceded by a quotation process: - This is a chargeable configuration. - The article IDs relevant for the configuration are listed in price sheet A of MSB. - 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. - In the case in which the order placement is not preceded by a quotation process: - This is not a chargeable configuration. This would be the case, for example, with an order placement for a transmission of values according to type 1. - In the case of the order placement of a configuration from LF to NB: NB has received an order placement of the configuration from LF via the use case “[Order placement of a configuration from LF to NB](/en/prozessdoku/202610/LF/GPKE-Teil3-bestellung-einer-konfiguration-vom-lf-an-nb)” (e.g. the order placement of a change of the balancing method or the order placement of a configuration for which a metering time period definition of NB is required) for which the setup of the configuration is generally possible from the point of view of NB. - The device technology available at the ordered point in time permits the configuration to be set up. In the case of an order placement for a configuration that requires a metering time period definition of LF, for example, this means that all metering locations of the market location are equipped with iMS. - In the case of the order placement of a tax permit: - The order placement is only possible for one location (controllable resource, grid location). - The location is equipped with a iMS and a control device that communicates via the SMGW. - In the case of the order placement of a configuration that enables the transmission of values directly from iMS to NB or LF: - The order placement is only possible for one location. - The location is equipped with a iMS. - In the case of the order placement of a configuration for which a metering time period definition, switching time definition or power curve definition is required: The definition relevant for the configuration (e.g. metering time period definition of NB) was exchanged within the use cases of the chapter “Exchange regarding metering time, switching time and power curve definitions”. - In the case of the order placement of a configuration for which a metering time period definition is required: This concerns a consuming market location.
  2. ### Results - If the configuration was set up successfully for all affected locations, MSB of the respective affected location carries out the use case “Master data change” (here: SD “[Master data change originating from MSB (responsible)](/en/prozessdoku/202610/MSB--WMSB/GPKE-Teil4-stammdatenaenderung-vom-msb-verantwortlich-ausgehend)”) (GPKE Part 4), provided a master data change is required for the respective location due to the setup of the configuration. - In the case of the order placement of a configuration from LF to NB: NB forwards the confirmation to LF. - In the case in which the order placement was preceded by a quotation process: The billing of the article ID can be carried out via the use case “Billing of services of price sheet A of MSB" by MSB to NB or LF.
  3. ### Error case #### Result in the error case - The NB or LF checks whether a renewed order issuance for the configuration is required. - In the case of the order placement of a configuration from LF to NB: NB forwards the rejection to LF. - The existing configuration remains in place. If the ordered configuration has already been set up for an affected location, the original state prior to the order placement is restored for that location. #### Error cases - In the case in which the order placement is preceded by a quotation process: - This is not a chargeable configuration or - the article IDs relevant to the configuration are not listed in price sheet A of the MSB or - the metering point operation is not performed by the same MSB at all affected locations; i.e. the MSB of the directly affected location is not the MSB of all further affected locations. - In the case in which the order placement is not preceded by a quotation process: This concerns a chargeable configuration. - The market partner is not assigned to the affected location at the ordered start of the effective period. - The device technology available at the ordered point in time does not permit the configuration to be set up. In the case of an order placement for a configuration that requires a metering time period definition of LF, for example, this means: not all metering locations of the market location are equipped with iMS. - In the case of the order placement of a tax permit: - More than one location is specified in the order placement or - The location is not equipped with a iMS and a control device that communicates via the SMGW. - In the case of the order placement of a configuration that enables the transmission of values directly from iMS to NB or LF: - More than one location is specified in the order placement or - The location is not equipped with a iMS. - In the case of the order placement of a configuration for which a metering time period definition, switching time definition or power curve definitions are required: The definition relevant for the configuration (e.g. metering time period definition of NB) was not exchanged within the use cases of the chapter “Exchange regarding metering time, switching time and power curve definition”. - In the case of the order placement of a configuration for which a metering time period definition is required: This concerns a generating market location or a tranche. - Not all parameters or incorrect parameters are available for the setting up of the configuration.
  4. ### Further requirements - If the device technology available at the ordered point in time does not permit the setup of the configuration, the change of the device technology is not to be ordered via this use case. A corresponding change of the device technology can be commissioned as part of a device replacement or via the use cases for the metering location change (WiM Part 1). - Via this use case, the LF can also transmit an order placement of a configuration to the future MSB. - Configurations of NB are communicated by NB to MSB in the use case “[Start of metering point operation](/en/prozessdoku/202610/LF/WiM-Teil1-beginn-messstellenbetrieb)” (WiM Part 1) in process step 2 within the minimum parameters for the metering location(s). An order placement of a configuration contained in the minimum parameters is not necessary via the use case described here. In addition to the configurations communicated in the minimum parameters, NB can transmit an order placement of a configuration to the future MSB using the use case described here. Note: If a metering time period definition of NB is communicated to MSB within the minimum parameters in the use case “[Start of metering point operation](/en/prozessdoku/202610/LF/WiM-Teil1-beginn-messstellenbetrieb)” (WiM Part 1) that MSB has not received in advance via the use case “[Transmission of a definition of NB by NB](/en/prozessdoku/202610/LF/GPKE-Teil3-uebermittlung-einer-definition-des-nb-durch-den-nb)”, the energy is to be recorded in one register at the metering location(s) and the associated market location for the metering time period usage purpose “grid usage”.
  5. ### Trigger - The NB needs to have a configuration set up, or - The LF needs a configuration to be set up which the LF has to order directly from the MSB and not via the NB. This can be, for example: - In the case of the order placement of a configuration for which a metering time period definition of NB is required: NB wishes to change the existing configuration of a market location and its associated metering locations for the metering time period usage purpose “grid usage”. - In the case of the order placement of a configuration for which a metering time period definition of LF is required: LF wishes to state in the order placement - that it wants to order a metering time period definition of the LF with the metering time period usage purpose “end customer” that differs from the existing configuration with the metering time period usage purpose “grid usage” or - that it wants to change the existing configuration for the metering time period usage purpose “end customer” to a different metering time period definition of the LF.
  6. ### First message **MSB** sends “Order placement for a configuration for further affected locations” (step 6). From here on, it is the turn of the party involved on this page.
  7. ### Objective The order placement for the configuration (e.g. metering product, tax permit) for the affected locations (e.g. metering location, market location, controllable resource, grid location) has been confirmed by the MSB of the directly affected 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 MSB](/en/prozessdoku/202610/MSB/GPKE-Teil3-bestellung-einer-konfiguration-vom-lf-an-msb) — MSB - [View LF](/en/prozessdoku/202610/LF/GPKE-Teil3-bestellung-einer-konfiguration-vom-lf-an-msb) — LF *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: [6](#schritt-6) 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: [6](#schritt-6) 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: [10](#schritt-10) For the check identifiers of these steps there is no test case in the test data set; the »Try it out« button of the write interface therefore offers no body. Applies to: [7](#schritt-7), [8](#schritt-8), [10](#schritt-10)