# Request and order placement of values by the ESA — ESA view The ESA requests the transmission of values and the associated costs from the MSB. If the values can be made available in the ordered granularity and scope by the MSB (from the back-end system or directly from the iMS), the MSB creates a quotation for this transmission of values and makes it available to the ESA. The ESA can then order the transmission of values. If the ESA wants to receive the values at market location level, it addresses its request and order placement to the MSB of the market location. If the ESA wants to receive the values at metering location level, it addresses its request and order placement to the MSB of the metering location. If the ESA wants to receive the values at grid location level, it addresses its request and order placement to the MSB of the grid location. ## Process flow from the perspective of the ESA \nSystem diagram: Anfrage und Bestellung von Werten durch den ESA — view of ESA\n\n\nCustomer backend system\n\nMACO APP · ESA\n\nMarket partner\n\n\n\n1. Anfrage von Werten\n\nMSB\n\nAS4\n35003\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Angebot zur / Ablehnung\nder Anfrage\n\n\nMSB\n\nAS4\n15003, 21033\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n3. Bestellung\n\n\nMSB\n\nAS4\n17007\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n4. Antwort auf Bestellung\n\n\nMSB\n\nAS4\n19011, 19012\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n5. Stornierung einer\nbestätigten Bestellung\n\n\nMSB\n\nAS4\n39002\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n6. Antwort auf Stornierung\neiner bestätigten Bestellung\n\n\nMSB\n\nAS4\n19013, 19014\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Anfrage und Bestellung von Werten durch den ESA — view of ESA\n\n\nBackend (customer)\n\n\nMACO APP · ESA\n\n\nMSB\n\n\n1. Anfrage von Werten\nAS4 · PI 35003\n\nUpdate transaction\nUpdate process data\n\n2. Angebot zur / Ablehnung der Anfrage\nAS4 · PI 15003, 21033 · E_0252\nE_0252 — Anfrage prüfen\n\nUpdate transaction\nUpdate process data\n\n3. Bestellung\nAS4 · PI 17007\n\nUpdate transaction\nUpdate process data\n\n4. Antwort auf Bestellung\nAS4 · PI 19011, 19012 · E_0256\nE_0256 — Bestellung prüfen\n\nUpdate transaction\nUpdate process data\n\n5. Stornierung einer bestätigten Bestellung\nAS4 · PI 39002\n\nUpdate transaction\nUpdate process data\n\n6. Antwort auf Stornierung einer bestätigten Bes…\nAS4 · PI 19013, 19014 · E_0257\nE_0257 — Stornierung prüfen\n\nUpdate transaction\nUpdate process data\n"} titel="ESA" /> ## Process steps ### Request for values
**Check identifiers** - [35003](/en/schnittstellen/202604/pruefi/REQOTE/PI_35003) — Request for values · AS4
**Flow**
  1. Message to **MSB** · AS4
  2. **Write endpoint** - Transaction updated — `AKTUALISIEREN_PROZESSDATEN` Updates the existing transaction in the backend once the message has been created.
### Quotation for / rejection of the request
**Check identifiers** - [15003](/en/schnittstellen/202604/pruefi/QUOTES/PI_15003) — Quotation for the request for values · AS4 - [21033](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21033) — Rejection of the request · AS4
**Flow**
  1. Message from **MSB** · AS4
    **Response per decision tree** - `21033` → [E_0252](/en/referenz/202604/ebd/E_0252) · MSB · Check request
  2. **Write endpoint** - Transaction updated — `AKTUALISIEREN_PROZESSDATEN` Updates the existing transaction in the backend with the data of the incoming message.
### Order placement
**Check identifiers** - [17007](/en/schnittstellen/202604/pruefi/ORDERS/PI_17007) — Order placement of values · AS4
**Flow**
  1. Message to **MSB** · AS4
  2. **Write endpoint** - Transaction updated — `AKTUALISIEREN_PROZESSDATEN` Updates the existing transaction in the backend once the message has been created.
### Response to order placement
**Check identifiers** - [19011](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19011) — Confirmation of the order cancellation/placement of values · AS4 - [19012](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19012) — Rejection of the order cancellation/placement of values · AS4
**Flow**
  1. Message from **MSB** · AS4
    **Response per decision tree** - `19011`, `19012` → [E_0256](/en/referenz/202604/ebd/E_0256) · MSB · Check order placement
  2. **Write endpoint** - Transaction updated — `AKTUALISIEREN_PROZESSDATEN` Updates the existing transaction in the backend with the data of the incoming message.
### Cancellation of a confirmed order placement
**Check identifiers** - [39002](/en/schnittstellen/202604/pruefi/ORDCHG/PI_39002) — Cancellation of the order placement · AS4
**Flow**
  1. Message to **MSB** · AS4
  2. **Write endpoint** - Transaction updated — `AKTUALISIEREN_PROZESSDATEN` Updates the existing transaction in the backend once the message has been created.
### Response to cancellation of a confirmed order placement
**Check identifiers** - [19013](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19013) — Confirmation of the cancellation of an order placement · AS4 - [19014](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19014) — Rejection of the cancellation of an order placement · AS4
**Flow**
  1. Message from **MSB** · AS4
    **Response per decision tree** - `19013`, `19014` → [E_0257](/en/referenz/202604/ebd/E_0257) · MSB · Check cancellation
  2. **Write endpoint** - Transaction updated — `AKTUALISIEREN_PROZESSDATEN` Updates the existing transaction in the backend with the data of the incoming message.
Decision trees of this process | EBD | Name | |---|---| | [E_0252](/referenz/202604/ebd/E_0252) | Check request | | [E_0256](/referenz/202604/ebd/E_0256) | Check order placement | | [E_0257](/referenz/202604/ebd/E_0257) | Check cancellation |
## Process information Wording of the consolidated version, profile ch. 4.1.1, pp. 69–71.
  1. ### Preconditions - The assurance of ESA regarding compliance with the legal data protection requirements is available to MSB. - The contractual basis for the request and transmission of the values and for the billing of the service provided from MSB to ESA is available to MSB. - For a request for values at market location level: - The metering point operation is carried out at all metering locations of the market location by the same MSB; i.e. the MSB of the market location is the MSB of the metering location(s). - For a request for values at grid location level: - The metering point operation is carried out at all metering locations of the grid location by the same MSB; i.e. the MSB of the grid location is the MSB of the metering location(s). - The EDIFACT communication between MSB and ESA has been established. - The existing device technology permits the transmission of the requested values. - For the transmission of values from the iMS: all metering locations required to perform the transmission of values are equipped with a iMS.
  2. ### Results - The MSB provides the transmission of values ordered by the ESA (from the back-end system or directly from the iMS). - In the case in which the metering location is equipped with iMS: If parameterisation of the measuring equipment is necessary in order to provide the transmission of values, MSB carries out the parameterisation of the measuring equipment.
  3. ### Error case #### Result in the error case - The transmission of values cannot be provided. #### Error cases - The MSB is not assigned to the market location /metering location/grid location for the requested time period. - The existing device technology does not permit the transmission of the requested values. - The legal basis for the transmission of values does not exist.
  4. ### Further requirements - The request of values must always be addressed to the MSB assigned to the metering location/market location/grid location that is assigned to the market location/metering location/grid location for the time period for which the values are required. This also applies to historical values. - The request of values can only be made for the time period for which the AN is assigned to the market location/metering location/grid location. - Ordering other types of values/transmission of values not covered by this use case by the ESA towards the MSB by way of NON-EDIFACT communication (in text form) remains possible at any time. - If the existing device technology does not permit the requested transmission of values, the change of the device technology is not to be ordered via this use case. ESA must transmit this request to MSB involving the AN outside the process standardisation (i.e. via NON-EDIFACT).
  5. ### First message The party involved on this page sends this itself: “Request for values” to **MSB** (step 1).
  6. ### Objective The ESA has ordered the transmission of values from the MSB.
## 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/202604/MSB/WiM-Teil2-anfrage-und-bestellung-von-werten-durch-den-esa) — 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 source does not yet name the event that triggers these steps. Applies to: [1](#schritt-1) 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), [6](#schritt-6) For this market role there is no write catalog; the step therefore shows only the command of the write call, without address and without button. Applies to: [1](#schritt-1), [2](#schritt-2), [3](#schritt-3), [4](#schritt-4), [5](#schritt-5), [6](#schritt-6)