Check identifier 17102 — Request of values
Check identifier 17102 · EDIFACT message type ORDERS · Format version 202604
Data structure
| Structure (BO4E) | Description | Format | 17102 | Condition |
|---|---|---|---|---|
| stammdaten * | — | object | Must | — |
| ANFRAGE [ ] * | — | object[] | Must | — |
| anfragekategorie * 00010 | Category of the request (ORDERS ORDRSP BGM 1001) | Enum Anfragekategorie | Must | — |
PROZESSDATENBERICHT | — | — | Must | — |
GERAETEUEBERNAHME | — | — | Must | — |
WEITERVERPFLICHTUNG_BETRIEB_MELO | — | — | Must | — |
AENDERUNG_MELO | — | — | Must | — |
STAMMDATEN_MALO_ODER_MELO | — | — | Must | — |
BILANZIERTE_MENGE_MEHR_MINDER_MENGEN | — | — | Must | — |
ALLOKATIONSLISTE_MEHR_MINDER_MENGEN | — | — | Must | — |
ENERGIEMENGE_UND_LEISTUNGSMAXIMUM | — | — | Must | — |
ABRECHNUNG_MESSSTELLENBETRIEB_MSB_AN_LF | — | — | Must | — |
AENDERUNG_PROGNOSEGRUNDLAGE_GERAETEKONFIGURATION | — | — | Must | — |
AENDERUNG_GERAETEKONFIGURATION | — | — | Must | — |
REKLAMATION_VON_WERTEN | — | — | Must | — |
LASTGANG_MALO_TRANCHE | — | — | Must | — |
SPERRUNG | — | — | Must | — |
ENTSPERRUNG | — | — | Must | — |
REKLAMATION_ZAEHLZEITDEFINITION | — | — | Must | — |
ZEITREIHEN_IM_RAHMEN_BILANZKREISABRECHNUNG | — | — | Must | — |
GERAETEWECHSELABSICHT | — | — | Must | — |
AENDERUNG_KONZESSIONSABGABE | — | — | Must | — |
AENDERUNG_ZAEHLZEITDEFINITION | — | — | Must | — |
UEBERMITTLUNG_WERTE_AN_ESA | — | — | Must | — |
AENDERUNG | — | — | Must | — |
BILANZKREISZUORDNUNGSLISTE | — | — | Must | — |
CLEARINGLISTE | — | — | Must | — |
NORMIERTES_PROFIL_PROFILSCHAR | — | — | Must | — |
REDISPATCH_EINZELZEITREIHE_AUSFALLARBEIT | — | — | Must | — |
REKLAMATION_PROFIL_PROFILSCHAR | — | — | Must | — |
STAMMDATEN_MALO | — | — | Must | — |
STAMMDATEN_MELO | — | — | Must | — |
STAMMDATEN_TRANCHE | — | — | Must | — |
BEENDIGUNG_EINER_KONFIGURATION | — | — | Must | — |
BESTELLUNG_EINER_KONFIGURATION | — | — | Must | — |
BESTELLUNG_EINES_ANGEBOTS_EINER_KONFIGURATION | — | — | Must | — |
REKLAMATION_EINER_KONFIGURATION | — | — | Must | — |
BESTELLUNG_AENDERUNG_NETZENTGELTE_NETZORIENTIERTER_STEUERUNGSMOEGLICHKEIT | — | — | Must | — |
AENDERUNG_DER_TECHNIK_DER_LOKATION | — | — | Must | — |
AENDERUNG_INDIVIDUELLER_KONFIGURATION | — | — | Must | — |
BESTELLUNG_AENDERUNG_ABRECHNUNGSDATEN | — | — | Must | — |
EINRICHTUNG_KONFIGURATION_AUFGRUND_ZUORDNUNG_LF | — | — | Must | — |
REKLAMATION_DEFINITION | — | — | Must | — |
BESTELLUNG_ANGEBOT_AENDERUNG_TECHNIK_LOKATION | — | — | Must | — |
| anfragetyp 00020 | Type/kind of the request (ORDERS ORDRSP IMD 7081) | Enum Anfragetyp | Must | [2] |
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 | — |
| lokationsId * 00030 | Which market or metering location this request applies to. | string | X | — |
| AUFTRAG [ ] * | — | object[] | Must | — |
| positionsdaten [ ] * | — | object[] | Must | — |
| enddatum * 00040 | enddatum | string (date-time) | X | — |
| startdatum * 00050 | startdatum | string (date-time) | X | — |
| transaktionsdaten * | — | object | Must | — |
| dokumentennummer * 00060 | EDIFACT reference from the BGM segment / BGM | string | Must | — |
| 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 | — |
| absender * | — | object | Must | — |
| rollencodenummer * 00100 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp * 00110 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
| ansprechpartner | — | object | May | — |
| eMailAdresse 00120 | Email address | string | Must | — |
| nachname 00130 | Surname (family name) of the contact person | string | X | — |
| rufnummern [ ] | — | object[] | May | — |
| nummerntyp 00140 | 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 00150 | rufnummer | string | Must | — |
| empfaenger * | — | object | Must | — |
| rollencodenummer * 00160 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp * 00170 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
Application handbook (AHB)
| Structure (EDIFACT) | Description | Format | 17102 | 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.4b00060 | Version number of the underlying BDEW message description | — | X | — |
| BGM | — | — | Must | — |
1001 700070 | Process data report | — | X | ([6] ∧ [27] ∧ [492]) ∨ ([6] ∧ [23] ∧ [493]) ∨ ([7] ∧ [27] ∧ [493]) |
1001 Z2800080 | Energy quantity and maximum demand | — | X | [6] ∧ [27] ∧ [492] |
1001 Z4800090 | Load curve market location, tranche | — | X | [6] ∧ [27] ∧ [492] |
100400100 | Document number | — | X | — |
| DTM | — | — | Must | — |
2005 13700110 | Document-/message date/time | — | X | — |
238000120 | Date or time or time span, value | — | X | [931] [494] |
2379 30300130 | CCYYMMDDHHMMZZZ | — | X | — |
| IMD | — | — | Must | [2] |
7081 Z1100140 | Load curve data | — | X | [519] |
7081 Z1200150 | Meter readings | — | X | — |
7081 Z3500160 | Energy quantity single value | — | X | [101] |
| SG1.RFF | — | — | Must | — |
1153 Z1300170 | Check identifier | — | X | — |
1154 1710200180 | Request for values | — | X | — |
| SG2.NAD | — | — | Must | — |
3035 MS00190 | Document-/message sender or sender | — | X | — |
303900200 | MP-ID | — | X | — |
3055 900210 | GS1 | — | X | — |
3055 29300220 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
3055 33200230 | DE, DVGW Service & Consult GmbH | — | X | — |
| SG5.CTA | — | — | Must | — |
3139 IC00240 | Information contact | — | X | — |
341200250 | Contact | — | X | — |
| SG5.COM | — | — | Must | — |
314800260 | Communication address, identification | — | X | (([939] [147]) ∨ ([940] [148])) ∧ [567] |
3155 EM00270 | Electronic mail | — | X | [1P0..1] |
3155 FX00280 | Fax number | — | X | [1P0..1] |
3155 TE00290 | Telephone | — | X | [1P0..1] |
3155 AJ00300 | further telephone | — | X | [1P0..1] |
3155 AL00310 | Mobile phone | — | X | [1P0..1] |
| SG2.NAD | — | — | Must | — |
3035 MR00320 | Message recipient | — | X | — |
303900330 | MP-ID | — | X | — |
3055 900340 | GS1 | — | X | — |
3055 29300350 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
3055 33200360 | DE, DVGW Service & Consult GmbH | — | X | — |
| SG2.NAD | — | — | Must | — |
3035 DP00370 | Supply address | — | X | — |
| SG2.LOC | — | — | Must | — |
3227 17200380 | Reporting point | — | X | — |
322500390 | Identifier | — | X | ([950] [521] ∧ ([21] ⊻ [24] ⊻ [51] ⊻ ([18] ∧ [493] ∧ [6]))) ⊻ ([951] [522] ∧ (([6] ⊻ [7]) ∧ ([2] ∧ [18]) ⊻ [19])) ⊻ ([950] [523] ∧ [492] ∧ [51]) |
| SG29.LIN | — | — | Must | — |
108200400 | Line item number | — | X | [903] |
| SG29.DTM | — | — | Must | — |
2005 16300410 | Processing, start date/time | — | X | — |
238000420 | Date or time or time span, value | — | X | [931] |
2379 30300430 | CCYYMMDDHHMMZZZ | — | X | — |
| SG29.DTM | — | — | Must | — |
2005 16400440 | Processing, end date/time | — | X | — |
238000450 | Date or time or time span, value | — | X | [931] |
2379 30300460 | CCYYMMDDHHMMZZZ | — | X | — |
| UNS | — | — | Must | — |
0081 S00470 | Separation of detail and summary section | — | 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 28 conditions referenced by the rows above. All conditions of the message type are listed in the condition index ORDERS.
| Marker | Condition |
|---|---|
| [2] | If BGM+7 present |
| [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 |
| [18] | If IMD++Z11 present |
| [19] | If IMD++Z12 present |
| [21] | If BGM+Z28 present |
| [23] | If MP-ID in SG2 NAD+MR with role NB is present |
| [24] | If IMD++Z35 present |
| [27] | If MP-ID in SG2 NAD+MR with role MSB is present |
| [51] | If BGM+Z48 present |
| [101] | If MP-ID in SG2 NAD+MR with role MSB is not present in the division Gas |
| [147] | if the code EM is present in DE3155 in the same COM |
| [148] | if the code TE / FX / AJ / AL is present in DE3155 in the same COM |
| [492] | if MP-ID in NAD+MR from division electricity |
| [493] | if MP-ID in NAD+MR from division gas |
| [494] | The date stated here must be the point in time at which the document was created, or a point in time before that. |
| [519] | Note: For gas, the request always refers both to the preliminary profile values and to the final profile values, if these are already available. |
| [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 |
| [567] | Note: Only one piece of information may be transmitted in DE3148 |
| [903] | Format: Possible value: 1 |
| [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+9903790000002:500+9904446000007:500+{{date}}:{{time}}+M2WINF2E'
UNH+UNHM2X0RPSS+ORDERS:D:09B:UN:1.4b'
BGM+Z28+BGMM2JZ7IGE'
DTM+137:202504050200?+00:303'
RFF+Z13:17102'
NAD+MS+9903790000002::293'
NAD+MR+9904446000007::293'
NAD+DP'
LOC+172+50074561188'
LIN+1'
DTM+163:202412312300?+00:303'
DTM+164:202501312300?+00:303'
UNS+S'
UNT+13+UNHM2X0RPSS'
UNZ+1+M2WINF2E'[1 item
{6 fields
"data": {3 fields
"stammdaten": {2 fields
"ANFRAGE": [1 item
{6 fields
"AUFTRAG": [1 item
{3 fields
"positionsdaten": [1 item
{3 fields
"transaktionsdaten": {9 fields
"absender": {5 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 and MSB.
| Role | Party involved | Process | Rulebook | Division | Step |
|---|---|---|---|---|---|
| LF | LF | Business data request | GPKE part 4 | Electricity | Step 3 |
| LF | LF | Business data request from the LF to NB | GeLi Gas 2.0 | Gas | Step 1 |
| NB | NB | Business data request | GPKE part 4 | Electricity | Step 3 |
| NB | NB | Business data request from the LF to NB | GeLi Gas 2.0 | Gas | Step 1 |
| MSB | MSB | Business data request | GPKE part 4 | Electricity | Step 3 |
Business classification
| Attribute | Value |
|---|---|
| Use case (AHB) | Request for values |
| AHB | ORDERS AHB |
| Transmission channel | AS4 |
This check identifier is used in 4 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 |
|---|---|---|---|
| GPKE part 4 | Business data request | LF → MSB | Business data request |
| GeLi Gas 2.0 | Business data request from LF to NB | LF → NB | Business data request |
| GeLi Gas | Ch. D 3.2 No. 1 | LF → NB | Business data request |
| WiM gas | UF GeLiGas_006 business data request from NB to MSB | NB → MSB | Business data request |
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 | 13002 | Meter reading (gas) | MSCONS | explicit |
| Response | 13008 | Load curve (gas) | MSCONS | explicit |
| Response | 13009 | Energy quantity (gas) | MSCONS | explicit |
| Response | 13016 | Energy quantity and max. demand (electricity) | MSCONS | from the step sequence |
| Response | 13017 | Meter reading (electricity) | MSCONS | from the step sequence |
| Response | 13018 | Load curve metering location, grid coupling point, grid location | MSCONS | from the step sequence |
| Response | 13019 | Energy quantity (electricity) | MSCONS | from the step sequence |
| Response | 13025 | Load curve market location, tranche | MSCONS | from the step sequence |
| Response | 19102 | Rejection of the request for values | ORDRSP | explicit |
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.
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 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.