Determination of the MaLo-ID of the market location — LF view
The LF requests the MaLo-ID of the market location from the NB. In doing so, the LF provides information that serves to identify the market location. The NB checks the request and, if successful, reports the MaLo-ID of the market location and supplementary information back to the LF.
Process flow from the perspective of the LF
Process steps
Determination of the MaLo-ID of the market location
LF NBTransmission API API00003 · /maloID/request/
Flow
Message to NB · API
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend once the message has been created.
- Transaction updated — Update process data
Response message to a request
LF NBTransmission API API00003 · /maloId/dataForMarketLocationNegative/ · API API00003 · /maloId/dataForMarketLocationPositive/
Flow
Message from NB · API
Response per decision tree
- — → E_0594 · NB · Check request from LF
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated — Update process data
Decision trees of this process
| EBD | Name |
|---|---|
| E_0594 | Check request from LF |
Process information
Wording of the consolidated version, profile ch. 1.1.1, p. 5.
Preconditions
- In the case of a consuming market location: LF holds the power of attorney of the final customer to submit the request on their behalf.
- In the case of a generating market location or a tranche: LF holds the power of attorney of the EZ to submit the request on its behalf.
Results
If required, the LF can
- Use case “Contract termination”
- Use case “Start of supply”
- Start use case “Business data request”.
Error case
Result in the error case
The LF enters into bilateral clearing with the final customer or EZ; if necessary, the LF starts the use case again.
Error cases
The market location cannot be identified by the NB, or not uniquely
Further requirements
This use case is to be implemented via API web services.
Trigger
- The LF does not have the MaLo-ID of the market location or supplementary information such as the MaLo-ID of the tranche available in order, if required, to
- Use case “Contract termination”
- Use case “Start of supply”
- to start use case “Business data request”.
- The LF does not have the MaLo-ID of the market location or supplementary information such as the MaLo-ID of the tranche available in order, if required, to
First message
The party involved on this page is itself the sender of: „Determination of the MaLo-ID of the market location“ to NB (step 1).
Objective
The LF has the MaLo-ID of the market location as well as supplementary information (e.g. MaLo-ID of the tranche) from the NB.
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 — NB
Notes on this page
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
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
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.