Check identifier 55064 — Response
Check identifier 55064 · EDIFACT message type UTILMD · Format version 202610
This page is derived from the application handbook
The MACO APP does not carry this check identifier. The complete Prüfi pages of this level are produced from the specifications of the application — one class in the templater per check identifier — and that is where the assignment to the business objects (BO4E) comes from: which object carries which field of the message.
The catalogue of the application handbook is the larger set. This page therefore shows what the handbook itself provides — use case, process context and the AHB field list with its conditions. A data structure according to BO4E is not shown, and not because there is none, but because the application does not form one for this check identifier.
All check identifiers in this situation — and the corresponding figures — are listed by the overview of this version.
Application handbook (AHB)
| Structure (EDIFACT) | Description | Format | 55064 | Condition |
|---|---|---|---|---|
| UNH | — | — | Must | — |
006200010 | Message reference number | — | X | — |
0065 UTILMD00020 | Grid connection master data | — | X | — |
0052 D00030 | Draft version | — | X | — |
0054 11A00040 | Edition 2011 - A | — | X | — |
0051 UN00050 | UN/CEFACT | — | X | — |
0057 S2.200060 | Version number of the underlying BDEW message description | — | X | — |
| BGM | — | — | Must | — |
1001 Z0700070 | Activation/ deactivation of MaBiS-ZP | — | X | — |
100400080 | Document number | — | X | — |
| DTM | — | — | Must | — |
2005 13700090 | Document/message date/time | — | X | — |
238000100 | Date or time or time span, value | — | X | [931] [494] |
2379 30300110 | CCYYMMDDHHMMZZZ | — | X | — |
| SG2.NAD | — | — | Must | — |
3035 MS00120 | Document-/ message sender or sender | — | X | — |
303900130 | MP-ID | — | X | — |
3055 900140 | GS1 | — | X | — |
3055 29300150 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
| SG2.NAD | — | — | Must | — |
3035 MR00160 | Message recipient | — | X | — |
303900170 | MP-ID | — | X | [280] |
3055 900180 | GS1 | — | X | — |
3055 29300190 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
| SG4.IDE | — | — | Must | — |
7495 2400200 | Transaction | — | X | — |
740200210 | Transaction number | — | X | — |
| SG4.DTM | — | — | Should | [30] |
2005 15800220 | Start of balancing | — | X | — |
238000230 | Date or time or time span, value | — | X | [UB1] |
2379 30300240 | CCYYMMDDHHMMZZZ | — | X | — |
| SG4.DTM | — | — | Should | [34] |
2005 15900250 | End of balancing | — | X | — |
238000260 | Date or time or time span, value | — | X | [UB1] |
2379 30300270 | CCYYMMDDHHMMZZZ | — | X | — |
| SG4.STS | — | — | Must | [249] |
9015 E0100280 | Status of the response | — | X | — |
901300290 | Code of the check step | — | X | — |
1131 E_000900300 | EBD no. E_0009 | — | X | [233] ∧ [251] ∧ [639] |
1131 E_001000310 | EBD no. E_0010 | — | X | [98] ∧ [233] ∧ [639] |
1131 E_001100320 | EBD no. E_0011 | — | X | [6] ∧ [251] |
1131 E_001200330 | EBD no. E_0012 | — | X | [6] ∧ [251] ∧ [639] |
1131 E_001500340 | EBD no. E_0015 | — | X | [6] ∧ [251] ∧ [640] |
1131 E_001800350 | EBD no. E_0018 | — | X | [233] ∧ [251] |
1131 E_002000360 | EBD no. E_0020 | — | X | [98] ∧ [233] ∧ [640] |
1131 E_002400370 | EBD no. E_0024 | — | X | [233] ∧ [251] ∧ [640] |
1131 E_002700380 | EBD no. E_0027 | — | X | [6] ∧ [251] |
1131 E_002800390 | EBD no. E_0028 | — | X | [6] ∧ [251] |
1131 E_003400400 | EBD no. E_0034 | — | X | [233] ∧ [251] |
1131 E_003500410 | EBD no. E_0035 | — | X | [6] ∧ [251] ∧ [639] |
| SG5.LOC | — | — | Must | — |
3227 Z1500420 | MaBiS metering point | — | X | — |
322500430 | Identifier | — | X | [951] |
| SG6.RFF | — | — | Must | — |
1153 Z1300440 | Check identifier | — | X | — |
1154 5506400450 | MaBiS / Response to activation / deactivation of MaBiS-ZP | — | X | — |
| SG6.RFF | — | — | Must | — |
1153 TN00460 | Transaction reference number | — | X | — |
115400470 | Transaction number | — | X | — |
| UNT | — | — | Must | — |
007400480 | Number of segments in a message | — | X | — |
006200490 | Message reference number | — | X | — |
Conditions of this table
The free text of the 14 conditions referenced by the rows above. All conditions of the message type are listed in the condition index UTILMDS.
| Marker | Condition |
|---|---|
| [6] | If MP-ID in SG2 NAD+MR (message recipient) in the role ÜNB |
| [30] | If a response to the activation is transmitted |
| [34] | If a response to the deactivation is transmitted |
| [98] | If MP-ID in SG2 NAD+MS (message sender) in the role NB |
| [233] | If MP-ID in SG2 NAD+MR (message recipient) in the role NB |
| [249] | Within one SG4 IDE, all DE1131 of the SG4 STS+E01 (status of the response) must contain the identical value |
| [251] | If MP-ID in SG2 NAD+MS (message sender) in the role BIKO |
| [280] | Only MP-ID from the electricity division |
| [494] | The date stated here must be the point in time at which the document was created, or a point in time before that |
| [639] | Note: If response to deactivation |
| [640] | Note: If response to activation |
| [931] | Format: ZZZ = +00 |
| [951] | Format: Metering point identifier |
| [UB1] | ([931] ∧ [932] [490]) ⊻ ([931] ∧ [933] [491]) |
Belongs to these role views
The check identifier itself carries no market role. This assignment is derived back from the role views in whose process steps it occurs — affected are NB, ÜNB, BIKO and BKV.
Business classification
| Attribute | Value |
|---|---|
| Use case (AHB) | Response |
| AHB | UTILMD AHB electricity |
| Decision tree | E_0020 · E_0024 · E_0010 · E_0009 · E_0015 · E_0035 · E_0034 · E_0018 · E_0011 · E_0012 · E_0027 · E_0028 |
| Transmission channel | AS4 |
This check identifier is used in 13 contexts
Regulatory determination and communication direction depend on the process in which the message is sent. A single entry would be misleading — all placements are therefore listed here.
| Process description / rulebook | Process step | Communication | Action |
|---|---|---|---|
| MaBiS | Activation of a MaBiS metering point for the grid time series | NB (neighbouring NB) → NB (responsible NB) | Response |
| MaBiS | Activation of a MaBiS metering point for the grid time series | BIKO → NB (responsible NB) | Response |
| MaBiS | Deactivation of a MaBiS metering point for the grid time series | NB (neighbouring NB) → NB (responsible NB) | Response |
| MaBiS | Deactivation of a MaBiS metering point for the grid time series | BIKO → NB (responsible NB) | Response |
| MaBiS | Activation of a MaBiS metering point for the balancing area aggregate time series from the ÜNB to BIKO and NB | BIKO → ÜNB | Response |
| MaBiS | Deactivation of a MaBiS metering point for the balancing area aggregate time series from the ÜNB to BIKO and NB | BIKO → ÜNB | Response |
| MaBiS | Activation of a MaBiS metering point for the balancing group aggregated time series from the NB to BIKO and BKV | BIKO → NB | Response |
| MaBiS | Deactivation of a MaBiS metering point for the balancing group aggregated time series from the NB to BIKO and BKV | BIKO → NB | Response |
| MaBiS | Activation of a MaBiS metering point for the balancing group aggregated time series from the ÜNB to BIKO and BKV | BIKO → ÜNB | Response |
| MaBiS | Deactivation of a MaBiS metering point for the balancing group aggregated time series from the ÜNB to BIKO and BKV | BIKO → ÜNB | Response |
| MaBiS | Activation of a MaBiS metering point for the delta time series carry-over from the ÜNB to BIKO and NB | BIKO → ÜNB | Response |
| MaBiS | Deactivation of a MaBiS metering point for the delta time series carry-over from the ÜNB to BIKO and NB | BIKO → ÜNB | Response |
| MaBiS | UF MaBiS_005 activation of a MaBiS metering point for the delta time series carry-over from the ÜNB to BIKO and NB | BIKO → ÜNB | Response |
Further relationships from format version 202604
Version 202604 also carries this check identifier in contexts that the table of version 202610 does not know; they are included in the list above. Everything else on this page — use case, rulebook and communication direction — comes from the page's own version. Before adopting it into an implementation specification, check whether what is stated applies to 202610.
Notes on this page
The status column carries two vocabularies because the manual answers two questions: on a group row, Muss, Soll or Kann states whether the EDIFACT segment must be present; on a field row, X states that this qualifier is used in this check identifier. Both are kept exactly as the source records them.
For this check identifier, the application handbook lists 62 rows. They appear in the order of the handbook, indented by segment: a row without a data element opens a segment, the rows below it are its data elements.
The Condition column names the markers under which the handbook ties a row to a prerequisite; their free text is below the table.