Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
Esteemed Monks,
I've been looking for information on parsing EDI (Electronic Data Interchange) messages with Perl (in my case, edifact/D93A/INVOIC).

I found, and tried, XML::Edifact module from Michael Koehne. But it doesn't correctly parse my message and I don't need to output the results in XML.

All I need (and I know this is a lot of, and complex, work) is to check if the message is valid, parse it, create a data structure and show some informations to the user.

Googling and searching the monastery didn't help me much on this. So, here I am asking for help from some monk with experience in this field on how and where to start.

Note: I'm aware that this is a task for gurus - which I'm not - and there are lots of commercial and proprietary solutions out there, mainly using Java. But my main interest in this field is to learn, at least the basics, on EDI messages and how Perl can interact with them.

Thank you for your time,

In reply to Parsing EDI messages by Miguel

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.