Issue Details (XML | Word | Printable)

Key: MULE-758
Type: New Feature New Feature
Status: Closed Closed
Resolution: Won't Fix or Usage Issue
Priority: Major Major
Assignee: Ross Mason
Reporter: Holger Hoffstaette
Votes: 0
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
Mule

EDI/EDIFACT functionality

Created: 11/Apr/06 06:13 AM   Updated: 30/Nov/08 04:31 AM
Component/s: Modules: (other)
Affects Version/s: 1.3-rc1
Fix Version/s: None

Time Tracking:
Not Specified

Labels:


 Description  « Hide
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.

 All   Comments   Work Log   Change History   Transitions   FishEye      Sort Order: Ascending order - Click to sort in descending order
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):

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).

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.

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