Check identifier 77777 — CONTRL
Check identifier 77777 · EDIFACT message type CONTRL · format version 202610
This page is derived from the application handbook
The MACO APP does not carry this check identifier. The complete Prüfi pages of this level are produced from the specifications of the application — one class in the templater per check identifier — and that is where the assignment to the business objects (BO4E) comes from: which object carries which field of the message.
The catalogue of the application handbook is the larger set. This page therefore shows what the handbook itself provides — use case, process context and the AHB field list with its conditions. A data structure according to BO4E is not shown, and not because there is none, but because the application does not form one for this check identifier.
All check identifiers in this situation — and the corresponding figures — are listed by the overview of this version.
Application handbook (AHB)
| Structure (EDIFACT) | Description | Format | 77777 | Condition |
|---|---|---|---|---|
| UNH | — | — | Must | — |
006200010 | Message reference number | — | X | — |
0065 CONTRL00020 | Syntax and service report | — | X | — |
0052 D00030 | Draft version | — | X | — |
0054 300040 | Third issue (CONTRL message) | — | X | — |
0051 UN00050 | UN/CEFACT | — | X | — |
0057 2.0b00060 | Version number of the underlying BDEW message description | — | X | — |
| UCI | — | — | Must | — |
002000070 | Interchange control reference | — | X | — |
000400080 | Sender designation | — | X | — |
0007 1400090 | GS1 | — | X | — |
0007 50000100 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | X | — |
0007 50200110 | DE, DVGW (Deutsche Vereinigung des Gas- und Wasserfaches e.V.) | — | X | — |
001000120 | Recipient designation | — | X | — |
0007 1400130 | GS1 | — | X | — |
0007 50000140 | DE, BDEW (Bundesverband der Energie- und Wasserwirtschaft e.V.) | — | — | — |
0007 50200150 | DE, DVGW (Deutsche Vereinigung des Gas- und Wasserfaches e.V.) | — | X | — |
0083 400160 | This level and all lower levels rejected | — | — | — |
0083 700170 | Transmission confirmed (no syntax errors) | — | X | — |
0085 200180 | Syntax version or level not supported | — | — | — |
0085 700190 | Recipient of the transmission file is not the actual recipient | — | — | — |
0085 1200200 | Invalid value | — | — | — |
0085 1300210 | Missing | — | — | — |
0085 1600220 | Too many components | — | — | — |
0085 2000230 | Character invalid as service character | — | — | — |
0085 2100240 | Invalid character(s) | — | — | — |
0085 2300250 | Unknown sender of the transmission file | — | — | — |
0085 2500260 | Test indicator not supported | — | — | — |
0085 2600270 | Duplicate found | — | — | — |
0085 2800280 | References do not match | — | — | — |
0085 2900290 | Control counter does not correspond to the number of received cases | — | — | — |
0085 3200300 | Lower level empty | — | — | — |
0013 UNA00310 | Separator specification | — | — | — |
0013 UNB00320 | Interchange header segment | — | — | — |
0013 UNZ00330 | Interchange trailer segment | — | — | — |
009800340 | Segment position of the erroneous data element / data element group | — | — | — |
010400350 | Position of the erroneous composite data element | — | — | — |
SG1.UCM 006200360 | Message reference number | — | — | — |
SG1.UCM 0065 APERAK00370 | Application error and acknowledgement message | — | — | — |
SG1.UCM 0065 COMDIS00380 | Trade discrepancy | — | — | — |
SG1.UCM 0065 IFTSTA00390 | Multimodal status report | — | — | — |
SG1.UCM 0065 INSRPT00400 | Check report | — | — | — |
SG1.UCM 0065 INVOIC00410 | Invoice | — | — | — |
SG1.UCM 0065 MSCONS00420 | Report on the consumption of measurable services | — | — | — |
SG1.UCM 0065 ORDCHG00430 | Order change | — | — | — |
SG1.UCM 0065 ORDERS00440 | Order placement | — | — | — |
SG1.UCM 0065 ORDRSP00450 | Order response | — | — | — |
SG1.UCM 0065 PARTIN00460 | Partner master data | — | — | — |
SG1.UCM 0065 PRICAT00470 | Price list/catalog | — | — | — |
SG1.UCM 0065 QUOTES00480 | Quotation | — | — | — |
SG1.UCM 0065 REMADV00490 | Remittance advice | — | — | — |
SG1.UCM 0065 REQOTE00500 | Request | — | — | — |
SG1.UCM 0065 UTILMD00510 | Grid connection master data | — | — | — |
SG1.UCM 0065 UTILTS00520 | Grid usage times message | — | — | — |
SG1.UCM 0052 D00530 | Draft version | — | — | — |
SG1.UCM 005400540 | Release number of the message type of the underlying BDEW message description | — | — | — |
SG1.UCM 0051 UN00550 | UN/CEFACT | — | — | — |
SG1.UCM 005700560 | Version number of the underlying BDEW message description | — | — | — |
SG1.UCM 0083 400570 | This level and all lower levels rejected | — | — | — |
SG1.UCM 008500580 | Syntax error, coded | — | — | — |
SG1.UCM 0085 1200590 | Invalid value | — | — | — |
SG1.UCM 0085 1300600 | Missing | — | — | — |
SG1.UCM 0085 1600610 | Too many components | — | — | — |
SG1.UCM 0085 2100620 | Invalid character(s) | — | — | — |
SG1.UCM 0085 2200630 | Invalid service character(s) | — | — | — |
SG1.UCM 0085 2600640 | Duplicate found | — | — | — |
SG1.UCM 0085 2800650 | References do not match | — | — | — |
SG1.UCM 0085 2900660 | Control counter does not correspond to the number of received cases | — | — | — |
SG1.UCM 0085 3900670 | Data element too long | — | — | — |
SG1.UCM 001300680 | Service segment identifier, coded | — | — | — |
SG1.UCM 0013 UNH00690 | Message header segment | — | — | — |
SG1.UCM 0013 UNT00700 | Message trailer segment | — | — | — |
SG1.UCM 009800710 | Segment position of the erroneous data element / data element group | — | — | — |
SG1.UCM 010400720 | Position of the erroneous composite data element | — | — | — |
SG2.UCS 009600730 | Segment position in the message | — | — | — |
SG2.UCS 008500740 | Syntax error, coded | — | — | — |
SG2.UCS 0085 1300750 | Missing | — | — | — |
SG2.UCS 0085 1500760 | Not supported at this position | — | — | — |
SG2.UCS 0085 1600770 | Too many components | — | — | — |
SG2.UCS 0085 2200780 | Invalid service character(s) | — | — | — |
SG2.UCS 0085 3500790 | Too many segment repetitions | — | — | — |
SG2.UCS 0085 3600800 | Too many segment group repetitions | — | — | — |
SG2.UCD 0085 1200810 | Invalid value | — | — | — |
SG2.UCD 0085 1300820 | Missing | — | — | — |
SG2.UCD 0085 1600830 | Too many components | — | — | — |
SG2.UCD 0085 1900840 | Invalid decimal notation | — | — | — |
SG2.UCD 0085 2100850 | Invalid character(s) | — | — | — |
SG2.UCD 0085 2200860 | Invalid service character(s) | — | — | — |
SG2.UCD 0085 3700870 | Invalid character type | — | — | — |
SG2.UCD 0085 3800880 | Missing digit before the decimal separator | — | — | — |
SG2.UCD 0085 3900890 | Data element too long | — | — | — |
SG2.UCD 0085 4000900 | Data element too short | — | — | — |
SG2.UCD 009800910 | Segment position of the erroneous data element / data element group | — | — | — |
SG2.UCD 010400920 | Position of the erroneous composite data element | — | — | — |
| SG2.UNT | — | — | Must | — |
007400930 | Number of segments in a message | — | X | — |
006200940 | Message reference number | — | X | — |
Editorial — not derived from a source
What this CONTRL refers to. The positive CONTRL confirms a received transmission file as syntactically correct (UCI DE0083 7, »Übertragung bestätigt (keine Syntaxfehler)«, transmission acknowledged, no syntax errors). It names the file, not a single message in it: UCI DE0020 takes over the interchange reference from the UNB of the received file, DE0004 and DE0010 its sender and recipient. No field for this reference is documented in the JSON of the MACO APP: zusatzdaten.contrlReferenz is defined in the BO4E schema, but without a description and used in no interface.
Source: CONTRL AHB (Knowledge Collection ahb/202604/CONTRL and ahb/202610/CONTRL, files 77777.json and 88888.json, segments UCI and UCM); MIG CONTRL (mig/202604/CONTRL.json, description of the segments UCI and UCM); page »Keys and assignment« on contrlReferenz · As of: 2026-09-23 · Applies to format version: 202604, 202610 · To be reviewed by: 2027-04-01
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.
None of the evaluated tables lists a use case for this check identifier. The page therefore carries only the field list of the application handbook — that is the information the source provides.
No process assignment available
For PI_77777, no entry exists in any of the evaluated BDEW tables. Regulatory determination, process step and communication direction can therefore not be stated.
Notes on this page
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 97 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.
All conditions of the message type are listed in the condition index CONTRL.