The BusinessConnect EDI logging feature logs file with linefeeds (0x0A) stripped when using multiple characters for a segment terminator.
Article ID: KB0088817
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect | - |
| Not Applicable | - |
Description
Resolution:
Description:
============
When processing an incoming EDI-X12 transaction with multiple characters (such as CR-LF 0x0D0A) as a segment delimiter, BusinessConnect (BC) only logs the file with the CR in the file. The LF character is stripped.
Environment:
==========
BusinessConnect EDI Protocol 5.3 and 5.4.
Symptoms:
=========
The file logged by BusinessConnect EDI in the log directory does not identically match the file submitted to the BC system.
Cause:
=====
BC expects EDI-X12 files to only have one character segment delimiters and will strip out any other characters associated with the segment terminator.
Resolution:
=========
There is no workaround for this issue.
Description:
============
When processing an incoming EDI-X12 transaction with multiple characters (such as CR-LF 0x0D0A) as a segment delimiter, BusinessConnect (BC) only logs the file with the CR in the file. The LF character is stripped.
Environment:
==========
BusinessConnect EDI Protocol 5.3 and 5.4.
Symptoms:
=========
The file logged by BusinessConnect EDI in the log directory does not identically match the file submitted to the BC system.
Cause:
=====
BC expects EDI-X12 files to only have one character segment delimiters and will strip out any other characters associated with the segment terminator.
Resolution:
=========
There is no workaround for this issue.
Issue/Introduction
The BusinessConnect EDI logging feature logs file with linefeeds (0x0A) stripped when using multiple characters for a segment terminator.
Feedback
Yes
No
Powered by
