EDI Translators are expensive, but worth it if you have more than just a very few trading partners. I would suggest that approach before writing your own.

Secondly, if I was going to expend the effort to write my own translator, I would be run, not walk, away from any module that generated warnings saying something in it is 'experimental'. Is it something that is going to change functionality or just go away in a future release? Is all my hard work going to be wasted?

Is your test data well formed? I work with X12, not EDIFACT, so I can't tell just by looking. That might be the source of the error. If not, I think you need to open up the module and go to the line indicated and see what it was trying to do.

In reply to Re: Edifact anyone? by GotToBTru
in thread Edifact anyone? by Skeeve

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


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.