AHB conditions (18)
Conditions UTILMDG
EDIFACT message type UTILMDG · format version 202610 · 150 conditions · 1 packages · 1 UB conditions · from 88 handbook file(s)
Conditions
| Marker | Condition |
|---|---|
| [1] | If a split is present |
| [2] | If UNH DE0070 (transmission sequence number) with 1 is present |
| [3] | In the case of splitting, in the message with the highest transmission sequence number |
| [4] | If MP-ID in SG2 NAD+MR (message recipient) in the role LF |
| [5] | If MP-ID in SG2 NAD+MS (message sender) in the role LF |
| [7] | If SG4 STS+7++ZG9/ZH1/ZH2 (transaction reason: cancellation of a future assignment due to move-out of the customer / -due to decommissioning / -due to cancelled contractual relationship) is present |
| [9] | If SG4 STS+7++ZE4 (transaction reason: discontinued market location or metering location) is not present |
| [10] | If SG4 STS+Z17 (transaction reason for fixed-term registration) is present |
| [11] | If SG4 STS+7++ZG9/ZH1/ZH2 (transaction reason: cancellation of a future assignment due to move-out of the customer / -due to decommissioning / -due to cancelled contractual relationship) is not present |
| [12] | If SG4 DTM+471 (end at the next possible date) is not present |
| [13] | If SG4 STS+E01++Z01 (status of the response: consent with change of date) is not present |
| [14] | If the date is known |
| [15] | If SG4 STS+E01++Z34 (status of the response: rejection multiple termination) is present |
| [16] | If SG4 STS+E01++Z12 (status of the response: rejection contractual commitment) is present |
| [17] | If a confirmed contract termination by the customer or MP is already present |
| [18] | If SG4 DTM+93 (end as of) is not present |
| [19] | If SG8 SEQ+Z01 (data of the market location) SG10 CCI+++ZC0 (forecast based on values) present |
| [24] | If SG6 DTM+Z21 (date of the grid usage settlement) present |
| [25] | If the reporting point in SG5 LOC+172 (reporting point) DE3225 has the format of the market location ID |
| [26] | If the reporting point in SG5 LOC+172 (reporting point) DE3225 has the format of the metering point identifier |
| [28] | If SG4 DTM+93 (end as of) is present |
| [29] | If balancing takes place |
| [32] | If BGM+E03 (change notifications) present |
| [33] | If an end of balancing is present in the deregistration |
| [35] | If the DE2380 of SG4 DTM+Z01 (notice period of the contract) contains T (date) in the fourth position |
| [36] | If SG4 STS+E01++ZC5 (status of the response: rejection, another registration in progress) is present |
| [37] | If the registration/change is limited in time |
| [39] | If LF intends to transmit a meter reading |
| [46] | If in SG8 SEQ+Z35 a SG10 CCI+Z12 (load profile) CAV (load profile) DE3055 contains the value 293 |
| [47] | If in SG8 SEQ+Z35 a SG10 CCI+Z12 (load profile) CAV (load profile) DE3055 does not contain the value 293 |
| [48] | If the STS+E01++E14 (status of the response: rejection other) is present in this SG4 |
| [51] | For retroactive end of supply / start of supply |
| [58] | If in this CCI the DE3055 with the code 293 is present |
| [64] | If SG4 DTM+158 (start of balancing) is present |
| [65] | If a market area over-lap exists, all balancing groups of the LF in which free capacities exist at the NB must be reported |
| [66] | If SG10 CCI+Z19 (balancing group) is present more than once in the transaction |
| [68] | If SG10 CCI+Z19 (balancing group) is present more than twice in the transaction |
| [69] | If SG10 CCI+Z19 (balancing group) is present more than three times in the transaction |
| [70] | If SG10 CCI+Z19 (balancing group) is present five times in the transaction |
| [77] | If SG8 SEQ+Z03 (metering device data) CAV+Z30 (identification/number of the device) is not present |
| [78] | If SG4 STS+7++E02 (transaction reason: move-in to creation) is not present |
| [81] | If SG4 FTX+ABO+Z05 (description of the deviation from the transmitted list: change present) present |
| [84] | If SG4 STS+E01++Z35 (status of the response: rejection of the deregistration request) is present |
| [92] | If a value within the SG or segment is changed |
| [98] | If MP-ID in SG2 NAD+MS (message sender) in the role NB |
| [106] | If in this SG8 SEQ+Z01 SG10 CCI+++ZA6 (forecast basis of the market location: forecast based on profiles) is present |
| [108] | If customer value method (e.g. TU München) |
| [123] | If at least one further SG8 SEQ+Z20 (OBIS data of the metering device / volume corrector) references the same identification/number of the device with the SG8 RFF+MG / Z11 (device number of the meter / volume corrector) |
| [127] | If the supplier knows on the basis of its contract that the customer does not have a high KA, it must notify the NB of this |
| [128] | If SG10 CAV+TAS/TKS/SAS/KAS present |
| [129] | If the supplier knows the amount of the Sonder-KA on the basis of its contract, it must notify the NB of it |
| [130] | If present at the metering location |
| [133] | If present at the transmitted market location / metering location |
| [137] | Not for creation |
| [138] | If SG5 LOC+172 (reporting point) is not present |
| [147] | If present in the request |
| [165] | If known |
| [166] | If present |
| [200] | If BGM+Z26 (preliminary notification for market area conversion) present |
| [202] | If SG4 STS+E01+ZG2 (status of the response: valid result after the data check) is present |
| [203] | If STS+7++E06 / Z39 / ZC6 / ZC7 / ZT6 / ZT7 / Z02 / ZZD |
| [205] | If SG9 QTY+Y02 (TUM customer value) is not present |
| [209] | If code 303 is present in DE2379 in the same segment |
| [212] | If NAD DE3124 is not present in the same SG12 |
| [213] | If SG12 NAD+Z09 (customer of the supplier) is present |
| [216] | If CCI+++Z88 (grid usage) CAV+Z74:::Z08 (grid usage contract: direct contract between customer and NB) present |
| [219] | If present at the market location |
| [230] | Resulting date or end date of the cycle period from DTM+Z21 (date of the grid usage settlement) and DTM+Z09 (next grid usage settlement) must be >= DTM+92 (start on) |
| [241] | If MP-ID in SG2 NAD+MR (message recipient) in the role MSB |
| [249] | Within one SG4 IDE, all DE1131 of the SG4 STS+E01 must contain the identical value |
| [252] | If DE0068 is present |
| [257] | If in the same SG8 SEQ+Z02 (OBIS data of the market location) the PIA+5+7-0?:33.86.0 is present |
| [268] | If an "X" is listed for the code in DE3207 in the column "PLZ present" of the "EDI@Energy code list of European country codes" |
| [274] | If in the same SG8 SEQ+Z20 (OBIS data of the metering device / volume corrector) the PIA+5+7-b?:3.0.0 / 7-b?:6.0.0 / 7-b?:3.1.0 / 7-b?:6.1.0 / 7-b?:3.2.0 / 7-b?:6.2.0 / 7-b?:13.2.0 / 7-b?:16.2.0 / 7-b?:1.0.0 / 7-b?:2.0.0 / 7-b?:4.0.0 / 7-b?:5.0.0 / 7-b?:11.2.0 / 7-b?:12.2.0 / 7-b?:14.2.0 / 7-b?:15.2.0 is present |
| [283] | If the recipient of the message is the supplier currently assigned as at the message date |
| [315] | All OBIS codes in accordance with EDI@Energy code list of OBIS codes and media for the German energy market, chapter 4, that are required at the market location must be stated; the minimum scope from chapter 4.6 must be observed. The minimum scope of the OBIS codes results from the metering product codes stated in chapter 5.2 of the document "Code list of configurations" |
| [324] | All OBIS codes in accordance with EDI@Energy code list of OBIS codes chapter 4. that are used at the metering device must be stated. The minimum scope of the OBIS codes results from the metering product codes stated in chapter 5.2 of the document "Code list of configurations" |
| [328] | If IMD++Z36+Z12 (identification logic: market location ID) present |
| [333] | If IMD+Z36+Z13 (identification logic: all identification data) present |
| [336] | If filled in the change notification |
| [345] | If a 33-character reporting point is present in SG5 LOC+172 (reporting point) |
| [361] | If STS+E01++A03/A04 not present |
| [362] | If STS+E01++A03/A17 not present |
| [367] | If SG4 STS+E01++A04 is present |
| [368] | All codes from the code list G_0009 are permitted |
| [427] | Metering product code from chapter 3 "Code list of the standard metering products gas" of the code list of configurations |
| [442] | If the device number of the meter named in this RFF DE1154 is present in no SG8+SEQ+Z09 volume converter data in the RFF+MG (reference to the device number) |
| [490] | if the value in this DE, at position CCYYMMDDHHMM, is a point in time within the period stated in the table in chapter 3.5 “Overview of German statutory summer time (MESZ)” in the columns: “Summer time (MESZ) from” representation in UTC and “Summer time (MESZ) to” representation in UTC. |
| [491] | if the value in this DE, at position CCYYMMDDHHMM, is a point in time within the period stated in the table in chapter 3.6 “Overview of German statutory time (MEZ)” in the columns: “Winter time (MEZ) from” representation in UTC and “Winter time (MEZ) to” representation in UTC. |
| [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 |
| [501] | Note: The specification is taken from the DTM+157 (change as of) of the allocation list |
| [502] | Note: Replacement supply exists only for - market locations at the low pressure level that are not household customers as defined by the EnWG and that are no longer subject to statutory substitute supply (three months) and - for market locations that are to be supplied at medium pressure. The basis for a replacement supply is the bilateral agreement |
| [504] | Note: Code Z22 is also used in the electricity division. The reference to the feed-in tariff interval is not relevant in the gas division |
| [505] | Note: Transitional supply exists only for market locations that fall under § 38a EnWG. The basis is a bilateral agreement |
| [507] | Note: Start date originally confirmed by the NB |
| [508] | Note: Start date at the new NB |
| [510] | Note: To be used for the deregistration of the ESV |
| [511] | Note: To be used for the deregistration of the transitional supply |
| [513] | Note: If SG9 QTY+Y02 (TUM customer value) is present, then only SG9 QTY+Y02, irrespective of SG9 QTY+31 (total estimated annual quantity), is to be used for balancing and MMM billing |
| [527] | Note: The ID of the market location and all identifiers of the metering locations must be specified |
| [528] | Note: The date/dates from the request must be used |
| [530] | Note: All data existing at the reporting point that are transmitted with this segment group and are valid on the date “change as of” must be specified. This may mean that segment groups or segments have to be repeated |
| [556] | Note: If no correspondence address of the end consumer/customer is available, the address of the market location must be transmitted |
| [558] | Note: This information can be exchanged voluntarily |
| [559] | Note: The correspondence address of the end consumer/customer is not used for identification |
| [560] | Note: The name and address details for the meter reading card are not used for identification |
| [566] | Note: previous supplier |
| [567] | Note: New supplier |
| [570] | Note: Old grid operator |
| [571] | Note: Triggering market partner (LFA for STS+7++ZG9, LFN for STS+7++ZH0, NB for STS+7++ZH1) |
| [572] | Note: Customer name from registration new supplier |
| [573] | Note: If no other information for „name and address for the meter reading card“ is available, the segment is composed of the customer name in NAD+Z09 and the address from the correspondence address NAD+Z04 |
| [576] | Note: Master data of the previous metering point operator |
| [577] | Note: Filled with the start date originally confirmed by the NB |
| [581] | Note: The next possible contract termination date must be specified |
| [583] | Note: Use of the ID of the market location |
| [584] | Note: Use of the ID of the metering location |
| [590] | Note: The ID of the market location assigned to the LF and all identifiers of the metering locations must be specified |
| [601] | Note: The ID of the market location and all identifiers of the metering locations must be specified. |
| [621] | Note: The MSB must be specified that is assigned to the location from the point in time named in DTM+76 (date of the planned start of supply). |
| [622] | Note: If the OBIS code is relevant for several market roles, the segment group must be repeated for each market role |
| [636] | Note: Using a code in DE1153, this RFF classifies the DTM contained in the same segment group as content relevant to a market location or metering location |
| [637] | Note: In the case of a commitment request |
| [638] | Note: In the event of a request to take over the individual metering location by the gMSB |
| [643] | Note: Subsequent grid operator |
| [644] | Note: If the associated registration (44001) contains "move-in to creation" (SG4 STS+7++E02) in this segment, the code E01 is used in this business transaction |
| [651] | Note: In the case of a market area conversion (gas), note that the actual notification of the market area conversion takes place at the level of the metering location by specifying the gas quality. The affected market location must be determined by the LF and MSB themselves |
| [654] | Note: Only the data on the reporting point that are relevant for the market partner addressed in NAD+MR (message recipient) must be specified |
| [655] | Note: If a meter is connected to a volume corrector, no OBIS code numbers are stated at the meter Here there are only OBIS code numbers from the volume corrector |
| [902] | Format: Possible value: ≥ 0 |
| [907] | Format: max. 4 decimal places |
| [912] | Format: max. 6 decimal places |
| [930] | Format: max. 2 decimal places |
| [931] | Format: ZZZ = +00 |
| [934] | Format: HHMM = 0400 |
| [935] | Format: HHMM = 0500 |
| [937] | Format: no decimal places |
| [938] | Format: Possible value: <= 10 |
| [950] | Format: market location ID |
| [951] | Format: Metering point identifier |
| [952] | Format: device number according to DIN 43863-5 |
| [953] | Format: market location ID or metering point identifier |
| [2061] | Segment or segment group must be specified exactly once per SG4 IDE (transaction) |
| [2119] | The segment group must be specified exactly once per SG8 SEQ+Z13 (smart meter gateway) |
| [2284] | To be given exactly once for each metering location ID in SG5 LOC+172 (reporting point) DE3225 |
| [2286] | To be given at least once for each SEQ+Z18 (data of the metering location) |
| [2287] | To be given at least once for each SEQ+Z03 (metering device data) |
| [2335] | To be given exactly once for each SEQ+Z02 (OBIS data of the market location) that transmits the OBIS code 7-20:99.33.17/7-0:33.86.0 in PIA+5 |
| [2353] | To be given at least once for each SEQ+Z09 (volume corrector data) |
UB conditions
UB conditions combine several markers into a single expression. In the handbook rows they appear like a condition, but they resolve into the markers they contain.
| Marker | Printout |
|---|---|
| [UB2] | ([931] ∧ [934] [490]) ⊻ ([931] ∧ [935] [491]) |
Condition packages
Condition packages bundle prerequisites.
| Package | Prerequisites | Conditions |
|---|---|---|
| [1P] | -- | Note: This is the standard package if no condition applies. |
Notes on this page
This page carries the free text of every condition that the application handbook of message type UTILMDG references in this format version. A row of the handbook writes Muss [704]; what [704] requires is here.
The list applies to the message type, not to a single check identifier. This is not a simplification but the form of the source: the condition list is present identically in every handbook file of the format.
Why no assignment to individual check identifiers is given here
The intermediate format from which this documentation reads the handbook rows assigns conditions to a column — and this assignment is shifted against the original. Measured on 05.09.2026 against UTILMD electricity: the handbook lists STS DE9013 as X [360] (approval codes only) for check identifier 55017 and X [359] (rejection codes only) for 55018; the intermediate format puts [360] on 55016 and [359] on 55017 and 55018. The same applies to FTX Muss [83]: at 55018 in the handbook, at 55017 in the intermediate format.
Independently confirmed by the change lists of the source: change IDs 25242, 25821, 25822, 25445 and 25243 explicitly locate [83], [351] and [352] in „Use case 55018 Rejection of contract termination“. No entry assigns them to 55016 or 55017.
That is why the text of every condition is given here and nowhere the claim as to which condition applies to which check identifier. Anyone who needs that looks it up in the original application handbook.
1 condition does not appear in every handbook file
The list of conditions is meant to apply across the whole format, but it does not everywhere: the following markers occur in fewer than all 88 files of this format. They are given here nonetheless — leaving out a condition because one file does not carry it would mean letting a reference point into the void again.
[UB2]
As measured on 05.09.2026, no ahb_expression in this source points to a package marker — the condition packages are listed on this page because the source carries them, not because a handbook line refers to them.