Don't confuse between the two.
better you go through this--
<b>What are Idoc's?</b>
IDOC’s are by no means anything special. They are physically ASCII data streams like simple flat files with lines of text, where the lines are structured into data fields. The typical structured file has records, where each record starts with a leading string, which identifies the record type, e.g. if it is a header record or an item record. The only precondition for an IDoc is, that the meaning of every field must be recognizable without interpreting the contents, so that the data can be mapped into a database structure without semantical interpretation of the content.
IDOC’s is the acronym for Interchange Document, meaning a set of (electronic) information which builds a logical entity. Because an IDoc is meant to be exchanged (or interchanged) between two independently existing partners, an IDoc must adhere to a mutually accepted format or language. An IDoc is e.g. all the data of a single customer in your customer master data file. If you send data for multiple customer at the same time, we shall regard this as sending multiple IDOC’s.
Idoc data is usually exchanged between systems and partners who are completely independent. Therefore the data should be tfransmitted in a format, that can easily be corrected by the humans who operate the computers. It is therefore mandatory to post the data in a human readable form. Nowadays, this means that data is coded in ASCII fomat, including number, which are sent as string of figures 0 to 9. Such data can easily be read with any text editor on any computer, be it a PC, Macintosh a UNIX System or any internet browser.
Keep this in mind: IDOC’s are basically a small number of records in ASCII format, building altogether a logical entity. In order to sharpen your imagination, you should always see an IDoc as a plain ASCII text file. E.g. an IDoc may contain the data of a purchase or sales order, resp. or it may contain the data of a material master or of a customer master. See the illustration MATMAS for an example of a material master IDoc or illustration ORDERS for an example of a purchase order IDoc.
<b>What is SAP XI?</b>
SAP Exchange Infrastructure is SAP’s platform for process integration based on the exchange of XML messages.
1. It provides a technical infrastructure for XML based message exchange in order to connect SAP components with each other as well as with non-SAP components.
2. It delivers business process integration knowledge to the customer in the form of SAP pre-defined business scenarios.
3. It provides an integrated tool set for building new business scenarios by defining and maintaining all integration relevant information. (“Shared collaboration knowledge”).
Before we take a closer look at how the Exchange Infrastructure will enter into the IT landscape of every SAP customer, let’s take a closer look at the capabilities as well as the strategic direction of XI. This particular module of Net Weaver is one of the most powerful and is undeniably the most critical. Its purpose is really three-fold:
Connect:
XI has the ability to connect all applications regardless of whether it is an application
From a 3rd party or from SAP. The solution has pre-built connectivity to all SAP modules
Such as SAP CRM and utilizes the Adapter Framework to integrate 3rd Party solutions
such as Siebel, People Soft, Legacy systems, or AS/400s and Mainframes.
Coordinate:
XI has the ability to define a path/workflow for each business transaction that is
Integrated. The system actively routes each message to ensure that it is properly
Delivered from the source to the target destination. Active monitoring allows
Administrators to manage document exchange on an exception basis.
Communicate:
XI has the ability to translate files into any format whether an internal file format or any
Business to Business integration standard including but not limited to an XML format, an
EDI format, a marketplace, or a Web Service. Finally, there are multiple communication
Protocols included which allow the routing of a file over protocols such as s/FTP, http/s,
SOAP, ebMS, Value-Added Networks, or EDI INT (AS1, AS2).
Understanding The SAP Exchange Infrastructure_
Now, you might be saying to yourself, we already have solutions that provide all of this
Functionality. True, most organizations have invested previously in an integration strategy, but what we see in over 90% of organizations is that they have multiple translators and communication brokers, which they are supporting on a daily basis. This
is both a resource drain as well as a monetary drain. For example, it is not uncommon to see the following even in smaller organizations:
• Multiple Point to Point connectivity: For example, R/3 connected to a 3rd party
Warehouse Management Solution via an internally developed adapter or with the SAP
Business Connector
• A 3rd party EAI Integration Broker to connect legacy mainframe systems to SAP and
WMS
• A 3rd party EDI translator to communicate messages
• A 3rd party XML broker to communicate XML messages to marketplaces and non-EDI
Trading partners
• A communication server that focuses on sending messages via FTP, Value-Added
Networks and Internet protocols such as AS2 solution of choice for SAP end users
Interface-
regards,
srinivas
Bluesky
