Check identifier 66666 — APERAK
Check identifier 66666 · EDIFACT message type APERAK · format version 202610
Data structure
| Structure (BO4E) | Description | Format | 66666 | Condition |
|---|---|---|---|---|
| stammdaten * | — | object | Must | — |
| STATUSBERICHT [ ] * | — | object[] | Must | — |
| datumPruefung * 00010 | Check date (when the item under check was checked) | string (date-time) | X | — |
| pruefgegenstand * 00020 | The checked document, e.g. the reference to the EDIFACT message that was checked / objected to | string | X | — |
| transaktionsdaten * | — | object | Must | — |
| dokumentennummer * 00030 | EDIFACT reference from the BGM segment / BGM | string | Must | — |
| kategorie * 00040 | Qualifier from the beginning of the EDIFACT message / BGM | string | Must | — |
| 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 | — |
| absender * | — | object | Must | — |
| rollencodenummer * 00070 | Specifies the code value of the market role. | string | X | — |
| rollencodetyp * 00080 | Indicates the type of the code. | Enum Rollencodetyp | X | — |
BDEW | — | — | X | — |
GS1 | — | — | X | — |
GLN | — | — | X | — |
DVGW | — | — | X | — |
| empfaenger * | — | 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 | — |
Application handbook (AHB)
| Structure (EDIFACT) | Description | Format | 66666 | Condition |
|---|---|---|---|---|
| UNH | — | — | Must | — |
006200010 | Message reference number | — | X | — |
0065 APERAK00020 | Application error and acknowledgement message | — | X | — |
0052 D00030 | Draft version | — | X | — |
0054 07B00040 | Edition 2007 - B | — | X | — |
0051 UN00050 | UN/CEFACT | — | X | — |
0057 2.200060 | Version number of the underlying BDEW message description | — | X | — |
| BGM | — | — | Must | — |
1001 31200070 | Acknowledgment message | — | X | — |
1001 31300080 | Application system error message | — | — | — |
100400090 | Document number | — | X | — |
| DTM | — | — | Must | — |
2005 13700100 | Document-/message date/time | — | X | — |
238000110 | Date or time or time span, value | — | X | [931] [494] |
2379 30300120 | CCYYMMDDHHMMZZZ | — | X | — |
| SG2.RFF | — | — | Must | — |
1153 ACE00130 | Number of the associated document | — | X | — |
115400140 | Reference, identification | — | X | — |
| SG2.DTM | — | — | Must | — |
2005 17100150 | Reference date/time | — | X | — |
238000160 | Date or time or time span, value | — | X | [931] |
2379 30300170 | CCYYMMDDHHMMZZZ | — | X | — |
| SG2.RFF | — | — | Must | — |
1153 AGO00180 | Sender reference for the original message | — | X | — |
115400190 | Document number of the referenced message | — | X | — |
| SG2.RFF | — | — | Must | — |
1153 TN00200 | Transaction reference number | — | X | — |
115400210 | Transaction number of the referenced transaction | — | X | — |
| SG3.NAD | — | — | Must | — |
3035 MS00220 | Document-/message sender or sender | — | 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 | — | — | — |
| SG3.NAD | — | — | Must | — |
3035 MR00270 | Message recipient | — | X | — |
303900280 | MP-ID | — | X | — |
3055 900290 | GS1 | — | X | — |
3055 29300300 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
3055 33200310 | DE, DVGW Service & Consult GmbH | — | X | — |
SG4.ERC 9321 Z1000320 | ID unknown | — | — | — |
SG4.ERC 9321 Z1700330 | Sender is not assigned to the object for the specified time interval / point in time | — | — | — |
SG4.ERC 9321 Z1800340 | Recipient is not assigned to the object at the specified time interval / point in time | — | — | — |
SG4.ERC 9321 Z1900350 | Device number not known for the specified time interval / point in time at the metering location | — | — | — |
SG4.ERC 9321 Z2000360 | OBIS code for the specified time interval / point in time not known at the object | — | — | — |
SG4.ERC 9321 Z2100370 | Referencing within the business transaction is faulty | — | — | — |
SG4.ERC 9321 Z2400380 | Assignment tuple unknown | — | — | — |
SG4.ERC 9321 Z2500390 | Sender is not assigned to the object identified by the assignment tuple for the specified time interval / point in time | — | — | — |
SG4.ERC 9321 Z2600400 | Recipient is not assigned to the object identified by the assignment tuple at the specified time interval / point in time | — | — | — |
SG4.ERC 9321 Z2700410 | Number of integer digits of the meter reading is too long | — | — | — |
SG4.ERC 9321 Z3000420 | Time series incomplete | — | — | — |
SG4.ERC 9321 Z3300430 | Referenced business transaction tuple does not exist | — | — | — |
SG4.ERC 9321 Z4200440 | Configuration ID not known for the specified time interval / point in time | — | — | — |
SG4.ERC 9321 Z4300450 | Business transaction not permitted for object with this attribute | — | — | — |
SG4.ERC 9321 Z4400460 | Property of the object differs from the property coded in the business transaction | — | — | — |
SG4.ERC 9321 Z1400470 | Object not found in the IT system | — | — | — |
SG4.ERC 9321 Z1500480 | Object not unique in the IT system | — | — | — |
SG4.ERC 9321 Z1600490 | Object no longer in the grid area | — | — | — |
SG4.ERC 9321 Z2900500 | Required information for this use case is missing | — | — | — |
SG4.ERC 9321 Z3100510 | Business transaction is rejected by the recipient | — | — | — |
SG4.ERC 9321 Z3400520 | Time interval negative or zero | — | — | — |
SG4.ERC 9321 Z3500530 | Format not complied with | — | — | — |
SG4.ERC 9321 Z3700540 | Business transaction must not be sent by the sender | — | — | — |
SG4.ERC 9321 Z3800550 | Number of transmitted codes exceeds the package definition | — | — | — |
SG4.ERC 9321 Z3900560 | Code not from the permitted value range | — | — | — |
SG4.ERC 9321 Z4000570 | Segment or segment group repeatability exceeded | — | — | — |
SG4.ERC 9321 Z4100580 | Time specification implausible | — | — | — |
SG4.FTX 4451 ABO00590 | Information about deviation | — | — | — |
SG4.FTX 444000600 | Free text | — | — | — |
SG5.RFF 1153 ACW00610 | Reference number of a preceding message | — | — | — |
SG5.RFF 115400620 | Reference, identification | — | — | — |
SG5.RFF 1153 AGO00630 | Sender reference for the original message | — | — | — |
SG5.RFF 115400640 | Reference, identification | — | — | — |
SG5.FTX 4451 AAO00650 | Error description (free text) | — | — | — |
SG5.FTX 444000660 | Free text | — | — | — |
SG5.FTX 4451 Z0200670 | Location of the AHB error | — | — | — |
SG5.FTX 444000680 | Free text | — | — | — |
SG5.RFF 1153 TN00690 | Transaction reference number | — | — | — |
SG5.RFF 115400700 | Transaction number of the referenced transaction | — | — | — |
SG5.FTX 4451 AAO00710 | Error description (free text) | — | — | — |
SG5.FTX 444000720 | Free text | — | — | — |
SG5.FTX 4451 Z0200730 | Location of the AHB error | — | — | — |
SG5.FTX 444000740 | Free text | — | — | — |
SG5.RFF 1153 Z0800750 | MP-ID of the subsequent grid operator | — | — | — |
SG5.RFF 115400760 | MP-ID | — | — | — |
| SG5.UNT | — | — | Must | — |
007400770 | Number of segments in a message | — | X | — |
006200780 | Message reference number | — | X | — |
Conditions of this table
The free text of the 2 conditions referenced by the rows above. All conditions of the message type are listed in the condition index APERAK.
| 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 |
| [931] | Format: ZZZ = +00 |
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.
No process assignment available
For PI_66666, no entry exists in any of the evaluated BDEW tables. Regulatory determination, process step and communication direction can therefore not be stated.
Transaction and responses
Role of this check identifier: response message. Basis: the message type. An APERAK is an acknowledgement (BGM 312) or an application error message (BGM 313) about a received message and cites it via RFF+ACE (number of the related document), RFF+AGO (sender's reference of the original message) and RFF+TN (transaction number of the referenced transaction) — as in the APERAK application handbook from 202610; the file of format version 202604 has no lines. The check identifier table gives it neither a title nor an action.
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 APERAK has the same row structure in this version.
Editorial — not derived from a source
How the APERAK cites the checked message, in the JSON. In the test case Z10_Testfall1 the back references are in these fields: RFF+ACE (number of the related document) in STATUSBERICHT.pruefgegenstand, RFF+ACW (reference number of a previous message) in fehler.fehlerDetails → ursache.dokument, RFF+AGO (sender's reference of the original message, the document number of your message) in ursache.nachricht and RFF+TN (transaction number of the referenced transaction) in ursache.transaktion. The APERAK's own interchange reference is in transaktionsdaten.datenaustauschreferenz.
Source: Test set maco-edi-testfiles, inbound/v202404/APERAK/Z10_Testfall1_eingehend (EDIFACT and JSON of the same test case, compared on 23.09.2026); application handbook APERAK 202610 (Knowledge Collection ahb/202610/APERAK) · As of: 2026-09-23 · Applies to format version: 202604, 202610 · To be reviewed by: 2027-04-01
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 88 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.
No test case exists for this check identifier in the test data of the format version. There is therefore no example message here — not even a reconstructed one: on a page that promises evidence, an invented message would be worse than none.