APERAK
Application Error and Acknowledgement
D96AWhat is the APERAK message used for?
- The APERAK page serves as an instant reference for systems analysts, developers, and EDI operations teams.
- It brings together the message business role, associated segment breakdown, and a live example in one place.
- Highly valuable during trading partner onboarding, mapping verification, incident triage, and technical training.
The APERAK message is an application-level acknowledgement: the receiving system confirms it has processed the message and reports any business logic errors. It operates above the syntactic level of CONTRL.
Usage scenarios:
Automotive, logistics — where business processing confirmation is required.
Automotive, logistics — where business processing confirmation is required.
| Segment | Name | Mandatory | Max Repeat |
|---|---|---|---|
| UNB | Interchange Header | Mandatory | 1 |
| UNH | Message Header | Mandatory | 1 |
| UNT | Message Trailer | Mandatory | 1 |
| UNZ | Interchange Trailer | Mandatory | 1 |
| BGM | Beginning of Message | Mandatory | 1 |
| DTM | Date/Time/Period | Optional | 1 |
| NAD | Name and Address | Optional | 10 |
| RFF | Reference | Optional | 1 |
| ERC | Application Error Information | Optional | 1 |
| FTX | Free Text | Optional | 1 |
APERAK – Sample message (D96A)
Download (.edi)
Test in validator
UNA:+.? ' UNB+UNOC:3+RECEIVER:14+SENDER:14+260310:0805+00100' UNH+1+APERAK:D:96A:UN' BGM+313' DTM+137:20260310:102' RFF+ACE:1' UNT+5+1' UNZ+1+00100'
The sample above can be validated directly in the EDIFACT Validator – Online Syntax Checker.