Check identifier 55051 — End MSB
Check identifier 55051 · EDIFACT message type UTILMD · Format version 202610
Data structure
| Structure (BO4E) | Description | Format | 55051 | Condition |
|---|---|---|---|---|
| stammdaten * | — | object | Must | — |
| MESSLOKATION [ ] * | — | object[] | Must | — |
| messlokationsId * 00010 | The metering location identification. This is the former metering point identifier, e.g. DE 47108151234567 | string | X | — |
| NETZNUTZUNGSVERTRAG [ ] | — | object[] | May | — |
| vertragsbeginn 00020 | Specifies when the contract begins. | string (date-time) | X | — |
| vertragsende 00030 | Specifies when the contract (is expected to) end or was ended. | string (date-time) | X | — |
| transaktionsdaten * | — | object | Must | — |
| dokumentennummer * 00040 | EDIFACT reference from the BGM segment / BGM | string | X | — |
| kategorie * 00050 | Qualifier from the beginning of the EDIFACT message / BGM | string | X | — |
| nachrichtendatum * 00060 | Creation date of the EDIFact / DTM+137 | string (date-time) | X | — |
| nachrichtenreferenznummer * 00070 | EDIFACT reference from the UNT segment / UTILMD UNT+21 | string | Must | — |
| pruefidentifikator * 00080 | Contains the check identifier from the EDIFact communication / RFF+Z13 | string | X | — |
| transaktionsgrund * 00090 | The transaction reason describes the business transaction for the category in more detail / UTILMD STS+7++###+ZW4+E03 | string | X | — |
| vertragsbeginn 00100 | Contract start date / DTM+92 | string (date-time) | X | — |
| vertragsende 00110 | Contract end date / DTM+93 | string (date-time) | X | — |
| vorgangsnummer * 00120 | Number of the transaction / UTILMD UTILTS IDE+24 / INSRPT INVOIC DOC | string | X | — |
| absender * | — | object | Must | — |
| rollencodenummer * 00130 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp * 00140 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
| empfaenger * | — | object | Must | — |
| rollencodenummer * 00150 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp * 00160 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
Application handbook (AHB)
| Structure (EDIFACT) | Description | Format | 55051 | 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 E0200070 | Deregistrations | — | 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 | — |
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 | — | — | Must | [7] ∧ [577] |
2005 9200220 | Contract start date | — | X | — |
238000230 | Date or time or time span, value | — | X | [UB1] |
2379 30300240 | CCYYMMDDHHMMZZZ | — | X | — |
| SG4.DTM | — | — | Must | [11] |
2005 9300250 | Contract end date | — | X | — |
238000260 | Date or time or time span, value | — | X | [UB1] |
2379 30300270 | CCYYMMDDHHMMZZZ | — | X | — |
| SG4.STS | — | — | Must | — |
9015 700280 | Transaction reason | — | X | — |
9013 E0100290 | Move-in/move-out (relocation) | — | X | — |
9013 E0300300 | Change | — | X | — |
9013 Z3300310 | Move-out due to decommissioning | — | X | — |
9013 ZG900320 | Revocation of a future assignment due to the customer moving out | — | X | — |
9013 ZH100330 | Revocation of a future assignment due to decommissioning | — | X | — |
9013 ZH200340 | Revocation of a future assignment due to a revoked contractual relationship | — | X | — |
| SG5.LOC | — | — | Must | — |
3227 Z1700350 | Metering location | — | X | — |
322500360 | ID of the metering location | — | X | [951] |
| SG6.RFF | — | — | Must | — |
1153 Z1300370 | Check identifier | — | X | — |
1154 5505100380 | WiM electricity / end MSB | — | X | — |
| UNT | — | — | Must | — |
007400390 | Number of segments in a message | — | X | — |
006200400 | Message reference number | — | X | — |
Conditions of this table
The free text of the 7 conditions referenced by the rows above. All conditions of the message type are listed in the condition index UTILMDS.
| Marker | Condition |
|---|---|
| [7] | If SG4 STS+7++ZG9/ZH1/ZH2 (transaction reason: cancellation of a future assignment due to move-out of the customer / -due to decommissioning / -due to cancelled contractual relationship) is present |
| [11] | If SG4 STS+7++ZG9/ZH1/ZH2 (transaction reason: cancellation of a future assignment due to move-out of the customer / -due to decommissioning / -due to cancelled contractual relationship) is not present |
| [494] | The date stated here must be the point in time at which the document was created, or a point in time before that |
| [577] | Note: Filled with the start point in time originally confirmed by the NB |
| [931] | Format: ZZZ = +00 |
| [951] | Format: Metering point identifier |
| [UB1] | ([931] ∧ [932] [490]) ⊻ ([931] ∧ [933] [491]) |
Example message
UNA:+.? '
UNB+UNOC:3+9904446000007:500+9900321000005:500+{{date}}:{{time}}+LZKDBRDN'
UNH+UNHLZ9YBIAK+UTILMD:D:11A:UN:S2.2'
BGM+E02+BGMLZQ8B5SN'
DTM+137:202504041200?+00:303'
NAD+MS+9904446000007::293'
NAD+MR+9900321000005::293'
IDE+24+123456'
DTM+93:202506302200?+00:303'
STS+7++E03'
LOC+Z17+DE0032106765712000000000000000037'
RFF+Z13:55051'
UNT+11+UNHLZ9YBIAK'
UNZ+1+LZKDBRDN'[1 item
{6 fields
"data": {2 fields
"stammdaten": {2 fields
"MESSLOKATION": [1 item
{4 fields
"NETZNUTZUNGSVERTRAG": [1 item
{5 fields
"transaktionsdaten": {12 fields
"absender": {4 fields
"empfaenger": {4 fields
Download: EDIFACT file · BO4E JSON
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 and MSB.
| Role | Party involved | Process | Rulebook | Division | Step |
|---|---|---|---|---|---|
| NB | NB | End of metering point operation | WiM electricity part 1 | Electricity | Step 1 |
| MSB | GMSB | End of metering point operation | WiM electricity part 1 | Electricity | Step 1 |
| MSB | MSBA | End of metering point operation | WiM electricity part 1 | Electricity | Step 1 |
Business classification
| Attribute | Value |
|---|---|
| Use case (AHB) | End of MSB |
| AHB | UTILMD AHB electricity |
| Transmission channel | AS4 |
| Process description / rulebook | Process step | Communication | Action |
|---|---|---|---|
| WiM electricity part 1 | End of metering point operation | MSB (corresponds to MSBA on the object metering location) → NB | Deregistration |
Transaction and responses
Role of this check identifier: request. Basis: the transaction data carry neither antwortstatus nor antwortstatusCodeliste, and neither the title nor the action of the Prüfi table begins with “response” or “response message”.
Which messages respond to this
| Role | Check identifier | Use case | Message type | Origin of supply |
|---|---|---|---|---|
| Response | 55052 | Confirmation of end of MSB | UTILMD | from the step sequence |
| Response | 55053 | Rejection end MSB | UTILMD | from the step sequence |
This column is the inverse of the assignment on the response pages — not the next step of a list. The process source says of its own steps that they are »possible messages, not a sequence«.
Check identifiers of the same AHB table: No other check identifier of message type UTILMDS has the same row structure in this version.
Notes on this page
An * after a field or group name marks a mandatory field or a mandatory group. The type is beside it; where the value ends up in the EDIFACT segment is shown by the info icon next to the field name.
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 52 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.
The test data contains one transaction for this check identifier under the message type utilmd. Each is stored twice — as a EDIFACT message and as a BO4E JSON. That both representations show the same transaction has been recalculated, not assumed: interchange control reference, message reference number, document number, message date, sender and recipient match in all 517 pairs of the format version; check identifier, transaction number and location ID wherever both representations carry them. Not a single attribute contradicts.
Placeholder from the test data set
The test data set carries placeholders instead of valid values: {{date}} and {{time}} in the UNB interchange envelope of every EDIFACT file. The page replaces these on call with the current date and the current time — in the format that applies at the respective position: in the envelope year, month and day as well as hour and minute, two digits each.
<businessKey> stays in place. It is not a time value, and an invented key would look like a valid one.