Check identifier 55604 — Rejection of registration of new consuming MaLo
Check identifier 55604 · EDIFACT message type UTILMD · format version 202604
Data structure
| Structure (BO4E) | Description | Format | 55604 | Condition |
|---|---|---|---|---|
| stammdaten | — | object | May | — |
| MARKTLOKATION [ ] | — | object[] | May | — |
| marktlokationsId 00010 | Identification number of a market location at which energy is either consumed or generated | 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 | — |
| freitext 00060 | Free text / FTX+ACB | string | X | — |
| kategorie * 00070 | Qualifier from the beginning of the EDIFACT message / BGM | string | X | — |
| nachrichtendatum * 00080 | Creation date of the EDIFact / DTM+137 | string (date-time) | X | — |
| nachrichtenreferenznummer * 00090 | EDIFACT reference from the UNT segment / UTILMD UNT+21 | string | Must | — |
| pruefidentifikator * 00100 | Contains the check identifier from the EDIFact communication / RFF+Z13 | string | X | — |
| transaktionsgrund * 00110 | The transaction reason describes the business transaction for the category in more detail / UTILMD STS+7++###+ZW4+E03 | string | X | — |
| transaktionsgrundergaenzung * 00120 | Supplement to the transaction reason / UTILMD STS+7++E01+###+E03 | string | X | — |
| vorgangsnummer * 00130 | Number of the transaction / UTILMD UTILTS IDE+24 / INSRPT INVOIC DOC | string | X | — |
| absender * | — | object | Must | — |
| rollencodenummer * 00140 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp * 00150 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
| ansprechpartner | — | object | May | — |
| eMailAdresse 00160 | Email address | string | Must | — |
| nachname 00170 | Surname (family name) of the contact person | string | Must | — |
| rufnummern [ ] | — | object[] | May | — |
| nummerntyp 00180 | 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 00190 | rufnummer | string | Must | — |
| beteiligterMarktpartner | — | object | May | — |
| rollencodenummer 00200 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp 00210 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
| empfaenger * | — | object | Must | — |
| rollencodenummer * 00220 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp * 00230 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
Application handbook (AHB)
| Structure (EDIFACT) | Description | Format | 55604 | 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 E0100070 | Registrations | — | 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 E0200310 | Move-in to creation | — | X | — |
9013 ZW400320 | Consuming market location | — | X | — |
| SG4.STS | — | — | Must | [2061] |
9015 E0100330 | Status of the response | — | X | — |
901300340 | Code of the check step | — | X | [359] |
1131 E_060800350 | EBD no. E_0608 | — | X | — |
| SG4.FTX | — | — | Must | [55] |
4451 ACB00360 | Additional information (for general notes) | — | X | — |
444000370 | Text for general information | — | X | — |
| SG5.LOC | — | — | Must | — |
3227 Z1600380 | Market location | — | X | — |
322500390 | ID of the market location | — | X | [950] |
| SG6.RFF | — | — | Must | — |
1153 Z1300400 | Check identifier | — | X | — |
1154 5560400410 | GPKE / Rejection of registration of new consuming market location | — | X | — |
| SG6.RFF | — | — | Must | — |
1153 TN00420 | Transaction reference number | — | X | — |
115400430 | Transaction number | — | X | — |
| SG12.NAD | — | — | Must | — |
3035 VY00440 | other associated party | — | X | — |
303900450 | MP-ID | — | X | — |
3055 900460 | GS1 | — | X | — |
3055 29300470 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | 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 12 conditions referenced by the rows above. All conditions of the message type are listed in the condition index UTILMDS.
| Marker | Condition |
|---|---|
| [55] | If the STS+E01++A06/A99 (status of the response) is present in this SG4 |
| [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 |
| [359] | Only response codes from the rejection cluster are permitted |
| [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 |
| [950] | Format: market location ID |
| [2061] | Segment or segment group must be specified exactly once per SG4 IDE (transaction) |
| [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+9903790000002:500+{{date}}:{{time}}+LZ5VMD3J'
UNH+UNHLZ5RZVR9+UTILMD:D:11A:UN:S2.1'
BGM+E01+BGMLZXL5QSH'
DTM+137:202504041200?+00:303'
NAD+MS+9900321000005::293'
NAD+MR+9903790000002::293'
IDE+24+12345'
STS+7++E02+ZW4'
STS+E01++A01:E_0608'
LOC+Z16+50074561188'
RFF+Z13:55604'
RFF+TN:ABC1234'
UNT+12+UNHLZ5RZVR9'
UNZ+1+LZ5VMD3J'[1 item
{6 fields
"data": {2 fields
"stammdaten": {1 field
"MARKTLOKATION": [1 item
{4 fields
"transaktionsdaten": {15 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 LF and NB.
| Role | Party involved | Process | Rulebook | Division | Step |
|---|---|---|---|---|---|
| LF | LF | Creation | GPKE part 2 | Electricity | Step 3 |
| NB | NB | Creation | GPKE part 2 | Electricity | Step 3 |
Business classification
| Attribute | Value |
|---|---|
| Use case (AHB) | Rejection registration new cons. MaLo |
| AHB | UTILMD AHB electricity |
| Response to check identifier | 55600 |
| Decision tree | E_0608 |
| Transmission channel | AS4 |
| Process description / rulebook | Process step | Communication | Action |
|---|---|---|---|
| GPKE part 2 | Creation | NB → LF | Rejection of the registration of an assignment of the LF to the market location or tranche |
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 names a polarity (rejection).
Which request this message responds to
| Role | Check identifier | Use case | Message type | Origin of supply |
|---|---|---|---|---|
| Request | 55600 | Registration of new cons. MaLo | UTILMD | explicit, not adjacent |
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: 55600 lists vorgangsnummer in SG4.IDE+24.
Response codes
Decision tree E_0608 — named in: AHB STS DE1131 and Prüfi table.
Only the codes from the rejection cluster are shown: the tree carries both clusters, the handbook of this check identifier names exactly this one tree, and the title is polar (rejection). If one of the three conditions were missing, all codes would be listed here with their label.
| Response code | Cluster | Meaning | Outputs |
|---|---|---|---|
| A01 | Rejection | Lead time was not met | 1 |
| A02 | Rejection | Identified market location does not take part in market communication. Furthermore, this is not a creation. | 1 |
| A08 | Rejection | No or multiple identification | 1 |
| A03 | Rejection | Not a creation, wrong use case | 1 |
| A04 | Rejection | Incorrect use case, a LF is already assigned | 1 |
| A05 | Rejection | As of the receipt date of the notification, the market location is no longer in the grid area of the NB. | 1 |
| A06 | Rejection | Requirements cannot be met Note: The deviations must be named. | 1 |
| A07 | Rejection | Newly created market locations could not be identified | 1 |
| A99 | Rejection | Other Note: The identified problem is to be described/named in the response. End of usability: 01.10.2026 00:00 | 2 |
| A10 | Rejection | Lead time was not met | 1 |
| A11 | Rejection | Identified market location does not take part in market communication. Furthermore, this is not a creation. | 1 |
| A17 | Rejection | No or multiple identification | 1 |
| A12 | Rejection | Not a creation, wrong use case | 1 |
| A19 | Rejection | Not all measuring devices required to determine the energy quantity of the market location are equipped with the metering technology for quarter-hourly measurement. | 1 |
| A13 | Rejection | Incorrect use case, a LF is already assigned | 1 |
| A14 | Rejection | As of the receipt date of the notification, the market location is no longer in the grid area of the NB. | 1 |
| A15 | Rejection | Requirements cannot be met Note: The deviations must be named. | 1 |
| A16 | Rejection | Newly created market locations could not be identified | 1 |
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 65 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.