<?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 Re: idocs in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/idocs/m-p/3377139#M810898</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;Data Creation in Idoc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an &lt;/P&gt;&lt;P&gt;asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDoc is a intermediate document to exchange data between two SAP Systems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*IDocs are structured ASCII files (or a virtual equivalent). &lt;/P&gt;&lt;P&gt;*Electronic Interchange Document&lt;/P&gt;&lt;P&gt;*They are the file format used by SAP R/3 to exchange data with foreign systems.&lt;/P&gt;&lt;P&gt;*Data Is transmitted in ASCII format, i.e. human readable form&lt;/P&gt;&lt;P&gt;*IDocs exchange messages&lt;/P&gt;&lt;P&gt;*IDocs are used like classical interface files&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC types are templates for specific message types depending on what is the business document, you want to exchange.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WE30 - you can create a IDOC type.&lt;/P&gt;&lt;P&gt;An IDOC with data, will have to be triggered by the application that is trying to send out the data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FOr testing you can use WE19.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How to create idoc?&lt;/P&gt;&lt;P&gt;*WE30 - you can create a IDOC type&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For more information in details on the same along with the examples can be viewed on:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/presentation.html" target="test_blank"&gt;http://www.sappoint.com/presentation.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_search.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_search.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/idoc_abap.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/idoc_abap.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.erpgenie.com/sapedi/idoc_abap.htm" target="test_blank"&gt;http://www.erpgenie.com/sapedi/idoc_abap.htm&lt;/A&gt;&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;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;Creating a Segment&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;Create IDOC Type&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;Follow these steps to add more number of segments to Parent or as Parent-child relation&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;&lt;/P&gt;&lt;P&gt;Create Message Type&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;Assign Message Type to IDoc Type&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;Check these out..&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="2402859"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check below link. It will give the step by step procedure for IDOC creation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.supinfo-projects.com/cn/2005/idocs_en/2/" target="test_blank"&gt;http://www.supinfo-projects.com/cn/2005/idocs_en/2/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ALE/ IDOC&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank"&gt;http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap/ale.pdf" target="test_blank"&gt;http://www.sappoint.com/abap/ale.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap/ale2.pdf" target="test_blank"&gt;http://www.sappoint.com/abap/ale2.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/idoc_abap.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/idoc_abap.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap.html" target="test_blank"&gt;http://www.sappoint.com/abap.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank"&gt;http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;go trough these links.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank"&gt;http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap/ale.pdf" target="test_blank"&gt;http://www.sappoint.com/abap/ale.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap/ale2.pdf" target="test_blank"&gt;http://www.sappoint.com/abap/ale2.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/idoc_abap.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/idoc_abap.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap.html" target="test_blank"&gt;http://www.sappoint.com/abap.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank"&gt;http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&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;1.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;2.IDOCs are independent of the sending and receiving systems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3.IDOCs are independent of the direction of data exchange.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The two available process for IDOCs are&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Outbound Process&lt;/P&gt;&lt;P&gt;Inbound Process&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AND There are basically two types of IDOCs.&lt;/P&gt;&lt;P&gt;Basic IDOCs&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;Extended IDOCs&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;To Create Idoc we need to follow these steps:&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;imp links&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/idoc_abap.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/idoc_abap.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.sap.com/www.sappoint.com" target="test_blank"&gt;www.sappoint.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;--here u can find the ppts and basic seetings for ALE&lt;/P&gt;&lt;P&gt;&lt;A href="http://sappoint.com/presentation.html" target="test_blank"&gt;http://sappoint.com/presentation.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.sap.com/www.sapgenie.com" target="test_blank"&gt;www.sapgenie.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/ale/index.htm" target="test_blank"&gt;http://www.sapgenie.com/ale/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; WE30 - you can create a IDOC type.&lt;/P&gt;&lt;P&gt;An IDOC with data, will have to be triggered by the application that is trying to send out the data.&lt;/P&gt;&lt;P&gt;Try this..Hope this will help.&lt;/P&gt;&lt;P&gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt; SAP ALE &amp;amp; IDOC&amp;lt;&amp;lt;&amp;lt;&amp;lt; &lt;/P&gt;&lt;P&gt;Steps to configuration(Basis) &amp;gt;&amp;gt; &lt;/P&gt;&lt;P&gt;1. Create Logical System (LS) for each applicable ALE-enabled client &lt;/P&gt;&lt;P&gt;2. Link client to Logical System on the respective servers &lt;/P&gt;&lt;P&gt;3. Create background user, to be used by ALE(with authorizaton for ALE postings) &lt;/P&gt;&lt;P&gt;4. Create RFC Destinations(SM59) &lt;/P&gt;&lt;P&gt;5. Ports in Idoc processing(WE21) &lt;/P&gt;&lt;P&gt;6. Generate partner profiles for sending system &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The functional configuration(Tcode: SALE) &lt;/P&gt;&lt;P&gt;&amp;#149; Create a Customer Distribution Model (CDM); &lt;/P&gt;&lt;P&gt;&amp;#149; Add appropriate message types and filters to the CDM; &lt;/P&gt;&lt;P&gt;&amp;#149; Generate outbound partner profiles; &lt;/P&gt;&lt;P&gt;&amp;#149; Distribute the CDM to the receiving systems; and &lt;/P&gt;&lt;P&gt;&amp;#149; Generate inbound partner profiles on each of the clients. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Steps to customize a new IDoc &amp;gt;&amp;gt;&amp;gt; &lt;/P&gt;&lt;P&gt;1. Define IDoc Segment (WE31) &lt;/P&gt;&lt;P&gt;2. Convert Segments into an IDoc type (WE30) &lt;/P&gt;&lt;P&gt;3. Create a Message Type (WE81) &lt;/P&gt;&lt;P&gt;4. Create valid Combination of Message &amp;amp; IDoc type(WE82) &lt;/P&gt;&lt;P&gt;5. Define Processing Code(WE41 for OUT / WE42 for IN) &lt;/P&gt;&lt;P&gt;6. Define Partner Profile(WE20) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Important Transaction Codes: &lt;/P&gt;&lt;P&gt;SALE - IMG ALE Configuration root &lt;/P&gt;&lt;P&gt;WE20 - Manually maintain partner profiles &lt;/P&gt;&lt;P&gt;BD64 - Maintain customer distribution model &lt;/P&gt;&lt;P&gt;BD71 - Distribute customer distribution model &lt;/P&gt;&lt;P&gt;SM59 - Create RFC Destinations &lt;/P&gt;&lt;P&gt;BDM5 - Consistency check (Transaction scenarios) &lt;/P&gt;&lt;P&gt;BD82 - Generate Partner Profiles &lt;/P&gt;&lt;P&gt;BD61 - Activate Change Pointers - Globally &lt;/P&gt;&lt;P&gt;BD50 - Activate Change Pointer for Msg Type &lt;/P&gt;&lt;P&gt;BD52 - Activate change pointer per change.doc object &lt;/P&gt;&lt;P&gt;BD59 - Allocation object type -&amp;gt; IDOC type &lt;/P&gt;&lt;P&gt;BD56 - Maintain IDOC Segment Filters &lt;/P&gt;&lt;P&gt;BD53 - Reduction of Message Types &lt;/P&gt;&lt;P&gt;BD21 - Select Change Pointer &lt;/P&gt;&lt;P&gt;BD87 - Status Monitor for ALE Messages &lt;/P&gt;&lt;P&gt;BDM5 - Consistency check (Transaction scenarios) &lt;/P&gt;&lt;P&gt;BD62 - Define rules &lt;/P&gt;&lt;P&gt;BD79 - Maintain rules &lt;/P&gt;&lt;P&gt;BD55 - Defining settings for IDoc conversion &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WEDI - ALE IDoc Administration &lt;/P&gt;&lt;P&gt;WE21 - Ports in Idoc processing &lt;/P&gt;&lt;P&gt;WE60 - IDoc documentation &lt;/P&gt;&lt;P&gt;SARA - IDoc archiving (Object type IDOC) &lt;/P&gt;&lt;P&gt;WE47 - IDoc status maintenance &lt;/P&gt;&lt;P&gt;WE07 - IDoc statistics &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BALE - ALE Distribution Administration &lt;/P&gt;&lt;P&gt;WE05 - IDoc overview &lt;/P&gt;&lt;P&gt;BD87 - Inbound IDoc reprocessing &lt;/P&gt;&lt;P&gt;BD88 - Outbound IDoc reprocessing &lt;/P&gt;&lt;P&gt;BDM2 - IDoc Trace &lt;/P&gt;&lt;P&gt;BDM7 - IDoc Audit Analysis &lt;/P&gt;&lt;P&gt;BD21 - Create IDocs from change pointers &lt;/P&gt;&lt;P&gt;SM58 - Schedule RFC Failures &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basic config for Distributed data: &lt;/P&gt;&lt;P&gt;BD64: Maintain a Distributed Model &lt;/P&gt;&lt;P&gt;BD82: Generate Partner Profile &lt;/P&gt;&lt;P&gt;BD64: Distribute the distribution Model &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Programs &lt;/P&gt;&lt;P&gt;RBDMIDOC &amp;#150; Creating IDoc Type from Change Pointers &lt;/P&gt;&lt;P&gt;RSEOUT00 &amp;#150; Process all selected IDocs (EDI) &lt;/P&gt;&lt;P&gt;RBDAPP01 - Inbound Processing of IDocs Ready for Transfer &lt;/P&gt;&lt;P&gt;RSARFCEX - Execute Calls Not Yet Executed &lt;/P&gt;&lt;P&gt;RBDMOIND - Status Conversion with Successful tRFC Execution &lt;/P&gt;&lt;P&gt;RBDMANIN - Start error handling for non-posted IDocs &lt;/P&gt;&lt;P&gt;RBDSTATE - Send Audit Confirmations &lt;/P&gt;&lt;P&gt;FOr testing you can use WE19.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;with regards,&lt;/P&gt;&lt;P&gt;sowjanya.gosala.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 15 Feb 2008 07:52:37 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-02-15T07:52:37Z</dc:date>
    <item>
      <title>idocs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/idocs/m-p/3377136#M810895</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; how to send idoc form one sap system to another sap system&lt;/P&gt;&lt;P&gt; please tell me with example&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Feb 2008 03:44:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/idocs/m-p/3377136#M810895</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-15T03:44:39Z</dc:date>
    </item>
    <item>
      <title>Re: idocs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/idocs/m-p/3377137#M810896</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Venkat,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;STEP BY STEP procedure to create idoc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Salesorder IDOC&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this example a purchase is created, using the SAP standard functionallity for creating salesorders. When the salesorder is saved, and IDOC is automatically generated. Then we use the IDOC test tool to &lt;/P&gt;&lt;P&gt;create an order confirmation from the salesorder IDOC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create Vendor&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create customer&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create partner profiles&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create purchase order&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create the order confirmation IDOC&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create vendor&lt;/P&gt;&lt;P&gt;Create vendor using transaction code MK01. You can also use an existing vendor.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vendor: T-BILHFN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Purch. org. : 001&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Purchase organization may vary from system to system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create Customer&lt;/P&gt;&lt;P&gt;Create a customer using transaction VD01. You could also use an existing customer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the follwing example the vendor 3471 is used.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create partner profiles&lt;/P&gt;&lt;P&gt;Create vendor partner profile&lt;/P&gt;&lt;P&gt;General data&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;Out bound parameters&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;		&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Inbound parameters&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 customer partner profile&lt;/P&gt;&lt;P&gt;General data&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;Outbound parameters&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;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Imbound parameters&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 purchase order&lt;/P&gt;&lt;P&gt;Use transaction ME21 to create the purchase order&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;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To send an IDOC when the document is finished, go to Header -&amp;gt; Messages and &lt;/P&gt;&lt;P&gt;change the output medium to EDI.&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;Then select Further Data and change Dispatch Time to Send immediately. This will &lt;/P&gt;&lt;P&gt;create the IDOC as soon as the purchase order is saved.&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;Save the document.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Use transaction WE02 to check that the IDOC has been created without errors&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 the order confirmation IDOC&lt;/P&gt;&lt;P&gt;As the system has not been configured to handle the IDOC flow, the IDOC test tool &lt;/P&gt;&lt;P&gt;is used to simulate the flow. The Order IDOC is used as a template to create the &lt;/P&gt;&lt;P&gt;order confirmation IDOC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Transaction code: WE19&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Type the number of the Order IDOC in on the start screen and select menu IDOC -&amp;gt; &lt;/P&gt;&lt;P&gt;Create to create the template.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Change the control record&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;Note that the name of the port SAPTST may vary from system to system. The name can be seen in the Sender &lt;/P&gt;&lt;P&gt;port of the IDOC&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create new E1DK02 segment&lt;/P&gt;&lt;P&gt;The E1DK02 Document header reference data segment includes references to other documents.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The new E1DK02 segment should be created as a copy of the existing E1DK02, and at the same level.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Change the following fields of the record:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Qualifier: 002&lt;/P&gt;&lt;P&gt;Document item: 10&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Qualifier = IDOC qualifier reference document = 002 = Vendor order&lt;/P&gt;&lt;P&gt;Document item =: Item number, see the item number on the purchasing document&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create E1EDP02 segment&lt;/P&gt;&lt;P&gt;The E1EDP02 Document Item Reference data includes references to other documents.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create E1EDP02 as subelement of E1EDP01 Document item General Data&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Qualifier: 001&lt;/P&gt;&lt;P&gt;Document: 4500010757&lt;/P&gt;&lt;P&gt;Document item: 10&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Qualifier : IDOC qualifier reference document 001 = Customer purchase order&lt;/P&gt;&lt;P&gt;Document : Document number &amp;#150; The number of the purchase order&lt;/P&gt;&lt;P&gt;Document item : Item number, see the item number on the purchasing document&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Changing the ACTION field at header or item level&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are working without a confirmation control key, the IDoc must have a processable action code at either &lt;/P&gt;&lt;P&gt;header or item level:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At header level, the segment field ACTION of segment E1EDK01 must be filled with the value '000' if the complete &lt;/P&gt;&lt;P&gt;purchase order is to be confirmed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At item level, the segment field ACTION of segment E1EDP01 must be filled with the value '000' or '004' if the PO &lt;/P&gt;&lt;P&gt;item is to be confirmed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Test IDOC&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After the changes have been made, press the Standard Inbound button to generate the IDOC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If no errors occurs go to transaction WE02 to check if the IDOC has been processed without errors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the IDOC has been processed without errors, then display the Purchase order (Transaction ME23). display the &lt;/P&gt;&lt;P&gt;item data and double-click on the item line. If all went well, you will now se that the field Acknowl. no. has been &lt;/P&gt;&lt;P&gt;filled out.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Feb 2008 04:04:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/idocs/m-p/3377137#M810896</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-15T04:04:07Z</dc:date>
    </item>
    <item>
      <title>Re: idocs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/idocs/m-p/3377138#M810897</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;&lt;A href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/201769e0-3174-2910-e287-baa58d198246" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/201769e0-3174-2910-e287-baa58d198246&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Hope this helps, Do reward.&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Feb 2008 04:14:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/idocs/m-p/3377138#M810897</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-15T04:14:09Z</dc:date>
    </item>
    <item>
      <title>Re: idocs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/idocs/m-p/3377139#M810898</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;Data Creation in Idoc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an &lt;/P&gt;&lt;P&gt;asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDoc is a intermediate document to exchange data between two SAP Systems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*IDocs are structured ASCII files (or a virtual equivalent). &lt;/P&gt;&lt;P&gt;*Electronic Interchange Document&lt;/P&gt;&lt;P&gt;*They are the file format used by SAP R/3 to exchange data with foreign systems.&lt;/P&gt;&lt;P&gt;*Data Is transmitted in ASCII format, i.e. human readable form&lt;/P&gt;&lt;P&gt;*IDocs exchange messages&lt;/P&gt;&lt;P&gt;*IDocs are used like classical interface files&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC types are templates for specific message types depending on what is the business document, you want to exchange.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WE30 - you can create a IDOC type.&lt;/P&gt;&lt;P&gt;An IDOC with data, will have to be triggered by the application that is trying to send out the data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FOr testing you can use WE19.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How to create idoc?&lt;/P&gt;&lt;P&gt;*WE30 - you can create a IDOC type&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For more information in details on the same along with the examples can be viewed on:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/presentation.html" target="test_blank"&gt;http://www.sappoint.com/presentation.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_search.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_search.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/idoc_abap.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/idoc_abap.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.erpgenie.com/sapedi/idoc_abap.htm" target="test_blank"&gt;http://www.erpgenie.com/sapedi/idoc_abap.htm&lt;/A&gt;&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;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;Creating a Segment&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;Create IDOC Type&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;Follow these steps to add more number of segments to Parent or as Parent-child relation&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;&lt;/P&gt;&lt;P&gt;Create Message Type&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;Assign Message Type to IDoc Type&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;Check these out..&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="2402859"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check below link. It will give the step by step procedure for IDOC creation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.supinfo-projects.com/cn/2005/idocs_en/2/" target="test_blank"&gt;http://www.supinfo-projects.com/cn/2005/idocs_en/2/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ALE/ IDOC&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank"&gt;http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap/ale.pdf" target="test_blank"&gt;http://www.sappoint.com/abap/ale.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap/ale2.pdf" target="test_blank"&gt;http://www.sappoint.com/abap/ale2.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/idoc_abap.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/idoc_abap.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap.html" target="test_blank"&gt;http://www.sappoint.com/abap.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank"&gt;http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;go trough these links.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank"&gt;http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap/ale.pdf" target="test_blank"&gt;http://www.sappoint.com/abap/ale.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap/ale2.pdf" target="test_blank"&gt;http://www.sappoint.com/abap/ale2.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/idoc_abap.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/idoc_abap.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap.html" target="test_blank"&gt;http://www.sappoint.com/abap.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank"&gt;http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&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;1.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;2.IDOCs are independent of the sending and receiving systems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3.IDOCs are independent of the direction of data exchange.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The two available process for IDOCs are&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Outbound Process&lt;/P&gt;&lt;P&gt;Inbound Process&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AND There are basically two types of IDOCs.&lt;/P&gt;&lt;P&gt;Basic IDOCs&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;Extended IDOCs&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;To Create Idoc we need to follow these steps:&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;imp links&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/idoc_abap.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/idoc_abap.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.sap.com/www.sappoint.com" target="test_blank"&gt;www.sappoint.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;--here u can find the ppts and basic seetings for ALE&lt;/P&gt;&lt;P&gt;&lt;A href="http://sappoint.com/presentation.html" target="test_blank"&gt;http://sappoint.com/presentation.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.sap.com/www.sapgenie.com" target="test_blank"&gt;www.sapgenie.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/ale/index.htm" target="test_blank"&gt;http://www.sapgenie.com/ale/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; WE30 - you can create a IDOC type.&lt;/P&gt;&lt;P&gt;An IDOC with data, will have to be triggered by the application that is trying to send out the data.&lt;/P&gt;&lt;P&gt;Try this..Hope this will help.&lt;/P&gt;&lt;P&gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt; SAP ALE &amp;amp; IDOC&amp;lt;&amp;lt;&amp;lt;&amp;lt; &lt;/P&gt;&lt;P&gt;Steps to configuration(Basis) &amp;gt;&amp;gt; &lt;/P&gt;&lt;P&gt;1. Create Logical System (LS) for each applicable ALE-enabled client &lt;/P&gt;&lt;P&gt;2. Link client to Logical System on the respective servers &lt;/P&gt;&lt;P&gt;3. Create background user, to be used by ALE(with authorizaton for ALE postings) &lt;/P&gt;&lt;P&gt;4. Create RFC Destinations(SM59) &lt;/P&gt;&lt;P&gt;5. Ports in Idoc processing(WE21) &lt;/P&gt;&lt;P&gt;6. Generate partner profiles for sending system &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The functional configuration(Tcode: SALE) &lt;/P&gt;&lt;P&gt;&amp;#149; Create a Customer Distribution Model (CDM); &lt;/P&gt;&lt;P&gt;&amp;#149; Add appropriate message types and filters to the CDM; &lt;/P&gt;&lt;P&gt;&amp;#149; Generate outbound partner profiles; &lt;/P&gt;&lt;P&gt;&amp;#149; Distribute the CDM to the receiving systems; and &lt;/P&gt;&lt;P&gt;&amp;#149; Generate inbound partner profiles on each of the clients. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Steps to customize a new IDoc &amp;gt;&amp;gt;&amp;gt; &lt;/P&gt;&lt;P&gt;1. Define IDoc Segment (WE31) &lt;/P&gt;&lt;P&gt;2. Convert Segments into an IDoc type (WE30) &lt;/P&gt;&lt;P&gt;3. Create a Message Type (WE81) &lt;/P&gt;&lt;P&gt;4. Create valid Combination of Message &amp;amp; IDoc type(WE82) &lt;/P&gt;&lt;P&gt;5. Define Processing Code(WE41 for OUT / WE42 for IN) &lt;/P&gt;&lt;P&gt;6. Define Partner Profile(WE20) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Important Transaction Codes: &lt;/P&gt;&lt;P&gt;SALE - IMG ALE Configuration root &lt;/P&gt;&lt;P&gt;WE20 - Manually maintain partner profiles &lt;/P&gt;&lt;P&gt;BD64 - Maintain customer distribution model &lt;/P&gt;&lt;P&gt;BD71 - Distribute customer distribution model &lt;/P&gt;&lt;P&gt;SM59 - Create RFC Destinations &lt;/P&gt;&lt;P&gt;BDM5 - Consistency check (Transaction scenarios) &lt;/P&gt;&lt;P&gt;BD82 - Generate Partner Profiles &lt;/P&gt;&lt;P&gt;BD61 - Activate Change Pointers - Globally &lt;/P&gt;&lt;P&gt;BD50 - Activate Change Pointer for Msg Type &lt;/P&gt;&lt;P&gt;BD52 - Activate change pointer per change.doc object &lt;/P&gt;&lt;P&gt;BD59 - Allocation object type -&amp;gt; IDOC type &lt;/P&gt;&lt;P&gt;BD56 - Maintain IDOC Segment Filters &lt;/P&gt;&lt;P&gt;BD53 - Reduction of Message Types &lt;/P&gt;&lt;P&gt;BD21 - Select Change Pointer &lt;/P&gt;&lt;P&gt;BD87 - Status Monitor for ALE Messages &lt;/P&gt;&lt;P&gt;BDM5 - Consistency check (Transaction scenarios) &lt;/P&gt;&lt;P&gt;BD62 - Define rules &lt;/P&gt;&lt;P&gt;BD79 - Maintain rules &lt;/P&gt;&lt;P&gt;BD55 - Defining settings for IDoc conversion &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WEDI - ALE IDoc Administration &lt;/P&gt;&lt;P&gt;WE21 - Ports in Idoc processing &lt;/P&gt;&lt;P&gt;WE60 - IDoc documentation &lt;/P&gt;&lt;P&gt;SARA - IDoc archiving (Object type IDOC) &lt;/P&gt;&lt;P&gt;WE47 - IDoc status maintenance &lt;/P&gt;&lt;P&gt;WE07 - IDoc statistics &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BALE - ALE Distribution Administration &lt;/P&gt;&lt;P&gt;WE05 - IDoc overview &lt;/P&gt;&lt;P&gt;BD87 - Inbound IDoc reprocessing &lt;/P&gt;&lt;P&gt;BD88 - Outbound IDoc reprocessing &lt;/P&gt;&lt;P&gt;BDM2 - IDoc Trace &lt;/P&gt;&lt;P&gt;BDM7 - IDoc Audit Analysis &lt;/P&gt;&lt;P&gt;BD21 - Create IDocs from change pointers &lt;/P&gt;&lt;P&gt;SM58 - Schedule RFC Failures &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basic config for Distributed data: &lt;/P&gt;&lt;P&gt;BD64: Maintain a Distributed Model &lt;/P&gt;&lt;P&gt;BD82: Generate Partner Profile &lt;/P&gt;&lt;P&gt;BD64: Distribute the distribution Model &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Programs &lt;/P&gt;&lt;P&gt;RBDMIDOC &amp;#150; Creating IDoc Type from Change Pointers &lt;/P&gt;&lt;P&gt;RSEOUT00 &amp;#150; Process all selected IDocs (EDI) &lt;/P&gt;&lt;P&gt;RBDAPP01 - Inbound Processing of IDocs Ready for Transfer &lt;/P&gt;&lt;P&gt;RSARFCEX - Execute Calls Not Yet Executed &lt;/P&gt;&lt;P&gt;RBDMOIND - Status Conversion with Successful tRFC Execution &lt;/P&gt;&lt;P&gt;RBDMANIN - Start error handling for non-posted IDocs &lt;/P&gt;&lt;P&gt;RBDSTATE - Send Audit Confirmations &lt;/P&gt;&lt;P&gt;FOr testing you can use WE19.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;with regards,&lt;/P&gt;&lt;P&gt;sowjanya.gosala.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Feb 2008 07:52:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/idocs/m-p/3377139#M810898</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-15T07:52:37Z</dc:date>
    </item>
  </channel>
</rss>

