Check identifier 17004 — Request for values
Check identifier 17004 · EDIFACT message type ORDERS · Format version 202604
Data structure
| Structure (BO4E) | Description | Format | 17004 | 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 | — |
| gueltigAb * 00020 | gueltigAb | string (date-time) | X | — |
| lokationsId * 00030 | Which market or metering location this request applies to. | string | X | — |
| AUFTRAG [ ] * | — | object[] | Must | — |
| positionsdaten [ ] * | — | object[] | Must | — |
| anfragegrund * 00040 | Request reason | Enum Anfragegrund | Must | — |
ABGRENZUNG_VON_ENERGIEMENGEN | — | — | Must | — |
ABGRENZUNG | — | — | Must | — |
WECHSELEREIGNIS | — | — | Must | — |
ZWISCHENABLESUNG | — | — | Must | — |
DIREKTER_VERTRAG_MSB_AN | — | — | Must | — |
DIREKTER_VERTRAG_MSB_ANN | — | — | Must | — |
AENDERUNG_IM_LOKATIONSBUENDEL | — | — | Must | — |
NEUKONFIGURATION | — | — | Must | — |
KONFIGURATION_UNVERAENDERT | — | — | Must | — |
| transaktionsdaten * | — | object | Must | — |
| dokumentennummer * 00050 | EDIFACT reference from the BGM segment / 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 | — |
| absender * | — | object | Must | — |
| rollencodenummer * 00090 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp * 00100 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
| ansprechpartner | — | object | May | — |
| eMailAdresse 00110 | Email address | string | Must | — |
| nachname 00120 | Surname (family name) of the contact person | string | X | — |
| rufnummern [ ] | — | object[] | May | — |
| nummerntyp 00130 | 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 00140 | rufnummer | string | Must | — |
| 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 | 17004 | 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 | — |
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 Z1300120 | Value determination | — | X | — |
| SG1.RFF | — | — | Must | — |
1153 Z1300130 | Check identifier | — | X | — |
1154 1700400140 | Request meter reading values | — | X | — |
| SG2.NAD | — | — | Must | — |
3035 MS00150 | Document-/message sender or sender | — | X | — |
303900160 | MP-ID | — | X | — |
3055 900170 | GS1 | — | X | — |
3055 29300180 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
3055 33200190 | DE, DVGW Service & Consult GmbH | — | X | — |
| SG5.CTA | — | — | Must | — |
3139 IC00200 | Information contact | — | X | — |
341200210 | Contact | — | X | — |
| SG5.COM | — | — | Must | — |
314800220 | Communication address, identification | — | X | (([939] [147]) ∨ ([940] [148])) ∧ [567] |
3155 EM00230 | Electronic mail | — | X | [1P0..1] |
3155 FX00240 | Fax number | — | X | [1P0..1] |
3155 TE00250 | Telephone | — | X | [1P0..1] |
3155 AJ00260 | further telephone | — | X | [1P0..1] |
3155 AL00270 | Mobile phone | — | X | [1P0..1] |
| SG2.NAD | — | — | Must | — |
3035 MR00280 | Message recipient | — | X | — |
303900290 | MP-ID | — | X | — |
3055 900300 | GS1 | — | X | — |
3055 29300310 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
3055 33200320 | DE, DVGW Service & Consult GmbH | — | X | — |
| SG2.NAD | — | — | Must | — |
3035 DP00330 | Supply address | — | X | — |
| SG2.LOC | — | — | Must | — |
3227 17200340 | Reporting point | — | X | — |
322500350 | Identifier | — | X | ([950] [521] ∧ [46]) ⊻ ([951] [522] ∧ [47]) |
| SG29.LIN | — | — | Must | — |
108200360 | Line item number | — | X | [903] |
| SG29.IMD | — | — | Must | — |
7081 Z4600370 | Delimitation of energy quantities | — | X | [45] ∧ [492] |
7081 Z4700380 | Delimitation | — | X | [15] ∧ [492] |
7081 Z4800390 | Change event | — | X | [493] |
7081 Z4900400 | Interim meter reading | — | X | — |
| SG29.DTM | — | — | Must | — |
2005 700410 | Effective date/time | — | X | — |
238000420 | Date or time or time span, value | — | X | [UB3] |
2379 30300430 | CCYYMMDDHHMMZZZ | — | X | — |
| UNS | — | — | Must | — |
0081 S00440 | Separation of detail and summary section | — | X | — |
| UNT | — | — | Must | — |
007400450 | Number of segments in a message | — | X | — |
006200460 | Message reference number | — | X | — |
Conditions of this table
The free text of the 20 conditions referenced by the rows above. All conditions of the message type are listed in the condition index ORDERS.
| Marker | Condition |
|---|---|
| [15] | If MP-ID in SG2 NAD+MS with role MSB is present |
| [45] | If MP-ID in SG2 NAD+MS with role MSB is not present |
| [46] | If SG29 IMD++Z46 is present |
| [47] | If SG29 IMD++Z46 is not present |
| [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. |
| [521] | Note: Use of the ID of the market location |
| [522] | Note: Use of the ID of the metering location |
| [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. |
| [UB3] | ([931] ∧ [932] [492] ∧ [490]) ⊻ ([931] ∧ [933] [492] ∧ [491]) ⊻ ([931] ∧ [934] [493] ∧ [490]) ⊻ ([931] ∧ [935] [493] ∧ [491]) |
Example message
UNA:+.? '
UNB+UNOC:3+9900259000002:500+9904629000006:500+{{date}}:{{time}}+M03UH94L'
UNH+M01QMYIF+ORDERS:D:09B:UN:1.4b'
BGM+7+LZWOTR6A'
DTM+137:202408140601?+00:303'
IMD++Z13'
RFF+Z13:17004'
NAD+MS+9900259000002::293'
CTA+IC+:Laue'
COM+marktpartner@stromnetz-hamburg.de:EM'
NAD+MR+9904629000006::293'
NAD+DP'
LOC+172+DE00014545768S0000000000000003054'
LIN+1'
IMD++Z49'
DTM+7:202407312200?+00:303'
UNS+S'
UNT+16+M01QMYIF'
UNZ+1+M03UH94L'[1 item
{6 fields
"data": {3 fields
"stammdaten": {2 fields
"ANFRAGE": [1 item
{7 fields
"AUFTRAG": [1 item
{3 fields
"positionsdaten": [1 item
{2 fields
"transaktionsdaten": {8 fields
"absender": {5 fields
"ansprechpartner": {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, NB and MSB.
| Role | Party involved | Process | Rulebook | Division | Step |
|---|---|---|---|---|---|
| LF | LF | Request and provision of measured values | GeLi Gas 2.0 | Gas | Step 1 |
| LF | LF | Request for a value from the LF | WiM electricity part 2 | Electricity | Step 1 |
| LF | LF | Request for a value from the LF | WiM electricity part 2 | Electricity | Step 4 |
| NB | NB | Request and provision of measured values | GeLi Gas 2.0 | Gas | Step 1 |
| NB | NB | Request for a value from the NB | WiM electricity part 2 | Electricity | Step 1 |
| NB | NB | Request for a value from the NB | WiM electricity part 2 | Electricity | Step 4 |
| MSB | MSB | Request and provision of measured values | GeLi Gas 2.0 | Gas | Step 1 |
| MSB | MSB-MALO | Request for a value from the LF | WiM electricity part 2 | Electricity | Step 1 |
| MSB | MSB-MALO | Request for a value from the LF | WiM electricity part 2 | Electricity | Step 4 |
| MSB | MSB-MALO | Request for value from the MSB of the market location | WiM electricity part 2 | Electricity | Step 1 |
| MSB | MSB-MALO | Request for a value from the NB | WiM electricity part 2 | Electricity | Step 1 |
| MSB | MSB-MALO | Request for a value from the NB | WiM electricity part 2 | Electricity | Step 4 |
| MSB | MSB-MELO | Request for a value from the LF | WiM electricity part 2 | Electricity | Step 1 |
| MSB | MSB-MELO | Request for a value from the LF | WiM electricity part 2 | Electricity | Step 4 |
| MSB | MSB-MELO | Request for value from the MSB of the market location | WiM electricity part 2 | Electricity | Step 1 |
| MSB | MSB-MELO | Request for a value from the NB | WiM electricity part 2 | Electricity | Step 1 |
| MSB | MSB-MELO | Request for a value from the NB | WiM electricity part 2 | Electricity | Step 4 |
Business classification
| Attribute | Value |
|---|---|
| Use case (AHB) | Request for values |
| AHB | ORDERS AHB |
| Transmission channel | AS4 |
This check identifier is used in 7 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 | Request value of the NB | NB → MSB (corresponds to MSB on the market location object) | Request value |
| WiM electricity part 2 | Request value of the NB | MSB (corresponds to MSB on the object market location) → MSB (corresponds to MSB on the object metering location) | Request for value of a metering location |
| WiM electricity part 2 | Request value of the LF | LF → MSB (corresponds to MSB on the market location object) | Request value |
| WiM electricity part 2 | Request value of the LF | MSB (corresponds to MSB on the object market location) → MSB (corresponds to MSB on the object metering location) | Request for value of a metering location |
| WiM electricity part 2 | Request for value from the MSB of the market location | MSB (corresponds to MSB on the object market location) → MSB (corresponds to MSB on the object metering location) | Request for value of a metering location |
| GeLi Gas 2.0 | Request and provision of meter reading values | NB → MSB | Forwarding of an individual request (outside the periodic meter reading) |
| GeLi Gas | Ch. D 1.2.3 No. 1 | NB → MSB | Forwarding of an individual request (outside the periodic meter reading) |
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 | 19007 | Rejection request values | 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.
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 62 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.