 - IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.
 |
Getting started with IDocs |
|
Learn more about SAP interface technologies |
| SAP CTO expects today's SAP applications to be running in 2020: Vishal Sikka, CTO of SAP, expects many of the SAP software applications running today to still be running in the year 2020 -- if the software is developed properly. |
| Converting IDocs to XML format: Learn how to convert IDocs into XML format for use in XI or any other application. |
| SAP applications demo: BP's key mapping: In this screencast of a composite application shown at TechEd, BP demonstrates a key mapping services using NetWeaver. |
| A primer on XML: This chapter examines the origins of XML and dives into issues like document vs. data-centric XML, instances, namespaces, document type definitions, XML schemas and processing. |
| Overcoming Basis challenges inside and outside the box: Learn how to overcome common administrator challenges and to be more productive working with SAP Basis in this new guide from Basis expert Giovanni Davila. |
| IT checklist: JCo installation exception madness: Misleading or even indecipherable exception messages seem to be the rule of the day when it comes to debugging JCo connector installation exceptions. This checklist by veteran Java expert Austin ... |
| Crash course: IDocs: IDocs may sound fairly straight-forward in theory. In reality, there are gotchas to avoid and tricks for speeding things up. This selection of tips and advice will get you started. |
| LAST UPDATED: |
24 Sep 2008
|
 |
Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com
|
|
More resources from around the web:
|
|
Show me everything on 
