Check identifier 19124 — Notification of change metering time period definition
Check identifier 19124 · EDIFACT message type ORDRSP · Format version 202610
Data structure
| Structure (BO4E) | Description | Format | 19124 | Condition |
|---|---|---|---|---|
| transaktionsdaten * | — | object | Must | — |
| antwortstatus * 00010 | Response status / STS+E01 | string | Must | — |
| antwortstatusCodeliste * 00020 | Response status code list / STS+E01 | string | Must | — |
| auftragsReferenz * 00030 | Order number 'purchasing' / RFF+ON | string | X | — |
| dokumentennummer * 00040 | EDIFACT reference from the BGM segment / BGM | string | X | — |
| freitext 00050 | Free text / FTX+ACB | 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 | — |
| empfaenger * | — | object | Must | — |
| rollencodenummer * 00110 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp * 00120 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
Application handbook (AHB)
| Structure (EDIFACT) | Description | Format | 19124 | Condition |
|---|---|---|---|---|
| UNH | — | — | Must | — |
006200010 | Message reference number | — | X | — |
0065 ORDRSP00020 | Order response | — | X | — |
0052 D00030 | Draft version | — | X | — |
0054 10A00040 | Edition 2010 - A | — | 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 | — |
| SG1.RFF | — | — | Must | — |
1153 ON00120 | Order number (purchasing) | — | X | — |
115400130 | Reference message number | — | X | [529] |
| SG1.RFF | — | — | Must | — |
1153 Z1300140 | Check identifier | — | X | — |
1154 1912400150 | Notification on the change of the metering time period definition | — | X | — |
| SG2.AJT | — | — | Must | — |
446500160 | Code of the check step | — | X | — |
1082 E_052300170 | EBD no. E_0523 | — | X | [3] |
1082 E_053300180 | EBD no. E_0533 | — | X | [10] |
| SG2.FTX | — | — | Must | [28] |
4451 AAP00190 | Response (free text) | — | X | — |
444000200 | Free text | — | X | — |
| SG3.NAD | — | — | Must | — |
3035 MS00210 | Document-/message sender or sender | — | X | — |
303900220 | MP-ID | — | X | [30] |
3055 900230 | GS1 | — | X | — |
3055 29300240 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
| SG3.NAD | — | — | Must | — |
3035 MR00250 | Message recipient | — | X | — |
303900260 | MP-ID | — | X | [30] |
3055 900270 | GS1 | — | X | — |
3055 29300280 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
| UNS | — | — | Must | — |
0081 S00290 | Separation of detail and summary section | — | X | — |
| UNT | — | — | Must | — |
007400300 | Number of segments in a message | — | X | — |
006200310 | Message reference number | — | X | — |
Conditions of this table
The free text of the 7 conditions referenced by the rows above. All conditions of the message type are listed in the condition index ORDRSP.
| Marker | Condition |
|---|---|
| [3] | If MP-ID in SG3 NAD+MS with role NB is present |
| [10] | If MP-ID in SG3 NAD+MS with role MSB is present |
| [28] | If AJT+A99 present |
| [30] | MP-ID only from division electricity |
| [494] | The date stated here must be the point in time at which the document was created, or a point in time before that. |
| [529] | Note: Document number from BGM DE1004 of the ORDERS |
| [931] | Format: ZZZ = +00 |
Example message
UNA:+.? '
UNB+UNOC:3+9900244000009:500+9903692000001:500+{{date}}:{{time}}+DASFTZWAIAUQDZ'
UNH+DALRTRVYCPSLBA+ORDRSP:D:10A:UN:1.4c'
BGM+Z56+DA862411200724399903323000007189649'
DTM+137:202610011100?+00:303'
RFF+ON:AFN9523'
RFF+Z13:19124'
AJT+A99+E_0523'
FTX+AAP+++Stell keine Fragen'
NAD+MS+9900244000009::293'
NAD+MR+9903692000001::293'
UNS+S'
UNT+11+DALRTRVYCPSLBA'
UNZ+1+DASFTZWAIAUQDZ'[1 item
{6 fields
"data": {3 fields
"stammdaten": {1 field
"ANFRAGE": [1 item
{3 fields
"transaktionsdaten": {12 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 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 5 |
| LF | LF | Order placement for a configuration from the LF to NB | GPKE part 3 | Electricity | Step 2 |
| NB | NB | Order placement for a configuration from the LF to NB | GPKE part 3 | Electricity | Step 2 |
| MSB | MSB | Order placement for a configuration from the LF to MSB | GPKE part 3 | Electricity | Step 5 |
| MSB | WMSB | Order placement for a configuration from the LF to MSB | GPKE part 3 | Electricity | Step 5 |
Business classification
| Attribute | Value |
|---|---|
| Use case (AHB) | Notification on the change of the metering time period definition |
| AHB | ORDRSP AHB |
| Response to check identifier | 17123 |
| Decision tree | E_0523 · E_0533 |
| 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 | NB → LF | Notification on the further procedure for the order placement |
| GPKE part 3 | Order placement for a configuration from LF to MSB | MSB → LF | Notification on the further procedure for the order placement |
Transaction and responses
Role of this check identifier: response. Basis: the transaction data carry antwortstatus and antwortstatusCodeliste. The title names no polarity — whether this message confirms or rejects is decided by the response code, not by the check identifier.
Which request this message responds to
| Role | Check identifier | Use case | Message type | Origin of supply |
|---|---|---|---|---|
| Request | 17123 | Order placement for change of metering time period definition | ORDERS | explicit |
In which field the request is quoted
| Reference field of this message | EDIFACT segment | Target field in the request |
|---|---|---|
auftragsReferenz | SG1.RFF+ON | dokumentennummer |
RFF+ON quotes the order number; it appears in the request in segment BGM as dokumentennummer. Measured: 17123 carries dokumentennummer in BGM+Z56.
Response codes
Decision trees: E_0523 · E_0533.
The Prüfi table names 2 further trees across all rows of this check identifier. They bind it to a process, not to a row of its handbook — their codes therefore appear only on the respective tree page.
Check identifiers of the same AHB table: No other check identifier of message type ORDRSP 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 42 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 ordrsp. 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.