Transmission of information — NB view
The sending market actor transmits all information to the receiving market actor. The transmission of the information can take place between
- from the NB to LF
- from the LF to NB
- from the NB to MSB
- from the MSB to NB
- from the NB to NB
- from the NB to BIKO
- from the BIKO to NB
- from the NB to BKV
- from the BKV to NB
- from the NB to ÜNB
- from the ÜNB to NB
- from the LF to LF
- from the LF to MSB
- from the MSB to LF
- from the LF to ÜNB
- from the ÜNB to LF
- from the BIKO to BKV
- from the BKV to BIKO
- from the ÜNB to BKV
- from the BKV to ÜNB
- from the ÜNB to MSB
- from the MSB to ÜNB
- from the ÜNB to BIKO
- from the BIKO to ÜNB
- from the MSB to MSB
- from the ESA to MSB
- from the MSB to ESA and is designated in the use case as „sending market participant“ and „receiving market participant“ and mapped in the SD.
Process flow from the perspective of the NB
Process steps
Information
NB LFCheck identifiers
- 21045 — EnFG information · AS4
- 37000 — Communication details of the LF, electricity · AS4
- 37001 — Communication details of the NB, electricity · AS4
- 37002 — Communication details of the MSB, electricity · AS4
- 37003 — Communication details of the BKV, electricity · AS4
- 37004 — Communication details of the BIKO, electricity · AS4
- 37005 — Communication details of the ÜNB, electricity · AS4
- 37006 — Communication details of the ESA, electricity · AS4
- 13028 — Basis for POG determination · AS4
Flow
Message from LF · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic
- Read market location
Write endpoint
21045→ Transaction created — Create process dataPOST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
Write endpoint
37000,37001,37002,37003,37004,37005→ Transaction updated — Update process dataPOST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
Write endpoint
37006,13028→ Transaction created — Create process dataPOST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
Load data for processing
- Read service provider communication details
GET /getCommunicationDataBasic
- Read service provider communication details
Process information
Wording of the consolidated version, profile ch. 4.1, pp. 31–32.
Preconditions
- The market actor is not a natural person.
- The sending market actor has new or changed information.
- The EDIFACT communication between the market participants has been established. Before the EDIFACT communication is established, contact is made bilaterally.
- In the case of privileged status under the Energiefinanzierungsgesetz: This concerns a consuming market location.
Results
- The information is used for the further business relationship and any clearing cases or
- the recipient processes the transmitted information and, where applicable, triggers further steps (such as taking the EnFG privilege entitlement into account in the grid usage settlement).
Error case
Result in the error case
In the error cases, the use case is started again and the information is transmitted.
Error cases
- the information contains an error;
- the information is not up to date;
- the information was not transmitted in full.
Further requirements
This use case is used for the transmission of information and comprises in particular
- the initial transmission and updating of contact details:
- In the case of an update, all communication details of the sending market actor are transmitted to the receiving market actor.
- The communication details are to be versioned unambiguously. The current version identifier, the start of validity and the identifier of the previous version are to be specified. Exception: for the initial population, no start of validity is to be specified, since the communication details apply with immediate effect. Furthermore, no previous version is to be specified for the initial population.
- The validity of communication details ends with the transmission of communication details with an identical start of validity and a higher version identifier, or with the entry into force of communication details with a later start of validity and a higher version identifier, or by transmission of the identifier "inactive" for the communication details. Communication details always begin and end at 00:00 of a calendar day.
- The first contact between the market participants, i.e. before a EDIFACT relationship is established, takes place bilaterally.
- If the final customer is itself the grid user (= grid user without an all-inclusive contract), it assumes the role of LF within the meaning of this process description, insofar as these provisions are applicable to it accordingly.
- and the transmission of the privilege under the Energy Financing Act by the LF to the NB:
- If the EnFG privilege entitlement is changed retroactively, an invoice correction may become necessary if the time period of an invoice is affected.
- the initial transmission and updating of contact details:
First message
LF sends “Information” (step 1). From here on, it is the turn of the party involved on this page.
Objective
The receiving market participant has the valid information of the sending market participant in full.
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 — LF
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 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: 1