Master data on balancing group integrity — View NB
The NB transmits the master data on balancing group integrity to the ÜNB. The ÜNB checks the data and gives the NB a quality response message on the content of the data. If the ÜNB expects different data content, it states this in the response message. In this case the NB informs the ÜNB of the processing status of its response message.
Process flow from the perspective of the NB
Process steps
Master data balancing group integrity
NB ÜNBSTART_VERSAND_SDAESTART_VERSAND_STDA_BK_TREUECheck identifiers
- 55670 — Master data BG fidelity · AS4
Flow
Process trigger
The backend triggers this step with one of these events.
Message to ÜNB · AS4
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 on master data
NB ÜNBZ33E_0616 Check response message to the change21047Check identifiers
- 55671 — Response message to master data BG fidelity · AS4
Flow
Message from ÜNB · AS4
Response per decision tree
55671→ E_0574 · ÜNB · Check master data on balancing group integrity
APERAK checks
55671→Z33
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
Load data for the check
- Read market location
GET /getMarketLocationBasic
- Read market location
Decision tree
55671→ E_0616 — Check response message to the change
Trigger follow-up process
- 21047 — Processing status message
After processing, the MACO APP starts this follow-up process itself.
Processing status of the response message
NB ÜNB55671START_VERSAND_BEARB_MELDUNGSTART_VERSAND_STATUSMELDUNGCheck identifiers
- 21047 — Processing status message · AS4
Flow
Triggered by incoming message
- 55671 — Response message to master data BG fidelity
The MACO APP sends this message itself, as a follow-up process after this incoming message. In addition, the backend can trigger this step with an event — the next item.
Process trigger
The backend triggers this step with one of these events.
Message to ÜNB · AS4
Response per decision tree
21047→ E_0616 · NB · Check response message to the change
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
Decision trees of this process
| EBD | Name |
|---|---|
| E_0574 | Check master data on balancing group integrity |
| E_0616 | Check response message to the change |
Process information
Wording of the consolidated version, profile ch. 2.1, p. 27.
Trigger
In the case of the use case „Billing data balancing group settlement“ it is a market location or tranche
- which is mapped with balancing based on quarter-hour values from the initial commissioning of the market location (creation) onwards or
- in which a change is made from balancing based on profiles to balancing based on quarter-hour values or
- with balancing based on quarter-hour values and master data on balancing group integrity have changed or
- in which a change is made from balancing based on quarter-hour values to balancing based on profiles or
- with balancing based on quarter-hour values and the market location is decommissioned.
Runs beforehand: Billing data for balancing group settlement — these processes name the one shown here in their result.
First message
The party involved on this page is itself the sender of: „Master data for balancing group integrity“ to ÜNB (step 1).
Objective
The master data on balancing group integrity have been exchanged.
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 · market role UENB
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.
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: 2