Conditions ORDCHG
EDIFACT message type ORDCHG · format version 202604 · 12 conditions · 1 packages · 0 UB conditions · from 3 handbook file(s)
Conditions
| Marker | Condition |
|---|---|
| [2] | If BGM+Z51 (disconnection) present |
| [3] | If BGM+Z52 (reconnection) present |
| [4] | if the code EM is present in DE3155 in the same COM |
| [5] | if the code TE / FX / AJ / AL is present in DE3155 in the same COM |
| [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: Document number from BGM DE1004 of the ORDERS |
| [501] | Note: Value from BGM+Z33 DE1004 of the IFTSTA with which the information on the reconnection order was transmitted |
| [502] | Note: Transaction number from CNI DE1490 of the IFTSTA with BGM+Z33 with which the information on the reconnection order was transmitted |
| [503] | Note: Only one piece of information may be transmitted in DE3148 |
| [931] | Format: ZZZ = +00 |
| [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 |
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 ORDCHG 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 is referenced without the source carrying its text
These markers are in at least one handbook row of this message type, but in none of the three lists of the source. The reference therefore points nowhere, and that is stated here instead of silently omitting the marker — an omitted gap looks like no gap at all.
[1]
Measured on 05.09.2026, after the position-faithful re-export of the source. Across both versions and all message types there are 22 markers, all in version 202604.
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.