<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: IDOC remains in status 62 or 64</title>
	<atom:link href="http://www.itcserver.com/blog/2007/06/22/idoc-remains-in-status-62-or-64/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.itcserver.com/blog/2007/06/22/idoc-remains-in-status-62-or-64/</link>
	<description>The SAP Consultant's Journey</description>
	<pubDate>Fri, 10 Feb 2012 21:52:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Jens</title>
		<link>http://www.itcserver.com/blog/2007/06/22/idoc-remains-in-status-62-or-64/#comment-79033</link>
		<dc:creator>Jens</dc:creator>
		<pubDate>Tue, 08 Jun 2010 13:13:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.itcserver.com/blog/2007/06/22/idoc-remains-in-status-62-or-64/#comment-79033</guid>
		<description>Hi, well after getting some upgrades to ERP we also received Status 64 but only for some IDoc-Types. 
Stepping by to this blogpost shows finally how to solve it.

SWU3 and OYEB finally did the job
Great stuff!!

Thx</description>
		<content:encoded><![CDATA[<p>Hi, well after getting some upgrades to ERP we also received Status 64 but only for some IDoc-Types.<br />
Stepping by to this blogpost shows finally how to solve it.</p>
<p>SWU3 and OYEB finally did the job<br />
Great stuff!!</p>
<p>Thx</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vaughn</title>
		<link>http://www.itcserver.com/blog/2007/06/22/idoc-remains-in-status-62-or-64/#comment-50001</link>
		<dc:creator>Vaughn</dc:creator>
		<pubDate>Fri, 14 Nov 2008 11:05:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.itcserver.com/blog/2007/06/22/idoc-remains-in-status-62-or-64/#comment-50001</guid>
		<description>Hi,

Thanks for the post. I also had a problem with the password. This was the first document I came across in a long time that explained everything in so much detail! Apart from having a different version of SAP, I was able to navigate to all fields thanks to your detailed explanations.

Your post, solved my problem !</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Thanks for the post. I also had a problem with the password. This was the first document I came across in a long time that explained everything in so much detail! Apart from having a different version of SAP, I was able to navigate to all fields thanks to your detailed explanations.</p>
<p>Your post, solved my problem !</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Lawblaw</title>
		<link>http://www.itcserver.com/blog/2007/06/22/idoc-remains-in-status-62-or-64/#comment-47722</link>
		<dc:creator>Bob Lawblaw</dc:creator>
		<pubDate>Fri, 19 Sep 2008 20:11:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.itcserver.com/blog/2007/06/22/idoc-remains-in-status-62-or-64/#comment-47722</guid>
		<description>Glad to hear this story had a happy ending. I have had my own problems with data synchronization in the past so I know what a headache it can be. I always find that with a klittle bit of determination there is no &lt;a href="http://www.emanio.com/" rel="nofollow"&gt;edi&lt;/a&gt; problem that can't be solved.</description>
		<content:encoded><![CDATA[<p>Glad to hear this story had a happy ending. I have had my own problems with data synchronization in the past so I know what a headache it can be. I always find that with a klittle bit of determination there is no <a href="http://www.emanio.com/" rel="nofollow">edi</a> problem that can&#8217;t be solved.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

