Feedback

Feedback

Did this article resolve your question/issue?

   

Article

Trouble shooting tips for issues when converting a SEF file to XML while using Connect for XML Converters

Printable View

Information

 
TitleTrouble shooting tips for issues when converting a SEF file to XML while using Connect for XML Converters
URL NameTrouble-shooting-tips-for-issues-when-converting-a-SEF-file-to-XML-while-using-Connect-for-XML-Converters
Article Number000110401
EnvironmentProduct: Connect for XML Converters
Version: All supported versions
OS: Java
Database: Not applicable
Application: All supported applications
Question/Problem Description
Trouble shooting tips for issues when converting a SEF file to XML while using Connect for XML Converters
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
Here are a few issues seen when problems occur converting SEF files to XML.

1) The SEF file includes some extra spaces in the middle of some of the segment names. These must be fixed in order for the SEF file to be valid. 
2) Length validation is enforced with len=yes, but at least one line has a text item defined to hold x amount of characters, but contains a larger amount of x characters. This requires setting len=no. 
3) The SEF file has x repetitions of GROUPx, but the definition for the GROUP has a lower maximum amount of repetitions. 
4) The SEF file contains the "$" character, which is not valid in the UNOA character encoding which is the default for IATA. Using the chr=UNOC option resolved this.
 
Workaround
Notes
Last Modified Date2/20/2019 3:55 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.


Copyright © 2022 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.

Progress, Telerik, Ipswitch, Chef, Kemp, Flowmon and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.

Terms of Use Privacy Center Security Center Trademarks License Agreements Code of Conduct Careers Offices
Do Not Sell My Personal Information