Check identifier 17003 — Order issuance change of technology
Check identifier 17003 · EDIFACT message type ORDERS · Format version 202604
Data structure
| Structure (BO4E) | Description | Format | 17003 | Condition |
|---|---|---|---|---|
| stammdaten * | — | object | Must | — |
| ANFRAGE [ ] * | — | object[] | Must | — |
| lokationsId * 00010 | Which market or metering location this request applies to. | string | X | — |
| AUFTRAG [ ] * | — | object[] | Must | — |
| ausfuehrungsdatum * 00020 | The execution date describes at which point in time an order is to be executed. | string (date-time) | X | — |
| MESSLOKATION [ ] * | — | object[] | Must | — |
| zaehlwerke [ ] * | — | object[] | Must | — |
| messprodukt * 00030 | messprodukt | string | X | — |
| transaktionsdaten * | — | object | Must | — |
| dokumentennummer * 00040 | EDIFACT reference from the BGM segment / BGM | string | X | — |
| nachrichtendatum * 00050 | Creation date of the EDIFact / DTM+137 | string (date-time) | X | — |
| nachrichtenreferenznummer * 00060 | EDIFACT reference from the UNT segment / UTILMD UNT+21 | string | Must | — |
| pruefidentifikator * 00070 | Contains the check identifier from the EDIFact communication / RFF+Z13 | string | X | — |
| absender * | — | object | Must | — |
| rollencodenummer * 00080 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp * 00090 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
| ansprechpartner * | — | object | Must | — |
| eMailAdresse 00100 | Email address | string | Must | — |
| nachname * 00110 | Surname (family name) of the contact person | string | X | — |
| rufnummern [ ] | — | object[] | May | — |
| nummerntyp 00120 | 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 00130 | rufnummer | string | Must | — |
| ansprechpartnerKunde | — | object | May | — |
| eMailAdresse 00140 | Email address | string | Must | — |
| nachname 00150 | Surname (family name) of the contact person | string | X | — |
| 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 | 17003 | 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 Z1200070 | Change of the technology of the location | — | 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 | — |
| DTM | — | — | Must | — |
2005 20300120 | Execution date/time | — | X | — |
238000130 | Date or time or time span, value | — | X | [UB3] |
2379 30300140 | CCYYMMDDHHMMZZZ | — | X | — |
| SG1.RFF | — | — | Must | — |
1153 Z1300150 | Check identifier | — | X | — |
1154 1700300160 | Order issuance for the change of the metering location | — | X | — |
| SG2.NAD | — | — | Must | — |
3035 MS00170 | Document-/message sender or sender | — | X | — |
303900180 | MP-ID | — | X | [60] |
3055 900190 | GS1 | — | X | — |
3055 33200200 | DE, DVGW Service & Consult GmbH | — | X | — |
| SG5.CTA | — | — | Must | — |
3139 IC00210 | Information contact | — | X | — |
341200220 | Contact | — | X | — |
| SG5.COM | — | — | Must | — |
314800230 | Communication address, identification | — | X | (([939] [147]) ∨ ([940] [148])) ∧ [567] |
3155 EM00240 | Electronic mail | — | X | [1P0..1] |
3155 FX00250 | Fax number | — | X | [1P0..1] |
3155 TE00260 | Telephone | — | X | [1P0..1] |
3155 AJ00270 | further telephone | — | X | [1P0..1] |
3155 AL00280 | Mobile phone | — | X | [1P0..1] |
| SG2.NAD | — | — | Must | — |
3035 MR00290 | Message recipient | — | X | — |
303900300 | MP-ID | — | X | [60] |
3055 900310 | GS1 | — | 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 | [951] [522] |
| SG2.NAD | — | — | Must | — |
3035 Z0900360 | Customer of the LF | — | X | — |
| SG5.CTA | — | — | Must | — |
3139 IC00370 | Information point | — | X | — |
341200380 | Contact | — | X | — |
| SG5.COM | — | — | Must | — |
314800390 | Communication address, identification | — | X | (([939] [147]) ∨ ([940] [148])) ∧ [567] |
3155 EM00400 | — | X | [1P0..1] | |
3155 FX00410 | Fax number | — | X | [1P0..1] |
3155 TE00420 | Telephone | — | X | [1P0..1] |
3155 AJ00430 | further telephone | — | X | [1P0..1] |
3155 AL00440 | Mobile phone | — | X | [1P0..1] |
| SG29.LIN | — | — | Must | — |
108200450 | Line item number | — | X | [911] |
1229 Z1900460 | Required product of the metering location | — | X | — |
| SG29.PIA | — | — | Must | — |
4347 500470 | Product identification | — | X | — |
714000480 | Product code | — | X | [153] ∧ (([6] ∧ [157]) ⊻ ([7] ∧ [156])) |
7143 Z1100490 | Product | — | X | — |
| UNS | — | — | Must | — |
0081 S00500 | Separation of detail and summary section | — | X | — |
| UNT | — | — | Must | — |
007400510 | Number of segments in a message | — | X | — |
006200520 | Message reference number | — | X | — |
Conditions of this table
The free text of the 18 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 |
| [60] | MP-ID only from 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 |
| [153] | Only the product codes are permitted that are present with the value "Metering location" in the column "Level" in chapter 7 "Products for the order placement of a change at a location" of the code list of configurations. |
| [156] | Furthermore, only the product codes are permitted that are marked with an "X" in the column "NB" within the column "Product orderable from MSB by market role" in chapter 7 "Products for the order placement of a change at a location" of the code list of configurations. |
| [157] | Furthermore, only the product codes are permitted that are marked with an "X" in the column "LF" within the column "Product orderable from MSB by market role" in chapter 7 "Products for the order placement of a change at a location" of the code list of configurations. |
| [494] | The date stated here must be the point in time at which the document was created, or a point in time before that. |
| [522] | Note: Use of the ID of the metering location |
| [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 |
| [951] | Format: Metering point identifier |
| [UB3] | ([931] ∧ [932] [492] ∧ [490]) ⊻ ([931] ∧ [933] [492] ∧ [491]) ⊻ ([931] ∧ [934] [493] ∧ [490]) ⊻ ([931] ∧ [935] [493] ∧ [491]) |
| [1P0..1] | Note: This is the standard package if no condition applies, e.g. in the COM segment. |
Example message
UNA:+.? '
UNB+UNOC:3+9800009600004:502+9800191400007:502+{{date}}:{{time}}+M5HNLNGQ'
UNH+UNHM5GVHK54+ORDERS:D:09B:UN:1.4b'
BGM+Z12+BGMM5CGENN0'
DTM+137:202506051200?+00:303'
DTM+203:202506302200?+00:303'
RFF+Z13:17003'
NAD+MS+9800009600004::332'
CTA+IC+:Mustermann'
COM+?+012345678910:TE'
NAD+MR+9800191400007::332'
NAD+DP'
LOC+172+DE0032106765712000000000000000037'
NAD+Z09'
CTA+IC+:Mustermann'
COM+?+012345678910:TE'
LIN+1+Z19'
PIA+5+9991000002305:Z11'
UNS+S'
UNT+18+UNHM5GVHK54'
UNZ+1+M5HNLNGQ'[1 item
{6 fields
"data": {3 fields
"stammdaten": {4 fields
"MESSLOKATION": [1 item
{5 fields
"zaehlwerke": [1 item
{1 field
"ENERGIELIEFERVERTRAG": [1 item
{5 fields
"vertragspartner2": [1 item
{3 fields
"geschaeftspartnerrolle": [1 item
"ANFRAGE": [1 item
{5 fields
"AUFTRAG": [1 item
{4 fields
"positionsdaten": [1 item
{1 field
"transaktionsdaten": {10 fields
"absender": {7 fields
"ansprechpartner": {4 fields
"rufnummern": [1 item
{2 fields
"empfaenger": {5 fields
"ansprechpartnerKunde": {4 fields
"rufnummern": [1 item
{2 fields
Download: EDIFACT file · BO4E JSON
Belongs to these role views
There is no role view for this check identifier: in this format version no process step of any market role carries it. A role statement would stand here without evidence.
No process in this release
The entry in which this check identifier appears is not a process but a chapter reference: as parties involved, the source names only running text there (“parties involved as in the original message”), and the step has neither a number nor an action. Counted as a process, it would have reported a coverage gap that is none — it still cannot be rendered. This is a gap in the process source, not in the delivery — and it is the reason why no “Belongs to these role views” table appears here.
Business classification
| Attribute | Value |
|---|---|
| Use case (AHB) | Order issuance change of technical equipment |
| 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 |
|---|---|---|---|
| WiM gas | Ch. C 1.2 No. 1a | LF → MSB | Order issuance change |
| WiM gas | Ch. C 1.2 No. 1c | NB → MSB | Order issuance change |
| WiM electricity part 1 | Metering location change from NB to MSB | NB → MSB (corresponds to MSB on the metering location object) | Order issuance change |
| WiM electricity part 1 | Metering location change from LF to MSB | LF → MSB (corresponds to MSB on the metering location object) | Order issuance change |
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”.
Responses: No response of this format version names this check identifier as a reference — neither explicitly in the Prüfi table nor via the step sequence. That does not mean there is none; it means that the sources do not record one.
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 70 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.