IDoc , short for Intermediate Document, is a SAP document format for business transaction data transfers. Non-SAP-systems can use IDocs as the standard (computing) interface for data transfer. IDoc is similar to XML in purpose, but differs in syntax. Both serve the purpose of data exchange and automation in computer systems, but IDoc-Technology takes a different approach.
While XML allows having some metadata about the document itself, IDoc is obliged to have information in its header like its creator, creation time etc. While XML has tree structures like tags that contain data and meta-data, IDocs uses tables with data and meta-data. IDocs also has sessions that describe all processes that the document passes or will skip, allowing someone to debug and track document status.
Different IDoc types are available to handle different types of messages. For example, IDOC ORDERS01 format can be used for purchase order and order confirmation.
IDoc Technology offers many tools for automation, monitoring and error handling. For example, if IDocs is customized like that on a particular server, then the SAP R/3 system user makes a purchase order; this is automatically sent via IDoc and a sales order is immediately made on the vendor's system.
When this order can not be made due to an application error (eg: The price per piece is lower than allowed for this material), then the administrator on the vendor system sees this IDoc among the wrong and can resolve the situation. If the error is in the master data in the vendor system, it can fix it and order IDoc to process it again.
Due to the flexibility and transparency of IDoc technology, some non-SAP technologies use it as well.
Video IDoc
Struktur IDoc
IDoc consists of
- Control notes (this contains IDoc types, partner ports, SAP R/3 releases that generate IDoc etc.)
- Data records of various types. The number and type of segments are mostly fixed for each IDoc type, but there is some flexibility (eg an SD order can have any number of items).
- The status record contains messages like 'IDOC created', 'Recipient is there', 'IDoc successfully passed to port', 'Can not order invoice because..'
The following transactions can be used to create and process IDocs. This list does not include transactions required for the development of new IDOC types. Please note that you get a full list of available transactions using the WEDI area menu.
- WE02 - IDoc List Report
- WE05 - IDoc List
- WE09 - IDoc Search for Business Content
- WLF_IDOC - IDoc Processing
- This transaction is used to display and edit IDocs.
- WE19 - Test Tools for Idok Processing
- WE20 - Partner Profile
- This transaction specifies the processing code based on the partner profile identified by the IDoc control records.
- WE21 - Ports in IDOC processing
- This transaction identifies an external port (RFC, File, ABAP-PI, etc.) that controls IDoc flow to an external system.
- WE30 - Type IDoc Development
- WE31 - Development of IDoc Segment
- WE32 - Development IDoc Display
- WE41 - Code of the exit process
- This transaction links the exit processing code specified in the partner profile to the function module.
- WE42 - Login process code
- This transaction links the login code specified in the partner profile to the function module.
- WE60 - IDo Documentation
- BD87 - Login process
- This transaction is processing outgoing documents.
Maps IDoc
NAST
NAST is a technique in SAP-Systems for creating messages. Messages can be printed, sent or transferred to IDocs. SAP uses this for many apps, e.g. Purchase Order (PO). PO can create messages that may be printed, sent by FAX, or translated into IDOC type ORDER. IDOC ORDERS can be forwarded in B2B process to vendor.
Error Handling
SAP provides standard reports (WE02) or (WE05) to view and edit IDocs. Unfortunately, the functionality provided is very basic; therefore, most customers are forced to create their own custom solutions..
References
External links
- Introduction to IDoc references at sdn.sap.com
- IDoc Medic - Error Handling for SAP
- IDOC Fundamentals For Functional Consultants
- Implement IDC Subsystem for NON-SAP System
Source of the article : Wikipedia
0 Comments