Lowercased tag — 997 functional acknowledgement
A functional acknowledgement whose ISA segment tag arrived in lowercase ('isa'). x12-tidy uppercases it; nothing else is wrong and the result is conformant.
The interchange as submitted
Corrected interchange
Envelope
| Sender | ZZ / GATEWAYEDIFrom ISA05 (qualifier) and ISA06 (ID). |
|---|---|
| Receiver | ZZ / PARTNERXFrom ISA07 (qualifier) and ISA08 (ID). |
| Usage indicator | PISA15 — P = production, T = test, I = information. |
| Interchange version | 00401ISA12 — the interchange control version number. |
| Date / time | 240102 0801ISA09 and ISA10 — when the interchange was prepared. |
| Functional groups | 1GS segments counted while walking the payload; IEA01 is checked against this. |
| Transaction sets | 1ST segments counted; each group's GE01 is checked against its own count. |
| Segments | 9Total segments in the cleansed payload; each SE01 is checked against its set's count. |
Repair passes
The Byte column is the offset into the submitted text where the flagged structure begins; ISA-line findings share a number, and a dash means the finding isn't tied to one spot.
Pass 1 1 error changed the interchange
246 bytes in → 246 bytes out.
| Severity | Code | Byte | Finding |
|---|---|---|---|
| ERROR | isa.identifier-lowercase |
0 |
ISA segment identifier is not uppercase
the ISA segment identifier is not uppercase ('isa' or mixed case); X12 segment identifiers are uppercase. Parsed case-insensitively.
The segment identifier was found as 'isa' or mixed case (e.g. 'Isa'). X12 segment identifiers are uppercase. x12-tidy matched it case-insensitively and continued -- a file with a non-uppercase ISA identifier almost certainly has every other segment identifier the same way, which downstream steps must also tolerate. |
Pass 2 clean no change
246 bytes in → 246 bytes out.
No findings on this pass.