Conditions CONTRL
EDIFACT message type CONTRL · format version 202604 · 7 conditions · 0 packages · 0 UB conditions · from 2 handbook file(s)
Conditions
| Marker | Condition |
|---|---|
| [1] | If a specification is possible. |
| [2] | If a syntax error is present in UNH. |
| [3] | If a syntax error is present in UNT. |
| [5] | If an error is present at segment (group) level. |
| [6] | If an error is present at data element, component data element or data group level. |
| [8] | If SG1 UCM DE0013 is present. |
| [9] | If SG1 UCM DE0013 is not present. |
Notes on this page
This page carries the free text of every condition that the application handbook of message type CONTRL 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.