AHB conditions (18)
Conditions REQOTE
EDIFACT message type REQOTE · format version 202610 · 91 conditions · 1 packages · 2 UB conditions · from 5 handbook file(s)
Conditions
| Marker | Condition |
|---|---|
| [1] | If DTM+203 (execution date) not present. |
| [2] | If DTM+469 (start at the (earliest possible date)) not present. |
| [10] | MP-ID only from division electricity |
| [15] | If DTM+76 (date of the planned start of service) not present |
| [16] | If SG1 RFF+Z41 (reference number of the registration transaction pursuant to WiM) not present. |
| [17] | If SG1 RFF+Z41 (reference number of the registration transaction pursuant to WiM) present. |
| [18] | If IMD++Z55 (change of configuration) present. |
| [19] | If SG27 LIN++Z64 (Required product switching time definitions) is present. |
| [20] | If SG27 LIN++Z65 (Required product power curve definitions) is present. |
| [21] | If SG27 LIN++Z66 (Required product ad hoc control channel) is present. |
| [22] | If SG27 LIN++Z67 (Required metering product for values of type 2 from backend) is present. |
| [23] | If SG27 LIN++Z68 (Required product configuration permission for values of type 2 from SMGW) is present. |
| [24] | If the product is to be ordered. |
| [25] | If the ID of a market location is specified in LOC+172 DE3225 (reporting point). |
| [26] | If the ID of a metering location is specified in LOC+172 DE3225 (reporting point). |
| [27] | If the ID of a grid location is specified in LOC+172 DE3225 (reporting point). |
| [28] | If the ID of a controllable resource is specified in LOC+172 DE3225 (reporting point). |
| [29] | Only the configuration products are permitted that are contained in chapter 4.1 „Configuration products switching time definition“ of the code list of configurations. |
| [30] | Only the configuration products are permitted that are contained in chapter 4.2 „Configuration products power curve definition“ of the code list of configurations. |
| [31] | Only the configuration products are permitted that are contained in chapter 4.3 „Configuration products ad-hoc control channel“ of the code list of configurations. |
| [32] | Only the metering products are permitted that are contained in chapter 4.5 „Metering products for values according to type 2 from the backend for LF and NB“ of the code list of configurations. |
| [33] | Only the metering products are permitted that are contained in chapter 4.4 „Metering products with configuration permission for values according to type 2 from SMGW“ of the code list of configurations. |
| [35] | If MP-ID in SG11 NAD+MS with role LF is present. |
| [36] | If MP-ID in SG11 NAD+MS with role NB is present. |
| [37] | Only the metering product position codes are permitted that are contained in chapter 4.7 „Type of values for metering products according to type 2“ of the code list of configurations. |
| [38] | If within the same SG27 LIN a product is specified in PIA+5 DE7140 (Required product configuration permission for values of type 2 from SMGW) that is marked in the code list of configurations in chapter 4.4 „Metering products with configuration permission for values of type 2 from SMGW“ in the column "Trigger" with the value "When falling below / exceeding the threshold value". |
| [39] | If code EM is present in DE3155 in the same COM. |
| [40] | If code TE / FX / AJ / AL is present in DE3155 in the same COM. |
| [41] | Only the metering products are permitted that are contained in chapter 4.6.1 „Values according to type 2 from the backend“ of the code list of configurations. |
| [42] | Only the metering products are permitted that are contained in chapter 4.6.2 „Values according to type 2 from SMGW“ of the code list of configurations. |
| [43] | If within the same SG27 LIN a product is specified in PIA+5 DE7140 (Required product configuration permission for values of type 2 from SMGW) that is marked in the code list of configurations in chapter 4.6.2 „Values of type 2 from SMGW“ in the column "Trigger" with the value "When falling below / exceeding the threshold value". |
| [44] | If in SG27 LIN (required product of the metering location) the PIA+5 DE7140 is present with a product code that is present in the code list of configurations in chapter 7 "Products for the order placement of a change at a location" in the "column designation" with the value "further energy flow direction". |
| [45] | If the ID of a controllable resource is specified in LOC+172 DE3225 (reporting point). |
| [47] | Only the product codes are permitted that are present with the value "Metering location" in the column "Level" in chapter 7 "Products for the order placement of a change at a location" of the code list of configurations. |
| [48] | Furthermore, only the product codes are permitted that are marked with an "X" in the column "NB" within the column "Product orderable from MSB by market role" in chapter 7 "Products for the order placement of a change at a location" of the code list of configurations. |
| [49] | Furthermore, only the product codes are permitted that are marked with an "X" in the column "LF" within the column "Product orderable from MSB by market role" in chapter 7 "Products for the order placement of a change at a location" of the code list of configurations. |
| [50] | Only the product codes are permitted that are present with the value "Grid location" in the column "Level" in chapter 7 "Products for the order placement of a change at a location" of the code list of configurations. |
| [51] | Only the product codes are permitted that are present with the value "Controllable resource" in the column "Level" in chapter 7 "Products for the order placement of a change at a location" of the code list of configurations. |
| [52] | If code TE / AL is present in DE3155 in the same COM. |
| [53] | If the LF of the market location is not assigned to the named location in the requested implementation period. |
| [59] | If SG27 LIN++ZH5 (Required configuration control box) is present. |
| [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. |
| [492] | if MP-ID in NAD+MR from division electricity |
| [493] | if MP-ID in NAD+MR from division gas |
| [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: Indication of a technical contact person for the device takeover |
| [501] | Note: Indication of a contact person for invoice processing |
| [502] | Note: Use of the ID of the market location |
| [503] | Note: Use of the ID of the metering location |
| [504] | Note: Use of the ID of the tranche |
| [507] | Note: Transaction number from SG4 IDE+24 DE7402 of the UTILMD with BGM+E01 with which the registration of the MSB switch was carried out. |
| [508] | Note: Value from BGM+Z73 DE1004 of the IFTSTA with which the response to the order placement for the configuration was transmitted |
| [509] | Note: Transaction number from CNI DE1490 of the IFTSTA with BGM+Z73 with which the response to the order placement of the configuration was transmitted |
| [510] | Note: Use of the ID of the grid location |
| [511] | Note: Use of the ID of the controllable resource |
| [512] | Note: For receiving the values according to type 2 from the SMGW. |
| [514] | Note: Only one piece of information may be transmitted in DE3148 |
| [515] | Note: An URI IPv4 must be specified for the provision of the values. |
| [516] | Note: An URI IPv6 must be specified for the provision of the values. |
| [517] | Note: Use of the ID of the technical resource |
| [518] | Note: for stating the contact details of the supplier's customer in order to simplify the change to the technology. |
| [520] | Note: Statement of the start point in time of the desired implementation date from the requesting party's point of view. |
| [521] | Note: Indication of the end point in time of the desired implementation date from the requester's perspective. |
| [903] | Format: Possible value: 1 |
| [906] | Format: max. 3 decimal places |
| [911] | Format: Possible values: 1 to n, starting at 1 for each message or segment group and ascending consecutively |
| [922] | Format: TR-ID |
| [931] | Format: ZZZ = +00 |
| [932] | Format: HHMM = 2200 |
| [933] | Format: HHMM = 2300 |
| [934] | Format: HHMM = 0400 |
| [935] | Format: HHMM = 0500 |
| [939] | Format: the character string must contain the characters @ and . |
| [940] | Format: the character string must begin with the character + and may only be followed by digits |
| [950] | Format: market location ID |
| [951] | Format: Metering point identifier |
| [960] | Format: Grid location ID |
| [961] | Format: SR-ID |
| [962] | Format: max. 6 digits before the decimal point |
| [967] | Format: Certificate body in accordance with X509.1, BSI TR-03109-4 |
| [2005] | The SG27 must be specified exactly once per message. |
| [2060] | The SG27 LIN+Z64 (required product switching time definitions) must be specified at most once per message. |
| [2061] | The SG27 LIN++Z65 (required product load curve definitions) must be specified at most once per message. |
| [2062] | The SG27 LIN++Z66 (required product ad-hoc control channel) must be specified at most once per message. |
| [2063] | The SG27 LIN++Z67 (required metering product for values according to type 2 from the backend) must be specified at most once per message. |
| [2064] | The SG27 LIN++Z68 (required product configuration permission for values according to type 2 from SMGW) must be specified at most once per message. |
| [2065] | This SG28 must be repeated as many times as a product is stated for the different metering product item codes for the product stated in PIA+5 DE7140 (required product configuration permission for values of type 2 from SMGW) within the same SG27 LIN, which is marked in the code list of configurations in chapter 4.4 "Metering products with configuration permission for values of type 2 from SMGW" in the column "trigger" with the value "When falling below / exceeding the threshold value". |
| [2066] | This SG28 must be repeated as many times as a product is stated for the different metering product item codes for the product stated in PIA+5 DE7140 (required product configuration permission for values of type 2 from SMGW) within the same SG27 LIN, which is marked in the code list of configurations in chapter 4.6.2 "Values of type 2 from SMGW" in the column "trigger" with the value "When falling below / exceeding the threshold value". |
| [2067] | The SG12 RFF+Z37 reference to ID of the technical resource must be repeated until all IDs of the technical resources are stated that are to be assigned with this transaction to the controllable resource in LOC+172 DE3225 (reporting point). |
| [2068] | This SG27 must be repeated as often as required so that all products for the location are stated that are requested from the point of view of the requesting party within the desired implementation date (time interval from DTM+469 (start date or point in time) and DTM+472 (end date or point in time)) and whose combination is possible according to the code list of configurations, chapter 7 "Products for ordering a change at a location". |
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 |
|---|---|
| [UB1] | ([931] ∧ [932] [490]) ⊻ ([931] ∧ [933] [491]) |
| [UB3] | ([931] ∧ [932] [492] ∧ [490]) ⊻ ([931] ∧ [933] [492] ∧ [491]) ⊻ ([931] ∧ [934] [493] ∧ [490]) ⊻ ([931] ∧ [935] [493] ∧ [491]) |
Condition packages
Condition packages bundle prerequisites.
| Package | Prerequisites | Conditions |
|---|---|---|
| [1P] | -- | Note: This is the standard package if no condition applies, e.g. in the COM segment. |
Notes on this page
This page carries the free text of every condition that the application handbook of message type REQOTE 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.
2 conditions do 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 5 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.
[UB1], [UB3]
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.