Check identifier 19123 — Rejection complaint about a definition
Check identifier 19123 · EDIFACT message type ORDRSP · Format version 202610
Data structure
| Structure (BO4E) | Description | Format | 19123 | Condition |
|---|---|---|---|---|
| transaktionsdaten * | — | object | Must | — |
| anfragereferenznummer 00010 | Reference transaction number 'from request message' / ORDERS RFF+TN / IFTSTA RFF+AAV / INSRPT RFF+TN RFF+AAV | string | X | — |
| antwortstatus * 00020 | Response status / STS+E01 | string | Must | — |
| antwortstatusCodeliste * 00030 | Response status code list / STS+E01 | string | Must | — |
| auftragsReferenz * 00040 | Order number 'purchasing' / RFF+ON | string | X | — |
| dokumentennummer * 00050 | EDIFACT reference from the BGM segment / BGM | string | X | — |
| freitext 00060 | Free text / FTX+ACB | 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 | — |
| vorgangsreferenznummer 00100 | Reference number of the transaction of the registration according to WiM / ORDERS RFF+Z41 / IFTSTA RFF+ACW | string | X | — |
| absender * | — | 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 | — |
| empfaenger * | — | object | Must | — |
| rollencodenummer * 00130 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp * 00140 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
Application handbook (AHB)
| Structure (EDIFACT) | Description | Format | 19123 | 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 Z5500070 | Complaint about the overview of the definitions or about a single definition | — | 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 ACW00140 | Reference number of a preceding message | — | X | — |
115400150 | Reference of a preceding message | — | X | ([60] ∧ [63]) ⊻ ([61] ∧ [64]) ⊻ ([62] ∧ [65]) |
| SG1.RFF | — | — | Must | — |
1153 TN00160 | Transaction reference number | — | X | — |
115400170 | Reference transaction number | — | X | ([70] ∧ [53]) ⊻ ([71] ∧ [54]) ⊻ ([52] ∧ [55]) |
| SG1.RFF | — | — | Must | — |
1153 Z1300180 | Check identifier | — | X | — |
1154 1912300190 | Rejection of the complaint about a definition | — | X | — |
| SG2.AJT | — | — | Must | — |
446500200 | Code of the check step | — | X | — |
1082 E_054400210 | EBD no. E_0544 | — | X | [3P0..1] |
1082 E_054500220 | EBD no. E_0545 | — | X | [4P0..1] |
1082 E_054600230 | EBD no. E_0546 | — | X | [5P0..1] |
1082 E_054700240 | EBD no. E_0547 | — | X | [6P0..1] |
1082 E_054800250 | EBD no. E_0548 | — | X | [3P0..1] |
1082 E_054900260 | EBD no. E_0549 | — | X | [4P0..1] |
1082 E_055000270 | EBD no. E_0550 | — | X | [5P0..1] |
1082 E_055100280 | EBD no. E_0551 | — | X | [6P0..1] |
| SG2.FTX | — | — | Must | [28] |
4451 AAP00290 | Response (free text) | — | X | — |
444000300 | Free text | — | X | — |
| SG3.NAD | — | — | Must | — |
3035 MS00310 | Document-/message sender or sender | — | X | — |
303900320 | MP-ID | — | X | [30] |
3055 900330 | GS1 | — | X | — |
3055 29300340 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
| SG3.NAD | — | — | Must | — |
3035 MR00350 | Message recipient | — | X | — |
303900360 | MP-ID | — | X | [30] |
3055 900370 | GS1 | — | X | — |
3055 29300380 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
| 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 21 conditions referenced by the rows above. All conditions of the message type are listed in the condition index ORDRSP.
| Marker | Condition |
|---|---|
| [28] | If AJT+A99 present |
| [30] | MP-ID only from division electricity |
| [52] | if the complaint was a complaint about the rolled-out load curve definitions |
| [53] | Transaction number from IDE DE7402 of the UTILTS with BGM+Z59 |
| [54] | Transaction number from IDE DE7402 of the UTILTS with BGM+Z80 |
| [55] | Transaction number from IDE DE7402 of the UTILTS with BGM+Z81 |
| [60] | if the complaint was a complaint about the overview of metering time definitions |
| [61] | if the complaint was a complaint about the overview of switching time definitions |
| [62] | if the complaint was a complaint about the overview of load curve definitions |
| [63] | Document number from BGM+Z60 DE1004 of the UTILTS |
| [64] | Document number from BGM+Z78 DE1004 of the UTILTS |
| [65] | Document number from BGM+Z79 DE1004 of the UTILTS |
| [70] | if the complaint was a complaint about the rolled-out metering time definitions |
| [71] | if the complaint was a complaint about the rolled-out switching time definitions |
| [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 |
| [3P0..1] | [3 ] If MP-ID in SG3 NAD+MS with role NB present [4] If MP-ID in SG3 NAD+MR with role LF present |
| [4P0..1] | [3] If MP-ID in SG3 NAD+MS with role NB present [14] If MP-ID in SG3 NAD+MR with role MSB present |
| [5P0..1] | [5] If MP-ID in SG3 NAD+MS with role LF present [15] If MP-ID in SG3 NAD+MR with role NB present |
| [6P0..1] | [5] If MP-ID in SG3 NAD+MS with role LF present [14] If MP-ID in SG3 NAD+MR with role MSB present |
Example message
UNA:+.? '
UNB+UNOC:3+9900327000009:500+9979015000001:500+{{date}}:{{time}}+DASOQTZDOUMNUL'
UNH+DAYTEATHFTCIFU+ORDRSP:D:10A:UN:1.4c'
BGM+Z55+DA232411191205089903323000007510196'
DTM+137:202610011100?+00:303'
RFF+ON:AFN9523'
RFF+Z13:19123'
AJT+A99+E_0548'
FTX+AAP+++Keine Zeit'
NAD+MS+9900327000009::293'
NAD+MR+9979015000001::293'
UNS+S'
UNT+11+DAYTEATHFTCIFU'
UNZ+1+DASOQTZDOUMNUL'[1 item
{6 fields
"data": {3 fields
"stammdaten": {1 field
"ANFRAGE": [1 item
{3 fields
"transaktionsdaten": {13 fields
"absender": {5 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.
Business classification
| Attribute | Value |
|---|---|
| Use case (AHB) | Rejection of complaint about a definition |
| AHB | ORDRSP AHB |
| Decision tree | E_0544 · E_0545 · E_0546 · E_0547 · E_0548 · E_0549 · E_0550 · E_0551 |
| Transmission channel | AS4 |
This check identifier is used in 8 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 | Complaint about the overview of the definitions of the NB from LF to NB | NB → LF | Rejection of the complaint |
| GPKE part 3 | Complaint about the overview of the definitions of the NB from MSB to NB | NB → MSB | Rejection of the complaint |
| GPKE part 3 | Complaint about the overview of the definitions of the LF from NB to LF | LF → NB | Rejection of the complaint |
| GPKE part 3 | Complaint about the overview of the definitions of the LF from MSB to LF | LF → MSB | Rejection of the complaint |
| GPKE part 3 | Complaint about a definition of the NB from LF to NB | NB → LF | Rejection of the complaint |
| GPKE part 3 | Complaint about a definition of the NB from MSB to NB | NB → MSB | Rejection of the complaint |
| GPKE part 3 | Complaint about a definition of the LF from NB to LF | LF → NB | Rejection of the complaint |
| GPKE part 3 | Complaint about a definition of the LF from MSB to LF | LF → MSB | Rejection of the complaint |
Transaction and responses
Role of this check identifier: response — rejection. Basis: the transaction data carry antwortstatus and antwortstatusCodeliste; the title names a polarity (rejection).
Which request this message responds to
| Role | Check identifier | Use case | Message type | Origin of supply |
|---|---|---|---|---|
| Request | 17122 | Complaint about a definition | ORDERS | from the step sequence |
In which field the request is quoted
| Reference field of this message | EDIFACT segment | Target field in the request |
|---|---|---|
anfragereferenznummer | SG1.RFF+TN | — |
For RFF+TN, the field description of the time slice names the »reference transaction number (from request message)« — the target is the vorgangsnummer in segment SG4.IDE+24 of the request. Request 17122, however, does not carry vorgangsnummer — the assignment therefore does not apply here, and the target field remains open.
Response codes
Decision trees: E_0544 · E_0545 · E_0546 · E_0547 · E_0548 · E_0549 · E_0550 · E_0551.
The Prüfi table names 8 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 54 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.