<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic What is an IDOC ? in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/what-is-an-idoc/m-p/1892171#M373323</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does somebody can explain me what is an IDOC, or what kind of work we do with this tool, what is the proposal of an IDOC ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Frank&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 17 Jan 2007 17:21:20 GMT</pubDate>
    <dc:creator>former_member425121</dc:creator>
    <dc:date>2007-01-17T17:21:20Z</dc:date>
    <item>
      <title>What is an IDOC ?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/what-is-an-idoc/m-p/1892171#M373323</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does somebody can explain me what is an IDOC, or what kind of work we do with this tool, what is the proposal of an IDOC ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Frank&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Jan 2007 17:21:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/what-is-an-idoc/m-p/1892171#M373323</guid>
      <dc:creator>former_member425121</dc:creator>
      <dc:date>2007-01-17T17:21:20Z</dc:date>
    </item>
    <item>
      <title>Re: What is an IDOC ?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/what-is-an-idoc/m-p/1892172#M373324</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Frank,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this will help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ferry Lianto&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Jan 2007 17:23:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/what-is-an-idoc/m-p/1892172#M373324</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-17T17:23:21Z</dc:date>
    </item>
    <item>
      <title>Re: What is an IDOC ?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/what-is-an-idoc/m-p/1892173#M373325</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi Frank,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Idoc is not a tool or IDoc is not a process.....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOCs are stored in the database.  In the SAP system, IDOCs are stored in database tables. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOCs are independent of the sending and receiving systems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOCs are independent of the direction of data exchange.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Business data is exchanged with an external system using the IDoc Interface.&lt;/P&gt;&lt;P&gt;The IDoc Interface consists of the definition of a data structure and a processing logic.&lt;/P&gt;&lt;P&gt;The data structure is the IDoc. &lt;/P&gt;&lt;P&gt;It is the exchange format that unites the communicating systems&lt;/P&gt;&lt;P&gt;An IDoc is used in the following situation&lt;/P&gt;&lt;P&gt;Electronic Data Exchange (EDI) &lt;/P&gt;&lt;P&gt;Application Link Enabling (ALE) &lt;/P&gt;&lt;P&gt;Linking to any other business application systems&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are basically two types of IDOCs. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basic IDOCs &lt;/P&gt;&lt;P&gt;Extended IDOCs &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Idoc Components &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basic Idoc &lt;/P&gt;&lt;P&gt;Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Extension Idoc &lt;/P&gt;&lt;P&gt;Extending the functionality by adding more segments to existing Basic IDOCs. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Creation of IDoc &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To Create Idoc we need to follow these steps: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create Segment ( WE31) &lt;/P&gt;&lt;P&gt;Create Idoc Type ( WE30) &lt;/P&gt;&lt;P&gt;Create Message Type ( WE81) &lt;/P&gt;&lt;P&gt;Assign Idoc Type to Message Type ( WE82) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Creating a Segment &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Go to transaction code WE31 &lt;/P&gt;&lt;P&gt;Enter the name for your segment type and click on the Create icon &lt;/P&gt;&lt;P&gt;Type the short text &lt;/P&gt;&lt;P&gt;Enter the variable names and data elements &lt;/P&gt;&lt;P&gt;Save it and go back &lt;/P&gt;&lt;P&gt;Go to Edit -&amp;gt; Set Release &lt;/P&gt;&lt;P&gt;Follow steps to create more number of segments &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create IDOC Type &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Go to transaction code WE30 &lt;/P&gt;&lt;P&gt;Enter the Object Name, select Basic type and click Create icon &lt;/P&gt;&lt;P&gt;Select the create new option and enter a description for your basic IDOC type and press enter &lt;/P&gt;&lt;P&gt;Select the IDOC Name and click Create icon &lt;/P&gt;&lt;P&gt;The system prompts us to enter a segment type and its attributes &lt;/P&gt;&lt;P&gt;Choose the appropriate values and press Enter &lt;/P&gt;&lt;P&gt;The system transfers the name of the segment type to the IDOC editor. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create IDOC Type &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Follow these steps to add more number of segments to Parent or as Parent-child relation &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Save it and go back &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Go to Edit -&amp;gt; Set release &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create Message Type &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Go to transaction code WE81 &lt;/P&gt;&lt;P&gt;Change the details from Display mode to Change mode &lt;/P&gt;&lt;P&gt;After selection, the system will give this message &amp;#147;The table is cross-client (see Help for further info)&amp;#148;. Press Enter &lt;/P&gt;&lt;P&gt;Click New Entries to create new Message Type &lt;/P&gt;&lt;P&gt;Fill details &lt;/P&gt;&lt;P&gt;Save it and go back &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Assign Message Type to IDoc Type &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Go to transaction code WE82 &lt;/P&gt;&lt;P&gt;Change the details from Display mode to Change mode &lt;/P&gt;&lt;P&gt;After selection, the system will give this message &amp;#147;The table is cross-client (see Help for further info)&amp;#148;. Press Enter. &lt;/P&gt;&lt;P&gt;Click New Entries to create new Message Type. &lt;/P&gt;&lt;P&gt;Fill details &lt;/P&gt;&lt;P&gt;Save it and go back &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you find it useful mark the points&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;~~Guduri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Jan 2007 17:30:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/what-is-an-idoc/m-p/1892173#M373325</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-17T17:30:49Z</dc:date>
    </item>
    <item>
      <title>Re: What is an IDOC ?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/what-is-an-idoc/m-p/1892174#M373326</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks both&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have now an idea about what is an IDOC, i'm going to reward points, just because i can give ten points twice, i will give for first answer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What does the RFC make ? , the IDOC has the data, it is transported via ALE or EDI, the sender program creates the IDOC; then the RFC is used to trigger the sending ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Frank&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Jan 2007 17:54:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/what-is-an-idoc/m-p/1892174#M373326</guid>
      <dc:creator>former_member425121</dc:creator>
      <dc:date>2007-01-17T17:54:37Z</dc:date>
    </item>
    <item>
      <title>Re: What is an IDOC ?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/what-is-an-idoc/m-p/1892175#M373327</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Frank&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. The Remote Function Call facility allows you to call an R/3 Function module on a &amp;#147;remote&amp;#148; machine.&lt;/P&gt;&lt;P&gt;2.  To communicate between two R/3 Systems and also with an External System.  External Application program also can call these function module for integration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you execute an RFC call, a number of task are automatically &lt;/P&gt;&lt;P&gt;  performed. These include:                                                                                &lt;/P&gt;&lt;P&gt;- Data conversion                                                &lt;/P&gt;&lt;P&gt;  - Logon to the SAP partner system                                &lt;/P&gt;&lt;P&gt;  - Conversion of all RFC data types                               &lt;/P&gt;&lt;P&gt;  - Control of the communication flow&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;~~Guduri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Jan 2007 18:00:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/what-is-an-idoc/m-p/1892175#M373327</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-17T18:00:01Z</dc:date>
    </item>
  </channel>
</rss>

