Check identifier 17113 — Complaint about values
Check identifier 17113 · EDIFACT message type ORDERS · Format version 202610
Data structure
| Structure (BO4E) | Description | Format | 17113 | Condition |
|---|---|---|---|---|
| stammdaten * | — | object | Must | — |
| ANFRAGE [ ] * | — | object[] | Must | — |
| anfragetyp * 00010 | Type/kind of the request (ORDERS ORDRSP IMD 7081) | Enum Anfragetyp | Must | — |
KAUF | — | — | Must | — |
NUTZUNGSUEBERLASSUNG | — | — | Must | — |
ABRECHNUNGSBRENNWERT_UND_ZUSTANDSZAHL | — | — | Must | — |
LASTGANGDATEN | — | — | Must | — |
ZAEHLERSTAENDE | — | — | Must | — |
WERTEERMITTLUNG | — | — | Must | — |
ENERGIEMENGE_EINZELWERT | — | — | Must | — |
INNERHALB_DER_ARBEITSZEIT | — | — | Must | — |
AUCH_AUSSERHALB_DER_ARBEITSZEIT | — | — | Must | — |
WECHSEL_SAEMTLICHER_EINRICHTUNGEN | — | — | Must | — |
TEILWEISER_WECHSEL | — | — | Must | — |
AENDERUNG_ZAEHLZEITDEFINITION | — | — | Must | — |
ABBESTELLUNG_ZAEHLZEITEN | — | — | Must | — |
ABBESTELLUNG_MESSPRODUKT | — | — | Must | — |
ANGEBOT_AUF_BASIS_PREISBLATT | — | — | Must | — |
INDIVIDUELLES_ANGEBOT | — | — | Must | — |
AENDERUNG_KONFIGURATION | — | — | Must | — |
KANN_NICHT_ANGEBOTEN_WERDEN | — | — | Must | — |
NEUKONFIGURATION | — | — | Must | — |
BEENDIGUNG_KONFIGURATION | — | — | Must | — |
AKTIVIERUNG_KONFIGURATION | — | — | Must | — |
| AUFTRAG [ ] * | — | object[] | Must | — |
| positionsdaten [ ] * | — | object[] | Must | — |
| gueltigAb 00020 | gueltigAb | string (date-time) | X | — |
| positionsnummer * 00030 | Line item number | integer | Must | — |
| REKLAMATION [ ] * | — | object[] | Must | — |
| konfiguration 00040 | konfiguration | string | X | — |
| lokationsId 00050 | Which market or metering location this complaint applies to. | string | X | — |
| obiskennzahl * 00060 | OBIS code | string | X | — |
| reklamationsgrund * 00070 | This specifies the reason for the complaint about values. | Enum Reklamationsgrund | Must | — |
WERTE_ZU_HOCH | — | — | Must | — |
WERTE_ZU_NIEDRIG | — | — | Must | — |
WERTE_FEHLEN | — | — | Must | — |
KONFIGURATION_WIRKT_NICHT | — | — | Must | — |
KONFIGURATION_WIRKT_TEILWEISE | — | — | Must | — |
WERTE_WERDEN_NICHT_NACH_VORGABEN_UEBERMITTELT | — | — | Must | — |
UEBERSICHT_FEHLT | — | — | Must | — |
UEBERSICHT_UNPLAUSIBEL | — | — | Must | — |
AUSGEROLLTE_DEFINITION_FEHLT | — | — | Must | — |
AUSGEROLLTE_DEFINITION_UNPLAUSIBEL | — | — | Must | — |
| reklamationsgrundBemerkung | — | object | May | — |
| bemerkung1 00080 | bemerkung1 | string | Must | — |
| bemerkung2 00090 | bemerkung2 | string | Must | — |
| bemerkung3 00100 | bemerkung3 | string | Must | — |
| bemerkung4 00110 | bemerkung4 | string | Must | — |
| bemerkung5 00120 | bemerkung5 | string | Must | — |
| zeitraumMesswertanfrage | — | object | May | — |
| enddatum 00130 | enddatum | string (date-time) | X | — |
| startdatum 00140 | startdatum | string (date-time) | X | — |
| transaktionsdaten * | — | object | Must | — |
| angebotsreferenz 00150 | Reference number of a preceding message / ORDERS RFF+ACW | string | X | — |
| dokumentennummer * 00160 | EDIFACT reference from the BGM segment / BGM | string | X | — |
| nachrichtendatum * 00170 | Creation date of the EDIFact / DTM+137 | string (date-time) | X | — |
| nachrichtenreferenznummer * 00180 | EDIFACT reference from the UNT segment / UTILMD UNT+21 | string | Must | — |
| pruefidentifikator * 00190 | Contains the check identifier from the EDIFact communication / RFF+Z13 | string | X | — |
| absender * | — | object | Must | — |
| 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 | — |
| ansprechpartner * | — | object | Must | — |
| eMailAdresse 00220 | Email address | string | Must | — |
| nachname * 00230 | Surname (family name) of the contact person | string | X | — |
| rufnummern [ ] | — | object[] | May | — |
| nummerntyp 00240 | 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 00250 | rufnummer | string | Must | — |
| empfaenger * | — | object | Must | — |
| rollencodenummer * 00260 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp * 00270 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
Application handbook (AHB)
| Structure (EDIFACT) | Description | Format | 17113 | Condition |
|---|---|---|---|---|
| UNH | — | — | Must | — |
006200010 | Message reference number | — | X | — |
0065 ORDERS00020 | Order placement | — | X | — |
0052 D00030 | Draft version | — | X | — |
0054 09B00040 | Edition 2009 - B | — | X | — |
0051 UN00050 | UN/CEFACT | — | X | — |
0057 1.4c00060 | Version number of the underlying BDEW message description | — | X | — |
| BGM | — | — | Must | — |
1001 Z3400070 | Complaint about values | — | 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 | — |
| IMD | — | — | Must | — |
7081 Z1100120 | Load curve data | — | X | — |
7081 Z1200130 | Meter readings | — | X | — |
7081 Z3500140 | Energy quantity single value | — | X | — |
| SG1.RFF | — | — | Must | — |
1153 ACW00150 | Reference number of a preceding message | — | X | — |
115400160 | Message number | — | X | [525] |
| SG1.RFF | — | — | Must | — |
1153 Z1300170 | Check identifier | — | X | — |
1154 1711300180 | Notification of a complaint about values | — | X | — |
| SG2.NAD | — | — | Must | — |
3035 MS00190 | Document-/message sender or sender | — | X | — |
303900200 | MP-ID | — | X | [61] |
3055 900210 | GS1 | — | X | — |
3055 29300220 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
| SG5.CTA | — | — | Must | — |
3139 IC00230 | Information contact | — | X | — |
341200240 | Contact | — | X | — |
| SG5.COM | — | — | Must | — |
314800250 | Communication address, identification | — | X | (([939] [147]) ⊻ ([940] [148])) ∧ [567] |
3155 EM00260 | Electronic mail | — | X | [1P0..1] |
3155 FX00270 | Fax number | — | X | [1P0..1] |
3155 TE00280 | Telephone | — | X | [1P0..1] |
3155 AJ00290 | further telephone | — | X | [1P0..1] |
3155 AL00300 | Mobile phone | — | X | [1P0..1] |
| SG2.NAD | — | — | Must | — |
3035 MR00310 | Message recipient | — | X | — |
303900320 | MP-ID | — | X | [61] |
3055 900330 | GS1 | — | X | — |
3055 29300340 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
| SG2.NAD | — | — | Must | — |
3035 DP00350 | Supply address | — | X | — |
| SG2.LOC | — | — | Must | [24] ⊻ [18] ⊻ ([108] ∧ [19]) |
3227 17200360 | Reporting point | — | X | — |
322500370 | Identifier | — | X | (([950] [521] ∧ ([6] ⊻ [7] ⊻ [26])) ⊻ ([951] [522] ∧ ([6] ⊻ [7] ⊻ [15])) ⊻ ([950] [523] ∧ ([6] ⊻ [7] ⊻ [26]))) |
| SG3.RFF | — | — | Must | — |
1153 AGK00380 | Application reference number | — | X | — |
115400390 | Configuration ID | — | X | — |
| SG29.LIN | — | — | Must | — |
108200400 | Line item number | — | X | [911] |
| SG29.PIA | — | — | Must | — |
4347 500410 | Product identification | — | X | — |
714000420 | OBIS code | — | X | — |
7143 SRW00430 | OBIS code | — | X | — |
| SG29.DTM | — | — | Must | [19] ∧ [67] ∧ [549] |
2005 700440 | Effective date/time | — | X | — |
238000450 | Date or time or time span, value | — | X | [931] |
2379 30300460 | CCYYMMDDHHMMZZZ | — | X | — |
| SG29.DTM | — | — | Must | [18] ⊻ [24] ⊻ ([19] ∧ [54] ∧ [68] ∧ [550]) |
2005 16300470 | Processing, start date/time | — | X | — |
238000480 | Date or time or time span, value | — | X | [931] |
2379 30300490 | CCYYMMDDHHMMZZZ | — | X | — |
| SG29.DTM | — | — | Must | [110] |
2005 16400500 | Processing, end date/time | — | X | — |
238000510 | Date or time or time span, value | — | X | [931] |
2379 30300520 | CCYYMMDDHHMMZZZ | — | X | — |
| SG29.FTX | — | — | Must | — |
4451 Z0400530 | Values too high in the specified time interval | — | X | — |
4451 Z0500540 | Values too low in the specified time interval | — | X | — |
4451 Z0600550 | Values missing in the specified time interval | — | X | — |
444000560 | Description of the complaint | — | — | — |
| UNS | — | — | Must | — |
0081 S00570 | Separation of detail and summary section | — | X | — |
| UNT | — | — | Must | — |
007400580 | Number of segments in a message | — | X | — |
006200590 | Message reference number | — | X | — |
Conditions of this table
The free text of the 30 conditions referenced by the rows above. All conditions of the message type are listed in the condition index ORDERS.
| Marker | Condition |
|---|---|
| [6] | If MP-ID in SG2 NAD+MS with role LF is present |
| [7] | If MP-ID in SG2 NAD+MS with role NB is present |
| [15] | If MP-ID in SG2 NAD+MS with role MSB is present |
| [18] | If IMD++Z11 present |
| [19] | If IMD++Z12 present |
| [24] | If IMD++Z35 present |
| [26] | If MP-ID in SG2 NAD+MS with role ÜNB is present |
| [54] | If FTX+Z06 present |
| [61] | MP-ID only from division electricity |
| [67] | If DTM+163 not present |
| [68] | If DTM+7 not present |
| [108] | If RFF+AGK (configuration ID) not present |
| [110] | If DTM+163 (start of time period for value request) present |
| [147] | If code EM is present in DE3155 in the same COM |
| [148] | 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. |
| [521] | Note: Use of the ID of the market location |
| [522] | Note: Use of the ID of the metering location |
| [523] | Note: Use of the ID of the tranche |
| [525] | Note: Value from BGM DE1004 of the MSCONS |
| [549] | Note: Always applies to the complaint about meter readings. The only exception is a complaint about a missing meter reading due to a periodic meter reading for which the MSB had transmitted the information on the "planned periodic meter reading of the MSB (electricity)" at the object of the market location in the UTILMD in SG6 DTM+752 as the reading period (DE2379 with code 104 MMWW-MMWW) in the previous master data, because in that case no point in time can be specified and the time interval in the segment form DTM+163 / DTM+164 must be used. |
| [550] | Note: Applies only if it is a complaint about a missing meter reading due to a periodic meter reading for which the MSB had transmitted the information on the "planned periodic meter reading of the MSB (electricity)" at the object of the market location in the UTILMD in SG6 DTM+752 as the reading period (DE2379 with code 104 MMWW-MMWW) in the previous master data. |
| [567] | Note: Only one piece of information may be transmitted in DE3148 |
| [911] | Format: Possible values: 1 to n, starting at 1 for each message or segment group and ascending consecutively |
| [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 |
| [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+9903111000003:500+9904629000006:500+{{date}}:{{time}}+M0OYS007'
UNH+M104QEDN+ORDERS:D:09B:UN:1.4c'
BGM+Z34+M0HC9M6V'
DTM+137:202610011100?+00:303'
IMD++Z11'
RFF+ACW:12345'
RFF+Z13:17113'
NAD+MS+9903111000003::293'
CTA+IC+:Andre Laue'
COM+marktpartner @stromnetz-hamburg.de:EM'
NAD+MR+9904629000006::293'
NAD+DP'
LOC+172+55123678945'
LIN+1'
PIA+5+1?:1.1.9.0:SRW'
DTM+163:202604282200?+00:303'
DTM+164:202608112200?+00:303'
FTX+Z04'
UNS+S'
UNT+19+M104QEDN'
UNZ+1+M0OYS007'[1 item
{6 fields
"data": {3 fields
"stammdaten": {3 fields
"ANFRAGE": [1 item
{4 fields
"AUFTRAG": [1 item
{3 fields
"positionsdaten": [1 item
{1 field
"REKLAMATION": [1 item
{7 fields
"zeitraumMesswertanfrage": {2 fields
"transaktionsdaten": {9 fields
"absender": {6 fields
"ansprechpartner": {4 fields
"empfaenger": {5 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, NB, MSB and ÜNB.
| Role | Party involved | Process | Rulebook | Division | Step |
|---|---|---|---|---|---|
| LF | LF | Complaint from the LF | WiM electricity part 2 | Electricity | Step 1 |
| LF | LF | Complaint from the LF | WiM electricity part 2 | Electricity | Step 5 |
| NB | NB | Complaint from the NB | WiM electricity part 2 | Electricity | Step 1 |
| NB | NB | Complaint from the NB | WiM electricity part 2 | Electricity | Step 5 |
| MSB | MSB-MALO | MSB of the market location identifies the need for a complaint itself | WiM electricity part 2 | Electricity | Step 3 |
| MSB | MSB-MALO | Complaint from the LF | WiM electricity part 2 | Electricity | Step 1 |
| MSB | MSB-MALO | Complaint from the LF | WiM electricity part 2 | Electricity | Step 5 |
| MSB | MSB-MALO | Complaint from the NB | WiM electricity part 2 | Electricity | Step 1 |
| MSB | MSB-MALO | Complaint from the NB | WiM electricity part 2 | Electricity | Step 5 |
| MSB | MSB-MALO | Complaint from the ÜNB | WiM electricity part 2 | Electricity | Step 1 |
| MSB | MSB-MALO | Complaint from the ÜNB | WiM electricity part 2 | Electricity | Step 5 |
| MSB | MSB-MELO | MSB of the market location identifies the need for a complaint itself | WiM electricity part 2 | Electricity | Step 3 |
| MSB | MSB-MELO | Complaint from the LF | WiM electricity part 2 | Electricity | Step 1 |
| MSB | MSB-MELO | Complaint from the LF | WiM electricity part 2 | Electricity | Step 5 |
| MSB | MSB-MELO | Complaint from the NB | WiM electricity part 2 | Electricity | Step 1 |
| MSB | MSB-MELO | Complaint from the NB | WiM electricity part 2 | Electricity | Step 5 |
| MSB | MSB-MELO | Complaint from the ÜNB | WiM electricity part 2 | Electricity | Step 1 |
| MSB | MSB-MELO | Complaint from the ÜNB | WiM electricity part 2 | Electricity | Step 5 |
| ÜNB | ÜNB | Complaint from the ÜNB | WiM electricity part 2 | Electricity | Step 1 |
| ÜNB | ÜNB | Complaint from the ÜNB | WiM electricity part 2 | Electricity | Step 5 |
Business classification
| Attribute | Value |
|---|---|
| Use case (AHB) | Complaint about values |
| AHB | ORDERS AHB |
| Transmission channel | AS4 |
This check identifier is used in 8 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 |
|---|---|---|---|
| WiM electricity part 2 | Complaint from the NB | NB → MSB (corresponds to MSB on the market location object) | Complaint value |
| WiM electricity part 2 | Complaint from the NB | MSB (corresponds to MSB on the object market location) → MSB (corresponds to MSB on the object metering location) | Complaint value of a metering location |
| WiM electricity part 2 | Complaint from the LF | LF → MSB (corresponds to MSB on the market location object) | Complaint value |
| WiM electricity part 2 | Complaint from the LF | MSB (corresponds to MSB on the object market location) → MSB (corresponds to MSB on the object metering location) | Complaint value of a metering location |
| WiM electricity part 2 | Complaint from the ÜNB | ÜNB → MSB (corresponds to MSB on the market location object) | Complaint value |
| WiM electricity part 2 | Complaint from the ÜNB | MSB (corresponds to MSB on the object market location) → MSB (corresponds to MSB on the object metering location) | Complaint value of a metering location |
| WiM electricity part 2 | MSB of the market location itself identifies a need for complaint | MSB (corresponds to MSB on the object market location) → MSB (corresponds to MSB on the object metering location) | Complaint value of a metering location |
| WiM gas | Ch. C 4.3.3.2 No. 1 | LF → NB | Notification of a complaint |
Individual entries from format version 202604
The check identifiers table of format version 202610 does not carry this entry: process step. It comes from 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 its own version. Before adopting this into an implementation specification, check whether what is stated applies to 202610.
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 | 19114 | Rejection of complaint | ORDRSP | 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 ORDERS has the same row structure in this version.
Editorial — not derived from a source
What the complaint refers to. The complaint cites the disputed message via RFF+ACW (reference number of a previous message), in the JSON transaktionsdaten.angebotsreferenz (SG1.RFF+ACW). It carries no anfrageReferenz (RFF+AGI): only the meter reading messages (MSCONS), IFTSTA 21042 to 21044 and UTILTS 25004 to 25009 carry one. Example from the test set (17113): RFF+ACW:ABC1234.
Source: ORDERS AHB (Knowledge Collection ahb/202604/ORDERS/17113.json and ahb/202610/ORDERS/17113.json, SG1 RFF+ACW); specification PI_17113 (segment mapping of angebotsreferenz); test set maco-edi-testfiles, inbound/v202404/ORDERS/17113_eingehend.edi · As of: 2026-09-23 · Applies to format version: 202604, 202610 · To be reviewed by: 2027-04-01
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 80 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 orders. 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.