<?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: how to debug Idocs in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-debug-idocs/m-p/2355502#M520402</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jyothsna,&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;Regards&lt;/P&gt;&lt;P&gt;Aneesh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 11 Jun 2007 15:46:40 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-06-11T15:46:40Z</dc:date>
    <item>
      <title>how to debug Idocs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-debug-idocs/m-p/2355500#M520400</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;how to debug idocs??&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Jun 2007 15:38:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-debug-idocs/m-p/2355500#M520400</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-11T15:38:08Z</dc:date>
    </item>
    <item>
      <title>Re: how to debug Idocs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-debug-idocs/m-p/2355501#M520401</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;You can use WE19 to debug IDoc.&lt;/P&gt;&lt;P&gt;&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>Mon, 11 Jun 2007 15:39:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-debug-idocs/m-p/2355501#M520401</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-11T15:39:06Z</dc:date>
    </item>
    <item>
      <title>Re: how to debug Idocs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-debug-idocs/m-p/2355502#M520402</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jyothsna,&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;Regards&lt;/P&gt;&lt;P&gt;Aneesh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Jun 2007 15:46:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-debug-idocs/m-p/2355502#M520402</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-11T15:46:40Z</dc:date>
    </item>
  </channel>
</rss>

