Check identifier **44022** · EDIFACT message type **UTILMD_GAS** · Format version **202610** ## Data structure

| Structure (BO4E) | Description | Format | 44022 | Condition | |---|---|---|---|---| | **transaktionsdaten** \* | — | object | Must | — | | [dokumentennummer](/en/bo4e/202610/cdoc/Transaktionsdaten#dokumentennummer) \* 00010 | EDIFACT reference from the BGM segment / BGM | string | Must | [500] | | [freitext](/en/bo4e/202610/cdoc/Transaktionsdaten#freitext) 00020 | Free text / FTX+ACB | string | X | — | | [kategorie](/en/bo4e/202610/cdoc/Transaktionsdaten#kategorie) \* 00030 | Qualifier from the beginning of the EDIFACT message / BGM | string | Must | [500] | | [nachrichtendatum](/en/bo4e/202610/cdoc/Transaktionsdaten#nachrichtendatum) \* 00040 | Creation date of the EDIFact / DTM+137 | string (date-time) | X | — | | [nachrichtenreferenznummer](/en/bo4e/202610/cdoc/Transaktionsdaten#nachrichtenreferenznummer) \* 00050 | EDIFACT reference from the UNT segment / UTILMD UNT+21 | string | Must | — | | [pruefidentifikator](/en/bo4e/202610/cdoc/Transaktionsdaten#pruefidentifikator) \* 00060 | Contains the check identifier from the EDIFact communication / RFF+Z13 | string | X | — | | [transaktionsgrund](/en/bo4e/202610/cdoc/Transaktionsdaten#transaktionsgrund) \* 00070 | The transaction reason describes the business transaction for the category in more detail / UTILMD STS+7++###+ZW4+E03 | string | X | — | | [vorgangsnummer](/en/bo4e/202610/cdoc/Transaktionsdaten#vorgangsnummer) \* 00080 | Number of the transaction / UTILMD UTILTS IDE+24 / INSRPT INVOIC DOC | string | X | — | | [vorgangsreferenznummer](/en/bo4e/202610/cdoc/Transaktionsdaten#vorgangsreferenznummer) \* 00090 | Reference number of the transaction of the registration according to WiM / ORDERS RFF+Z41 / IFTSTA RFF+ACW | string | X | — | | **absender** \* | — | object | Must | — | | [rollencodenummer](/en/bo4e/202610/bo/Marktteilnehmer#rollencodenummer) \* 00100 | Specifies the code value of the market role. | string | X | — | | [rollencodetyp](/en/bo4e/202610/bo/Marktteilnehmer#rollencodetyp) \* 00110 | Indicates the type of the code. | [Enum Rollencodetyp](/en/bo4e/202610/enum/Rollencodetyp) | X | — | | `BDEW` | — | — | X | — | | `GS1` | — | — | X | — | | `GLN` | — | — | X | — | | `DVGW` | — | — | X | — | | **empfaenger** \* | — | object | Must | — | | [rollencodenummer](/en/bo4e/202610/bo/Marktteilnehmer#rollencodenummer) \* 00120 | Specifies the code value of the market role. | string | X | — | | [rollencodetyp](/en/bo4e/202610/bo/Marktteilnehmer#rollencodetyp) \* 00130 | Indicates the type of the code. | [Enum Rollencodetyp](/en/bo4e/202610/enum/Rollencodetyp) | X | — | | `BDEW` | — | — | X | — | | `GS1` | — | — | X | — | | `GLN` | — | — | X | — | | `DVGW` | — | — | X | — |

## Application handbook (AHB)

| Structure (EDIFACT) | Description | Format | 44022 | Condition | |---|---|---|---|---| | **UNH** | — | — | Must | — | | `0062`00010 | Message reference number | — | X | — | | `0065 UTILMD`00020 | Grid connection master data | — | X | — | | `0052 D`00030 | Draft version | — | X | — | | `0054 11A`00040 | Edition 2011 - A | — | X | — | | `0051 UN`00050 | UN/CEFACT | — | X | — | | `0057 G1.2`00060 | Version number of the underlying BDEW message description | — | X | — | | **BGM** | — | — | Must | [500] | | `1001 E01`00070 | Registrations | — | X | — | | `1001 E02`00080 | Deregistrations | — | X | — | | `1001 E35`00090 | Contract termination | — | X | — | | `1004`00100 | Document number | — | X | — | | **DTM** | — | — | Must | — | | `2005 137`00110 | Document-/message date/time | — | X | — | | `2380`00120 | Date or time or time span, value | — | X | [931] [494] | | `2379 303`00130 | CCYYMMDDHHMMZZZ | — | X | — | | **SG2.NAD** | — | — | Must | — | | `3035 MS`00140 | Document-/message sender or sender | — | X | — | | `3039`00150 | MP-ID | — | X | — | | `3055 9`00160 | GS1 | — | X | — | | `3055 332`00170 | DE, DVGW Service & Consult GmbH | — | X | — | | **SG2.NAD** | — | — | Must | — | | `3035 MR`00180 | Message recipient | — | X | — | | `3039`00190 | MP-ID | — | X | — | | `3055 9`00200 | GS1 | — | X | — | | `3055 332`00210 | DE, DVGW Service & Consult GmbH | — | X | — | | **SG4.IDE** | — | — | Must | — | | `7495 24`00220 | Transaction | — | X | — | | `7402`00230 | Transaction number | — | X | — | | **SG4.STS** | — | — | Must | [2061] | | `9015 7`00240 | Transaction reason | — | X | — | | `9013 E05`00250 | Cancellation | — | X | — | | **SG4.FTX** | — | — | May | — | | `4451 ACB`00260 | Additional information (for general notes) | — | X | — | | `4440`00270 | Text for general information | — | X | — | | **SG6.RFF** | — | — | Must | — | | `1153 Z13`00280 | Check identifier | — | X | — | | `1154 44022`00290 | GeLi Gas / Request for cancellation | — | X | — | | **SG6.RFF** | — | — | Must | — | | `1153 ACW`00300 | Reference number of a preceding message | — | X | — | | `1154`00310 | Transaction number | — | X | — | | **UNT** | — | — | Must | — | | `0074`00320 | Number of segments in a message | — | X | — | | `0062`00330 | Message reference number | — | X | — |

### Conditions of this table The free text of the 4 conditions referenced by the rows above. All conditions of the message type are listed in the [condition index UTILMDG](/en/referenz/202610/ahb-bedingungen/UTILMDG).

| 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 | | **[500]** | Note: The code is to be selected according to the category of the notification to be canceled | | **[931]** | Format: ZZZ = +00 | | **[2061]** | Segment or segment group must be specified exactly once per SG4 IDE (transaction) |

## 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. :::note{title="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. ::: ## Business classification

| Attribute | Value | |---|---| | Use case (AHB) | Request for cancellation | | AHB | UTILMD AHB gas | | Transmission channel | AS4 |

:::caution{title="This check identifier is used in 4 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 | |---|---|---|---| | GeLi Gas 2.0 | GeLi_Gas 2.0 ch. 1.8 Cancellation | Parties involved as in the original message → Parties involved as in the original message | — | | AWH WiM gas 2.0 | AWH WiM gas 2.0 ch. 2.6 cancellation and reversal (GeLi_Gas 2.0 ch. 1.8 cancellation) | Parties involved as in the original message → Parties involved as in the original message | — | | WiM gas | Ch. A 8 | Sender of a cancellation request → recipient of a cancellation request | — | | GeLi Gas | Ch. A 9 | Parties involved as in the original message → Parties involved as in the original message | — |

:::caution{title="Individual entries from format version 202604"} The check identifiers table of format version 202610 does not carry this entry: **process step**. It comes from version 202604. Version 202604 also carries this check identifier in contexts that the table of version 202610 does not know; they are included in the list above. Everything else on this page — use case, rulebook and communication direction — comes from its own version. Before adopting this into an implementation specification, check whether what is stated applies to 202610. ::: ## 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”. **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 UTILMDG has the same row structure in this version. 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 **44 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.