Conditions INSRPT
EDIFACT message type INSRPT · format version 202604 · 31 conditions · 4 packages · 0 UB conditions · from 8 handbook file(s)
Conditions
| Marker | Condition |
|---|---|
| [1] | If the message sender has been informed by the customer. |
| [2] | If SG7 STS+Z06+Z10+ZC1 is present. |
| [3] | If present. |
| [4] | If MP-ID in SG2 NAD+MR in the role NB |
| [5] | If MP-ID in SG2 NAD+MR in the role LF |
| [6] | If no fault could be determined. |
| [7] | If no further SG7 with the same reporting point and DTM+9 is present |
| [8] | If STS+Z06+Z10 is present in this SG7 |
| [9] | If a fault was identified that the MSB could not rectify independently and through no fault of its own. |
| [10] | If in this STS DE4405 = Z09 |
| [11] | If in this STS DE4405 = Z10 |
| [12] | If a fault was identified that was rectified by the MSB. |
| [13] | If DE2379 = 303 |
| [14] | Only MP-ID from the electricity division |
| [494] | The date stated here must be the point in time at which the document was created, or a point in time before that |
| [495] | The point in time must be ≤ the value in DE2380 of DTM+137 |
| [500] | Note: Transaction number (DOC DE1004) from process step 4b „Confirmation of the fault report“ (gas) or process step 2 „Response“ (electricity). |
| [506] | Note: To be used if the fault cannot be rectified by the MSB independently and through no fault of its own. |
| [507] | Note: SG7 FTX+AAO must state the overarching cause due to which the MSB is unable to rectify the fault. |
| [508] | Note: Transaction number from DOC DE1004. |
| [509] | Note: Use of the ID of the metering location |
| [510] | Note: Use of the ID of the market location |
| [511] | Note: The numbering starts at 1 in every document |
| [512] | Note: If a fault was detected and rectified by the MSB, the segment group must be stated twice with the same reporting point |
| [513] | Note: If no fault was detected, the segment group must be stated exactly once |
| [514] | Note: If a fault was detected that could not be rectified by the MSB, the segment group must be stated exactly once |
| [515] | Note: "≤ the value in DE2380 of DTM+137" means that the day stated there must be ≥ the day stated in this DTM if code 102 is entered in DE2379. |
| [908] | Format: possible values: 1 to n |
| [931] | Format: ZZZ = +00 |
| [950] | Format: market location ID |
| [951] | Format: Metering point identifier |
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. |
| [2P] | [6] | If no fault could be determined . |
| [3P] | [12] | If a fault was identified that was rectified by the MSB . |
| [4P] | [9] | If a fault was identified that the MSB could not rectify independently and through no fault of its own . |
Notes on this page
This page carries the free text of every condition that the application handbook of message type INSRPT 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.
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.