[#MULE-758] EDI/EDIFACT functionality - JIRA

Details

Type: New Feature
Status: Closed
Priority: Major
Resolution: Won't Fix or Usage Issue
Affects Version/s: 1.3-rc1
Fix Version/s: None
Component/s: Modules: (other)
Labels:
None

Similar Issues:
None

Description

EDI/EDIFACT (Electronic Data Interchange, see http://en.wikipedia.org/wiki/Electronic_Data_Interchange) functionality is an interesting feature for any ESB in B2B settings. This issue is meant as initial starting point to collect ideas and contributions.

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

kenneth westelinck added a comment - 12/Apr/06 02:07 AM

Since I have 4 years of experience in EDI (Edifact and X12) I think I might be able to help. In projects, I have already succesfully used (in java based projects):

OBOE (http://www.americancoders.com/OpenBusinessObjects/): This is an API and XML convertor for EDI (both X12 and Edifact). As far as I know, this is the beste implementation out there, but it's not free.
XML-Edifact (http://www.xml-edifact.org/): This is a perl library to convert Edifact to XML and vice versa (no support for X12)

The problem with EDI is:

Sure you can write something that can parse/convert this type of files
You will need some kind of partnermanagement (who is sending orders to who)
You will have to be able to validate incoming and outgoing EDI (supported by tools mentioned above)
You will need support for batching/de-batching. One EDI document might contain multiple orders or invoic messages (or a combination).
You will need support for functional acknowledgements. This is not popular in the Edifact world, but is definetely used in X12 (997 documents).

Show

kenneth westelinck added a comment - 12/Apr/06 02:07 AM Since I have 4 years of experience in EDI (Edifact and X12) I think I might be able to help. In projects, I have already succesfully used (in java based projects):

OBOE (http://www.americancoders.com/OpenBusinessObjects/): This is an API and XML convertor for EDI (both X12 and Edifact). As far as I know, this is the beste implementation out there, but it's not free.
XML-Edifact (http://www.xml-edifact.org/): This is a perl library to convert Edifact to XML and vice versa (no support for X12)

The problem with EDI is:

Sure you can write something that can parse/convert this type of files
You will need some kind of partnermanagement (who is sending orders to who)
You will have to be able to validate incoming and outgoing EDI (supported by tools mentioned above)
You will need support for batching/de-batching. One EDI document might contain multiple orders or invoic messages (or a combination).
You will need support for functional acknowledgements. This is not popular in the Edifact world, but is definetely used in X12 (997 documents).

Hide

Permalink

henk-jan ebbers added a comment - 29/Aug/07 06:01 AM

You might want to look at Bots (http://bots.sourceforge.net).
I handles EDIFACT, XML, CSV, flat file; X12 is being worked on.
It is written in python.

Show

henk-jan ebbers added a comment - 29/Aug/07 06:01 AM You might want to look at Bots (http://bots.sourceforge.net). I handles EDIFACT, XML, CSV, flat file; X12 is being worked on. It is written in python.

Hide

Permalink

Ross Mason added a comment - 30/Nov/08 04:31 AM

This can be tracked on MuleForge: http://www.muleforge.org/projects.php?projectname=EDI%20Reader

Show

Ross Mason added a comment - 30/Nov/08 04:31 AM This can be tracked on MuleForge: http://www.muleforge.org/projects.php?projectname=EDI%20Reader

EDI/EDIFACT functionality

Details

Description

Activity

People

Dates

Agile