# Conditions APERAK
EDIFACT message type **APERAK** · format version **202604** · 23 conditions · 1 packages · 0 UB conditions · from 2 handbook file(s)
## Conditions
| Marker | Condition |
|---|---|
| **[1]** | If SG3 CTA+IC is present. |
| **[2]** | If erroneous content is present. |
| **[3]** | If required for a further error specification. |
| **[4]** | If in this SG4, RFF+TN is not present. |
| **[5]** | If SG4 ERC+Z29 present. |
| **[6]** | If an error is present within the transaction level of IFTSTA, INSRPT, UTILMD or UTILTS. |
| **[7]** | If SG4 ERC+Z21 present. |
| **[8]** | If SG4 ERC+Z16 is present. |
| **[9]** | If SG4 ERC+Z35 present. |
| **[10]** | If SG4 ERC+Z38 present. |
| **[11]** | If SG4 ERC+Z39 present. |
| **[12]** | If SG4 ERC+Z41 present. |
| **[13]** | If SG4 ERC+Z40 present. |
| **[14]** | If code EM is present in DE3155 in the same COM |
| **[15]** | If code TE / FX / AJ / AL is present in DE3155 in the same COM |
| **[16]** | If the referenced message type is IFTSTA, INSRPT, UTILMD or UTILTS. |
| **[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: For follow-up processes. |
| **[501]** | Note: For initial processes. |
| **[502]** | 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. |
This page carries the free text of every condition that the application handbook of message type **APERAK** 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.
:::caution{title="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.