Check identifier 17123 — Order placement change of metering time period definition
Check identifier 17123 · EDIFACT message type ORDERS · Format version 202610
Data structure
| Structure (BO4E) | Description | Format | 17123 | 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 | — |
| lokationsId * 00020 | Which market or metering location this request applies to. | string | X | — |
| AUFTRAG [ ] * | — | object[] | Must | — |
| ausfuehrungsdatum * 00030 | The execution date describes at which point in time an order is to be executed. | string (date-time) | X | — |
| MARKTLOKATION [ ] | — | object[] | May | — |
| zaehlwerke [ ] | — | object[] | May | — |
| messprodukt 00040 | messprodukt | string | X | — |
| zaehlzeiten | — | object | May | — |
| zaehlzeitDefinition 00050 | Metering time period definition | string | Must | — |
| transaktionsdaten * | — | object | Must | — |
| dokumentennummer * 00060 | EDIFACT reference from the BGM segment / BGM | string | X | — |
| 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 | — |
| empfaenger * | — | object | Must | — |
| rollencodenummer * 00120 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp * 00130 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
Application handbook (AHB)
| Structure (EDIFACT) | Description | Format | 17123 | 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 Z5600070 | Change of individual configuration | — | 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 | [UB1] |
2379 30300140 | CCYYMMDDHHMMZZZ | — | X | — |
| IMD | — | — | Must | — |
7081 Z5500150 | Change configuration | — | X | — |
7081 Z5700160 | Order cancellation metering time period definition | — | X | [27] |
7081 Z6000170 | Order cancellation metering product with metering time period definition of LF | — | X | [27] |
| SG1.RFF | — | — | Must | — |
1153 Z1300180 | Check identifier | — | X | — |
1154 1712300190 | Order placement for change of metering time period definition | — | X | — |
| SG2.NAD | — | — | Must | — |
3035 MS00200 | Document-/message sender or sender | — | X | — |
303900210 | MP-ID | — | X | [61] |
3055 900220 | GS1 | — | X | — |
3055 29300230 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
| SG2.NAD | — | — | Must | — |
3035 MR00240 | Message recipient | — | X | — |
303900250 | MP-ID | — | X | [61] |
3055 900260 | GS1 | — | X | — |
3055 29300270 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
| SG2.NAD | — | — | Must | — |
3035 DP00280 | Supply address | — | X | — |
| SG2.LOC | — | — | Must | — |
3227 17200290 | Reporting point | — | X | — |
322500300 | Identifier | — | X | [950] [521] |
| SG29.LIN | — | — | Must | — |
108200310 | Line item number | — | X | [903] |
1229 Z5400320 | Required product of the market location | — | X | — |
| SG29.PIA | — | — | Must | — |
4347 500330 | Product identification | — | X | — |
714000340 | Product code | — | X | [95] |
7143 Z1100350 | Product | — | X | — |
| SG30.CCI | — | — | Must | — |
7059 Z3900360 | Code of the metering time period definition | — | X | — |
7059 Z4100370 | No metering time period required for metering product | — | X | [75] |
703700380 | Code of the metering time period definition | — | X | [77] ∧ (([27] ∧ [540]) ⊻ ([23] ∧ [539])) |
| UNS | — | — | Must | — |
0081 S00390 | Separation of detail and summary section | — | X | — |
| UNT | — | — | Must | — |
007400400 | Number of segments in a message | — | X | — |
006200410 | Message reference number | — | X | — |
Conditions of this table
The free text of the 14 conditions referenced by the rows above. All conditions of the message type are listed in the condition index ORDERS.
| Marker | Condition |
|---|---|
| [23] | If MP-ID in SG2 NAD+MR with role NB is present |
| [27] | If MP-ID in SG2 NAD+MR with role MSB is present |
| [61] | MP-ID only from division electricity |
| [75] | If no metering time period is required for the required value |
| [77] | If code Z39 (code of the metering time period definition) is present in DE7059 in the same CCI |
| [95] | Metering product code from chapter 2.1 "Standard metering products of the market 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. |
| [521] | Note: Use of the ID of the market location |
| [539] | Note: Only codes of metering time periods from the list of the NB must be specified |
| [540] | Note: Only codes of metering time periods from the list of the LF must be specified |
| [903] | Format: Possible value: 1 |
| [931] | Format: ZZZ = +00 |
| [950] | Format: market location ID |
| [UB1] | ([931] ∧ [932] [490]) ⊻ ([931] ∧ [933] [491]) |
Example message
UNA:+.? '
UNB+UNOC:3+9903111000003:500+9903111000003:500+{{date}}:{{time}}+M0E47OMP'
UNH+M0CYKMGN+ORDERS:D:09B:UN:1.4c'
BGM+Z56+M0RAU7GV'
DTM+137:202610011100?+00:303'
DTM+203:202608222200?+00:303'
IMD++Z55'
RFF+Z13:17123'
NAD+MS+9903111000003::293'
NAD+MR+9903111000003::293'
NAD+DP'
LOC+172+44897654121'
LIN+1+Z54'
PIA+5+9991000000052:Z11'
CCI+Z39++AAL'
UNS+S'
UNT+15+M0CYKMGN'
UNZ+1+M0E47OMP'[1 item
{6 fields
"data": {3 fields
"stammdaten": {3 fields
"ANFRAGE": [1 item
{6 fields
"AUFTRAG": [1 item
{4 fields
"positionsdaten": [1 item
{1 field
"MARKTLOKATION": [1 item
{3 fields
"zaehlwerke": [1 item
{2 fields
"zaehlzeiten": {1 field
"transaktionsdaten": {8 fields
"absender": {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 and MSB.
| Role | Party involved | Process | Rulebook | Division | Step |
|---|---|---|---|---|---|
| LF | LF | Order placement for a configuration from the LF to MSB | GPKE part 3 | Electricity | Step 4 |
| LF | LF | Order placement for a configuration from the LF to NB | GPKE part 3 | Electricity | Step 1 |
| NB | NB | Order placement for a configuration from the LF to NB | GPKE part 3 | Electricity | Step 1 |
| MSB | MSB | Order placement for a configuration from the LF to MSB | GPKE part 3 | Electricity | Step 4 |
| MSB | WMSB | Order placement for a configuration from the LF to MSB | GPKE part 3 | Electricity | Step 4 |
Business classification
| Attribute | Value |
|---|---|
| Use case (AHB) | Order placement for change of metering time period definition |
| AHB | ORDERS AHB |
| Transmission channel | AS4 |
This check identifier is used in 2 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 3 | Order placement for a configuration from LF to NB | LF → NB | Order placement for a configuration at the level of the directly affected location |
| GPKE part 3 | Order placement for a configuration from LF to MSB | LF → MSB | Order placement for a configuration at the level of the directly affected location |
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 | 19124 | Notification on the change of the metering time period definition | 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 56 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.