Check identifier 55053 — Rejection of end MSB
Check identifier 55053 · EDIFACT message type UTILMD · Format version 202604
Data structure
| Structure (BO4E) | Description | Format | 55053 | 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 | — |
| transaktionsdaten * | — | object | Must | — |
| anfragereferenznummer * 00020 | Reference transaction number 'from request message' / ORDERS RFF+TN / IFTSTA RFF+AAV / INSRPT RFF+TN RFF+AAV | string | X | — |
| antwortstatus * 00030 | Response status / STS+E01 | string | X | — |
| antwortstatusCodeliste * 00040 | Response status code list / STS+E01 | string | X | — |
| dokumentennummer * 00050 | EDIFACT reference from the BGM segment / BGM | string | X | — |
| kategorie * 00060 | Qualifier from the beginning of the EDIFACT message / BGM | string | X | — |
| nachrichtendatum * 00070 | Creation date of the EDIFact / DTM+137 | string (date-time) | X | — |
| nachrichtenreferenznummer * 00080 | EDIFACT reference from the UNT segment / UTILMD UNT+21 | string | Must | — |
| pruefidentifikator * 00090 | Contains the check identifier from the EDIFact communication / RFF+Z13 | string | X | — |
| transaktionsgrund * 00100 | The transaction reason describes the business transaction for the category in more detail / UTILMD STS+7++###+ZW4+E03 | string | X | — |
| vorgangsnummer * 00110 | Number of the transaction / UTILMD UTILTS IDE+24 / INSRPT INVOIC DOC | string | X | — |
| absender * | — | object | Must | — |
| rollencodenummer * 00120 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp * 00130 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
| ansprechpartner | — | object | May | — |
| eMailAdresse 00140 | Email address | string | Must | — |
| nachname 00150 | Surname (family name) of the contact person | string | Must | — |
| rufnummern [ ] | — | object[] | May | — |
| nummerntyp 00160 | Phone number type | Enum Rufnummernart | Must | — |
RUF_ZENTRALE | — | — | Must | — |
FAX_ZENTRALE | — | — | Must | — |
SAMMELRUF | — | — | Must | — |
SAMMELFAX | — | — | Must | — |
ABTEILUNGRUF | — | — | Must | — |
ABTEILUNGFAX | — | — | Must | — |
RUF_DURCHWAHL | — | — | Must | — |
FAX_DURCHWAHL | — | — | Must | — |
MOBIL_NUMMER | — | — | Must | — |
| rufnummer 00170 | rufnummer | string | Must | — |
| empfaenger * | — | object | Must | — |
| rollencodenummer * 00180 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp * 00190 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
Application handbook (AHB)
| Structure (EDIFACT) | Description | Format | 55053 | 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.100060 | 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 | — |
| SG3.CTA | — | — | Must | — |
3139 IC00160 | Information contact | — | X | — |
341200170 | Name of the contact person | — | X | — |
| SG3.COM | — | — | Must | — |
314800180 | Number / address | — | X | (([939] [321]) ∨ ([940] [322])) ∧ [514] |
3155 EM00190 | Electronic mail | — | X | [1P0..1] |
3155 FX00200 | Fax number | — | X | [1P0..1] |
3155 TE00210 | Telephone | — | X | [1P0..1] |
3155 AJ00220 | further telephone | — | X | [1P0..1] |
3155 AL00230 | Mobile phone | — | X | [1P0..1] |
| SG2.NAD | — | — | Must | — |
3035 MR00240 | Message recipient | — | X | — |
303900250 | MP-ID | — | X | — |
3055 900260 | GS1 | — | X | — |
3055 29300270 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
| SG4.IDE | — | — | Must | — |
7495 2400280 | Transaction | — | X | — |
740200290 | Transaction number | — | X | — |
| SG4.STS | — | — | Must | — |
9015 700300 | Transaction reason | — | X | — |
9013 E0100310 | Move-in/move-out (relocation) | — | X | — |
9013 E0300320 | Change | — | X | — |
9013 Z3300330 | Move-out due to decommissioning | — | X | — |
9013 ZG900340 | Revocation of a future assignment due to the customer moving out | — | X | — |
9013 ZH100350 | Revocation of a future assignment due to decommissioning | — | X | — |
9013 ZH200360 | Revocation of a future assignment due to a revoked contractual relationship | — | X | — |
| SG4.STS | — | — | Must | [249] |
9015 E0100370 | Status of the response | — | X | — |
901300380 | Code of the check step | — | X | — |
1131 S_006000390 | Electricity code list no. S_0060 | — | X | — |
| SG5.LOC | — | — | Must | — |
3227 Z1700400 | Metering location | — | X | — |
322500410 | ID of the metering location | — | X | [951] |
| SG6.RFF | — | — | Must | — |
1153 Z1300420 | Check identifier | — | X | — |
1154 5505300430 | WiM electricity / rejection of end MSB | — | X | — |
| SG6.RFF | — | — | Must | — |
1153 TN00440 | Transaction reference number | — | X | — |
115400450 | Transaction number | — | X | — |
| UNT | — | — | Must | — |
007400460 | Number of segments in a message | — | X | — |
006200470 | Message reference number | — | X | — |
Conditions of this table
The free text of the 10 conditions referenced by the rows above. All conditions of the message type are listed in the condition index UTILMDS.
| Marker | Condition |
|---|---|
| [249] | Within one SG4 IDE, all DE1131 of the SG4 STS+E01 (status of the response) must contain the identical value |
| [321] | If code EM is present in DE3155 in the same COM |
| [322] | If code TE / FX / AJ / AL is present in DE3155 in the same COM |
| [494] | The date stated here must be the point in time at which the document was created, or a point in time before that |
| [514] | Note: Only one piece of information may be transmitted in DE3148 |
| [931] | Format: ZZZ = +00 |
| [939] | Format: the character string must contain the characters @ and . |
| [940] | Format: the character string must begin with the character + and may only be followed by digits |
| [951] | Format: Metering point identifier |
| [1P0..1] | Note: This is the standard package if no condition applies, e.g. in the COM segment. |
Example message
UNA:+.? '
UNB+UNOC:3+9900321000005:500+9904446000007:500+{{date}}:{{time}}+545603'
UNH+324283+UTILMD:D:11A:UN:S2.1'
BGM+E02+324283BGM'
DTM+137:202504040947?+00:303'
NAD+MS+9900321000005::293'
CTA+IC+:Mustermann'
COM+?+2345678910:AJ'
NAD+MR+9904446000007::293'
IDE+24+1981499403'
STS+7++E03'
STS+E01++Z09:S_0060'
LOC+Z17+DE0032106765712000000000000000037'
RFF+Z13:55053'
RFF+TN:REF12345678910'
UNT+14+324283'
UNZ+1+545603'[1 item
{6 fields
"data": {2 fields
"stammdaten": {1 field
"MESSLOKATION": [1 item
{4 fields
"transaktionsdaten": {14 fields
"absender": {5 fields
"ansprechpartner": {4 fields
"rufnummern": [1 item
{2 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 2 |
| MSB | GMSB | End of metering point operation | WiM electricity part 1 | Electricity | Step 2 |
| MSB | MSBA | End of metering point operation | WiM electricity part 1 | Electricity | Step 2 |
Business classification
| Attribute | Value |
|---|---|
| Use case (AHB) | Rejection end MSB |
| AHB | UTILMD AHB electricity |
| Decision tree | E_0202 |
| Transmission channel | AS4 |
| Process description / rulebook | Process step | Communication | Action |
|---|---|---|---|
| WiM electricity part 1 | End of metering point operation | NB → MSB (corresponds to MSBA on the metering location object) | Response to deregistration |
One entry from format version 202610
The check identifiers table of format version 202604 does not carry this entry: decision tree. It comes from version 202610. Everything else on this page — use case, rulebook and communication direction — comes from its own version. Before adopting this into an implementation specification, check whether what is stated applies to 202604.
Transaction and responses
Role of this check identifier: response — rejection. Basis: the transaction data carry antwortstatus and antwortstatusCodeliste; the title or the action of the Prüfi table begins with “response”; the title names a polarity (rejection).
Which request this message responds to
| Role | Check identifier | Use case | Message type | Origin of supply |
|---|---|---|---|---|
| Request | 55051 | End of MSB | UTILMD | from the step sequence |
In which field the request is quoted
| Reference field of this message | EDIFACT segment | Target field in the request |
|---|---|---|
anfragereferenznummer | SG4.IDE+24.SG6.RFF+TN | vorgangsnummer |
For RFF+TN, the time slice field description gives »reference transaction number (from request message)« — the target is the vorgangsnummer in segment SG4.IDE+24 of the request. Measured: 55051 lists vorgangsnummer in SG4.IDE+24.
Response codes
Decision trees: S_0060 · E_0202.
The Prüfi table names one further tree across all rows of this check identifier. They tie it to a process, not to a row of its handbook — their codes are therefore only on the respective tree page. For S_0060 there is no decision tree in version 202604; its response codes are therefore not given here.
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 61 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.