hi ,
read this blog on
I am sure it will solve the problem
SAP XI and EDI: Better Learning through Architecture
http://blogs.ittoolbox.com/sap/ehadzipetros/archives/sap-xi-and-edi-better-learning-through-architec...
here's an extract :
A good EDI system must support the full range of communications protocols including FTP, SFTP, HTTP, HTTP/S, file system transfers and so on. It also needs to provide the infrastructure to support secure communications outside the firewall including dedicated AS2 servers and Perimeter Servers that sit within the DMZ and control the data traffic between the outside world and your company's internal systems.
That's a lot of stuff and I'm just scratching the surface here. XI provides much of this and with enough time, money and development talent (Java, ABAP and BPML) can provide it all. But it would be a very expensive effort.
XI was designed as an applications integration tool that supports XML SOAP messaging and provides a framework for a Services Oriented Architecture (SOA) with Java and ABAP Proxies exposing selected functionality from all of its connected systems to each other. As a doorway into, out of and between all SAP systems, XI is wonderful. As the glue between your SAP and other internal systems in a Master Data Management architecture, XI is sublime.
XI was not, however, designed as an EDI system, which is still largely about batch processing of large volumes of standard electronic documents, although XI does support third party EDI plug-ins. I've worked with one of the third-party EDI plug-ins and it did not provide us the functionality that we needed in all the categories described above.
Here are two small examples to illustrate my point. While the plug-in advertised support for all EDI Standards, out of the box it only provided four example transactions of X12, EDIFACT and TRADACOMS in one version plus acknowledgements. You had to pay extra to get additional standards and versions from their library, which was exported from EDIFECS SpecBuilder in a proprietary format.
There was no support for Enveloping and De-Enveloping out of the box, unlike dedicated EDI systems such as Gentran Integration Suite (GIS). This critical EDI functionality could only be provided by bringing in the vendor's consultants who would then build custom Enveloping and De-Enveloping BP's using the XI BP modeler.
This is all out-of-the-box functionality in the leading EDI systems on the market, which also come with adapters for sending IDocs into and out of SAP, as well as for many other systems.
regards ,
TJ
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.