Check identifier 17002 — Continued commitment
Check identifier 17002 · EDIFACT message type ORDERS · Format version 202610
Data structure
| Structure (BO4E) | Description | Format | 17002 | Condition |
|---|---|---|---|---|
| stammdaten * | — | object | Must | — |
| ANFRAGE [ ] * | — | object[] | Must | — |
| lokationsId * 00010 | Which market or metering location this request applies to. | string | X | — |
| AUFTRAG [ ] * | — | object[] | Must | — |
| verschobenerAbmeldetermin * 00020 | verschobenerAbmeldetermin | string (date-time) | X | — |
| MARKTLOKATION [ ] | — | object[] | May | — |
| marktlokationsId 00030 | Identification number of a market location at which energy is either consumed or generated | 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 | — |
| empfaenger * | — | 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 | — |
Application handbook (AHB)
| Structure (EDIFACT) | Description | Format | 17002 | 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 Z1100070 | Continued commitment to operate the metering 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 Z0200120 | Postponed deregistration date | — | X | — |
238000130 | Date or time or time span, value | — | X | [UB3] ∧ [506] |
2379 30300140 | CCYYMMDDHHMMZZZ | — | X | — |
| SG1.RFF | — | — | Must | — |
1153 Z1300150 | Check identifier | — | X | — |
1154 1700200160 | Continued commitment MSBA | — | X | — |
| SG2.NAD | — | — | Must | — |
3035 MS00170 | Document-/message sender or sender | — | X | — |
303900180 | MP-ID | — | X | — |
3055 900190 | GS1 | — | X | — |
3055 29300200 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
3055 33200210 | DE, DVGW Service & Consult GmbH | — | X | — |
| SG2.NAD | — | — | Must | — |
3035 MR00220 | Message recipient | — | X | — |
303900230 | MP-ID | — | X | — |
3055 900240 | GS1 | — | X | — |
3055 29300250 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
3055 33200260 | DE, DVGW Service & Consult GmbH | — | X | — |
| SG2.NAD | — | — | Must | — |
3035 DP00270 | Supply address | — | X | — |
| SG2.LOC | — | — | Must | — |
3227 17200280 | Reporting point | — | X | — |
322500290 | Identifier | — | X | [951] [522] |
| SG3.RFF | — | — | Must | — |
1153 Z1800300 | Market location | — | X | — |
115400310 | ID of the market location | — | X | [950] [521] |
| UNS | — | — | Must | — |
0081 S00320 | Separation of detail and summary section | — | X | — |
| UNT | — | — | Must | — |
007400330 | Number of segments in a message | — | X | — |
006200340 | Message reference number | — | X | — |
Conditions of this table
The free text of the 8 conditions referenced by the rows above. All conditions of the message type are listed in the condition index ORDERS.
| Marker | Condition |
|---|---|
| [494] | The date stated here must be the point in time at which the document was created, or a point in time before that. |
| [506] | Note: Date up to which the MSBA is obliged to continue |
| [521] | Note: Use of the ID of the market location |
| [522] | Note: Use of the ID of the metering location |
| [931] | Format: ZZZ = +00 |
| [950] | Format: market location ID |
| [951] | Format: Metering point identifier |
| [UB3] | ([931] ∧ [932] [492] ∧ [490]) ⊻ ([931] ∧ [933] [492] ∧ [491]) ⊻ ([931] ∧ [934] [493] ∧ [490]) ⊻ ([931] ∧ [935] [493] ∧ [491]) |
Example message
UNA:+.? '
UNB+UNOC:3+9900244000009:500+9904733000009:500+{{date}}:{{time}}+LZZY4HOB'
UNH+M01RZWDE+ORDERS:D:09B:UN:1.4c'
BGM+Z11+M0MGNHP2'
DTM+137:202610011100?+00:303'
DTM+Z02:202611052200?+00:303'
RFF+Z13:17002'
NAD+MS+9900244000009::293'
NAD+MR+9904733000009::293'
NAD+DP'
LOC+172+DE00014545768S0000000000000003054'
RFF+Z18:55123678945'
UNS+S'
UNT+12+M01RZWDE'
UNZ+1+LZZY4HOB'[1 item
{6 fields
"data": {3 fields
"stammdaten": {4 fields
"MARKTLOKATION": [1 item
{5 fields
"marktlokationsTyp": [1 item
{1 field
"MESSLOKATION": [1 item
{4 fields
"ANFRAGE": [1 item
{5 fields
"AUFTRAG": [1 item
{3 fields
"transaktionsdaten": {8 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 NB and MSB.
| Role | Party involved | Process | Rulebook | Division | Step |
|---|---|---|---|---|---|
| NB | NB | End of metering point operation from the MSB to NB | AWH WiM gas 2.0 | Gas | Step 5 |
| NB | NB | End of metering point operation | WiM electricity part 1 | Electricity | Step 5 |
| MSB | GMSB | End of metering point operation from the MSB to NB | AWH WiM gas 2.0 | Gas | Step 5 |
| MSB | GMSB | End of metering point operation | WiM electricity part 1 | Electricity | Step 5 |
| MSB | MSBA | End of metering point operation from the MSB to NB | AWH WiM gas 2.0 | Gas | Step 5 |
| MSB | MSBA | End of metering point operation | WiM electricity part 1 | Electricity | Step 5 |
Business classification
| Attribute | Value |
|---|---|
| Use case (AHB) | Continued commitment |
| AHB | ORDERS AHB |
| Transmission channel | AS4 |
This check identifier is used in 3 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 1 | End of metering point operation | NB → MSB (corresponds to MSBA on the metering location object) | Continued commitment of the MSB |
| AWH WiM gas 2.0 | End of metering point operation from MSB to NB | NB → MSBA | Continued commitment of the MSB |
| WiM gas | Ch. B 4.3 No. 5a | NB → MSB | Optional: continued commitment of the MSBA |
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 | 19003 | Confirmation of continued commitment | ORDRSP | from the step sequence |
| Response | 19004 | Rejection continued commitment | 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 46 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.