Troubleshooting
Problem
A characters used as a composite delimiter definition is no longer allowed to occur in other areas of the data file
Symptom
If : is used as a composite delimiter definition and if : exist in other areas of the code, then Trading Manager 8.2.1.11 will reject the data file. This did not occur in TM 8.2.1.5.
Cause
A fix introduced in post WebSphere Transformation Extender 8.4.x resolved an issue where the exclude character property was added to define characters used in syntax that are not allowed in the data stream. The default is not to exclude characters unless defined, so the X12 type trees (8.4 and above) are set to exclude Composite and Repetition delimiters when that property is set.
Environment
Versions of Trading Manager later than 8.2.1.5 and WebSphere Transformation Extender 8.4.x
Diagnosing The Problem
Confirm that reject character in data file is also being used as a Composite and/or Repetition delimiters
Resolving The Problem
Remove the composite delimiter character in the data stream, or manually add the defined composite delimiter character to the exclude character property for the segment that contains that character.
The latter suggestion is not considered standard X12 data, so this is not a supported method.
Was this topic helpful?
Document Information
Modified date:
28 September 2018
UID
swg22016843