<?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: EDI inbound 945 problem in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/edi-inbound-945-problem/m-p/4860086#M1136373</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This might be due to the material inventory being locked if these idocs contain the same material. The ideal would be to process these sequentially. if its process immediately in WE20, then multipe idocs can get processed simultaneously and ending in error if all are using the same material.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 06 Dec 2008 03:26:19 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-12-06T03:26:19Z</dc:date>
    <item>
      <title>EDI inbound 945 problem</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/edi-inbound-945-problem/m-p/4860085#M1136372</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are using message type SHPCON and Basic type DELVRY03. Automatic inbound processing of the IDOC failing with status 51 and gives the following error:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC: XXXXXX Status: Application document not posted.&lt;/P&gt;&lt;P&gt;Object request is currently locked by user WF-BATCH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Due to this incoming idocs are not getting processed and getting queued in the EDI subsystem. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not able to find which process is getting locked by the user WF-BATCH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If we process it manually through BD87 it is able to process the IDOC.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please recommend what to do it this case.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Rohit&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Dec 2008 22:55:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/edi-inbound-945-problem/m-p/4860085#M1136372</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-12-05T22:55:48Z</dc:date>
    </item>
    <item>
      <title>Re: EDI inbound 945 problem</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/edi-inbound-945-problem/m-p/4860086#M1136373</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This might be due to the material inventory being locked if these idocs contain the same material. The ideal would be to process these sequentially. if its process immediately in WE20, then multipe idocs can get processed simultaneously and ending in error if all are using the same material.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 06 Dec 2008 03:26:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/edi-inbound-945-problem/m-p/4860086#M1136373</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-12-06T03:26:19Z</dc:date>
    </item>
    <item>
      <title>Re: EDI inbound 945 problem</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/edi-inbound-945-problem/m-p/4860087#M1136374</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is happening even for the single idoc.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 07 Dec 2008 23:10:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/edi-inbound-945-problem/m-p/4860087#M1136374</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-12-07T23:10:16Z</dc:date>
    </item>
  </channel>
</rss>

