<?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: idoc debugging in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-debugging/m-p/2143883#M451985</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Pavan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) We generally go for customized IDocs if none of the SAP standard IDoc does not suit our need/business process. Creating is custom IDoc should be a very stringent process. The SAP standard IDocs should be rigorously checked (if any user exits can be of our help or IDoc extension will solve the purpose).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) WE19 is the test tool by which we can create IDocs to see whether our functionality is working. It is mostly used to debug inbound function modules.&lt;/P&gt;&lt;P&gt;For outbound function module debugging you can use the following:&lt;/P&gt;&lt;P&gt;  1) RBDMIDOC - for master IDocs configured via change pointers.&lt;/P&gt;&lt;P&gt;  2) RSNASTED - for transaction IDocs with output/message control.&lt;/P&gt;&lt;P&gt;  3) RSEOUT00 - For IDoc whose status is "to be processed".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Gajendra.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 09 Apr 2007 10:48:10 GMT</pubDate>
    <dc:creator>gajendra_bhakuni</dc:creator>
    <dc:date>2007-04-09T10:48:10Z</dc:date>
    <item>
      <title>idoc debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-debugging/m-p/2143881#M451983</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi gurus,&lt;/P&gt;&lt;P&gt;1)     PLZ tell me in what situation we go for creating customized IDOC i.e writing posting and selection programing???&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2)how to do IDOC debugging?and how do we test weather our IDOC is functioning properly or not?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanx.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 07 Apr 2007 03:17:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-debugging/m-p/2143881#M451983</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-07T03:17:30Z</dc:date>
    </item>
    <item>
      <title>Re: idoc debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-debugging/m-p/2143882#M451984</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;We can Debug Idoc by using Tcode : We19&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Sunil&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Apr 2007 09:59:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-debugging/m-p/2143882#M451984</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-09T09:59:13Z</dc:date>
    </item>
    <item>
      <title>Re: idoc debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-debugging/m-p/2143883#M451985</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Pavan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) We generally go for customized IDocs if none of the SAP standard IDoc does not suit our need/business process. Creating is custom IDoc should be a very stringent process. The SAP standard IDocs should be rigorously checked (if any user exits can be of our help or IDoc extension will solve the purpose).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) WE19 is the test tool by which we can create IDocs to see whether our functionality is working. It is mostly used to debug inbound function modules.&lt;/P&gt;&lt;P&gt;For outbound function module debugging you can use the following:&lt;/P&gt;&lt;P&gt;  1) RBDMIDOC - for master IDocs configured via change pointers.&lt;/P&gt;&lt;P&gt;  2) RSNASTED - for transaction IDocs with output/message control.&lt;/P&gt;&lt;P&gt;  3) RSEOUT00 - For IDoc whose status is "to be processed".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Gajendra.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Apr 2007 10:48:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-debugging/m-p/2143883#M451985</guid>
      <dc:creator>gajendra_bhakuni</dc:creator>
      <dc:date>2007-04-09T10:48:10Z</dc:date>
    </item>
    <item>
      <title>Re: idoc debugging</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-debugging/m-p/2143884#M451986</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;in order to get the status of your idoc you can go to TCODE - WE05,&lt;/P&gt;&lt;P&gt;in that give the date of the idoc created and the message type(if you know),once you give all these details and execute it will list all the idoc created under the conditions you have selected  along with the status of the idoc &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;We can identify the process with the number of status record.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Outbound Process&lt;/P&gt;&lt;P&gt;	 Sending out the data from our system. The IDOC which is called as Outbound IDOC&lt;/P&gt;&lt;P&gt;   01 - 49  for Outbound Process&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Inbound Process&lt;/P&gt;&lt;P&gt;    When the data is coming in, the process is called Inbound Process and the IDoc is known as Inbound IDoc.&lt;/P&gt;&lt;P&gt;   50 - 75  for Inbound Process&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Apr 2007 11:31:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-debugging/m-p/2143884#M451986</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-09T11:31:23Z</dc:date>
    </item>
  </channel>
</rss>

