Supported EDIFACT syntax versions

Post author
Robin Reiß

Hello,

After some further tests with the Free Trial, i'm wondering which EDIFACT syntax versions EdiFabric supports?

Best regards,

Robin Reiß

Comments

4 comments

  • Comment author
    Admin

    Hello Robin,

    EdiFabric Framework supports all EDIFACT versions, as well as all X12 versions. To be precise, it supports the standards per se, where each particular transaction is represented as an EDI template, hence any transaction can be represented as EDI template.

    We offer off-the-shelf EDI templates as part of our plans for the following EDIFACT transactions (each check mark is an EDI template):

    EDIFACT Templates - click on each version range for details.

    In case we haven't got a version\transaction ready, we can prepare it for you at no extra cost.

    Best,

    Don

    1
  • Comment author
    Robin Reiß
    • Edited

    Hello Don,

    Thanks for your quick reply.
    When I spoke of syntax versions, I meant the syntactic structure of an interchange defined by some ISO standards, e.g. Syntax Version 4 (http://www.gefeg.com/jswg/v4/data/v4_docs.htm), Syntax Version 3 (http://www.gefeg.com/jswg/v3/data/v1-9735. pdf) and so on.

    For the two syntax versions mentioned above, there are some differences regarding the interchange structure and certain delimiters.

    Best regards,
    Robin Reiß

    0
  • Comment author
    Admin

    Hello Robin,

    The framework can support both syntax versions or any syntax version for that matter. Things such as repeating data elements, character sets, control segment structure are either built in or can be extended by inheritance.

    It supports stand-alone or composite data element repetitions, even without service repetition character based on the syntax id (currently only for syntax id == IATA).

    Validation against a syntax set is configurable, supports UNOA and UNOB, details here. You can implement custom syntax sets by inheriting from SyntaxSet.

    Encoding can be applied to both the reader or writer.

    Relationships and inter-segment dependencies can be applied using the set of conditional attributes.

    All control segments, UNB, UNH, etc. are extendable and the structure or validation attributes can be amended according to whatever syntax you need it.

    The EDI template is like a canvas that can be configured with both the structure and the validation attributes.

    Best,

    Don

    1
  • Comment author
    Robin Reiß

    Hello Don,

    Thanks for your detailed explanation. It helped me a lot.

    Best regards,
    Robin Reiß

    0

Please sign in to leave a comment.