edifact / error
EL7009
edifact.trailing-data
Applies to: edifact
What it catches and why it matters
Segments appear outside any interchange; data after UNZ is not part of a valid EDIFACT file.
Failing example
These synthetic fragments illustrate the defect; they are not complete interchange files. Backslash escapes name bytes such as \r (CR) and \n (LF).
UNZ+1+EXAMPLE'FTX+AAI+++EXTRA'
How to fix it
Remove an accidental transport suffix or place the segment inside its intended message. Keep all EDIFACT segments inside an interchange.
False positives and limits
Transport framing outside the interchange may be deliberate. Strip the wrapper and lint only the EDI payload.
Acknowledgments and suppression
No direct acknowledgment code is mapped for this rule. CONTRL references use syntax-error element 0085, not action element 0083. UCI, UCF and UCM report interchange, group and message service-segment errors respectively. A missing or unreadable header can prevent a valid CONTRL response. Truncation, orphaned envelopes and data outside an interchange have no single mapping here. Sources: https://service.gefeg.com/jwg1/Archive/v3/mt/m01.htm https://service.gefeg.com/jwg1/Archive/cl/v3/21a/cl16.htm Suppress the rule with --disable EL7009, or list it under "disable" in .edilint.yml. To accept the occurrences a file already has without suppressing the rule, record them with --write-baseline and run with --baseline. Reference: https://crb2nu.github.io/edilint/rules/EL7009.html