如何使EDI表格更具可读性？
我有一个 EDI 表格，我想让它更具可读性，特别是税收类型、名称、年份等的命名约定。这样我想交叉检查我的申请。
当我打开 EDI 表单时，它会在 XL 工作表中打开，并且我无法进行搜索等。
如何将 EDI 表单转换为可理解的格式？
I have an EDI form, I want make it more readable especially the naming conventions for tax types, name, year etc. This way I wanna cross check my application.
When I open the EDI form it opens in XL sheet and I am unable to do search etc.
How to convert an EDI form into understandable format?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
http://liaison.com/products/integrate/edi-notepad
这是最好的我发现该工具可以以良好的格式阅读几乎任何类型的 EDI 文档。我不经常使用它，但如果我有一份文档需要打印并发送给不了解 EDI 的人，它的效果会非常好。
http://liaison.com/products/integrate/edi-notepad
This is the best tool I've found for reading just about any type of EDI document in a nice format. I don't use it a ton, but if I have a document I need to print and send to someone who doesn't know EDI, it works fantastically.
简而言之，您将无法将 EDI 消息转换为易于阅读的格式。 EDI 是在带宽非常有限且昂贵的时代设计为机器对机器的格式。数据元素的存在或省略取决于它们在 EDI 消息标准中的隐含位置以及您的贸易伙伴可能对该消息执行的任何非标准变体。
这使得 EDI 难以阅读。即使您根据正确的消息标准目录/方言/版本对其进行验证，您的贸易伙伴仍然可能会执行某些与您期望的不太相符的元素。
为了快速查看，我只需使用一个好的文本编辑器并将 CR LF 添加到段终止符。为交换中的消息添加空白行。一段时间后，您将熟悉段命名约定和计数。
如果您要发送出站消息，验证要求最终将由您的贸易伙伴承担，反之亦然。这可能会使测试变得困难，因为您不想向新的 EDI 伙伴发送大量数据。
首先检查语法、控制计数等是否正确，然后检查是否与消息目录/版本等匹配。然后检查贸易伙伴例外/字段的非标准使用等是否正常。
The short answer is that you will not be able to make EDI messages into an easily-readable format. EDI was designed as a machine-to-machine format in an age when bandwidth was very limited and expensive. The presence or omission of data elements is based on their implicit position in the EDI message standard and any non-standard variations that your Trading Partner may be doing with that message.
This conspires to make EDI hard to read. Even if you validate it against the right message standard Directory/Dialect/Version there are still likely to be elements that your trading partner are doing that don't quite fit what you expect.
For a quick look I would simply use a good text editor and add CR LF's to the segment terminators. Add a blank row for messages within an interchange. After a while you will become familiar with the segment naming conventions and counts.
If you are sending outbound messages the validation requirement will ultimately be at your trading partner end and visa versa. This can make testing difficult as you don't want to send a load of crud to your new EDI buddy.
Check the syntax, control counts etc are all correct first, then does it match the Message Directory / Version etc. Then check that the Trading Partner exceptions / non-standard use of fields etc are okay.