<?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: Orders IDocs Processing With Wrong Data in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/orders-idocs-processing-with-wrong-data/m-p/1024160#M81947</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;Maintain the sequence# to the field Serialization in control record. &lt;/P&gt;&lt;P&gt;This Serialization feild allows the IDoc types to be placed in the correct order in the target system if this order was changed during transmission.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Naga&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 08 Dec 2005 18:14:42 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2005-12-08T18:14:42Z</dc:date>
    <item>
      <title>Orders IDocs Processing With Wrong Data</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/orders-idocs-processing-with-wrong-data/m-p/1024158#M81945</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm a very experienced IDoc ABAP programmer and cannot figure this one out.  We are parallel processing inbound ORDERS using IDOC_INPUT_ORDERS to create sales orders.  Inside the VA01 exit MV45AFZB / USEREXIT_CHECK_VBKD, we have a custom BADI call that checks for a duplicate PO number (against a Z table).  The call from the exit passes VBAK-BSTNK to the BADI at which time we check if the PO exists in a custom table.  If so, we invoke an error message.  If not, we update the custom table for subsequent checks.  However, IDoc 1 will come and post and update the Z table with IDoc 1's PO number.  Then IDoc 2 will come and fail on this check EVEN THOUGH IT HAS A UNIQUE PO NUMBER IN THE IDOC.  Even the error message in IDoc 2's status 51 message has IDoc 1's PO number?  So far I cannot re-create the issue.  For example, I've created 20+ IDocs and made ~5 contain duplicate PO numbers.  I parallel processed them and they successfully created orders while properly erroring the duplicates.  I've double-checked the IDoc posting program exits to ensure we weren't passing the wrong PO number to the application and they look OK.  Somehow, someway, when IDoc 2 runs, VA02 has IDoc 1's data???  Further, the error is rare.  In 99% of our runs, no issues.  But the error is pretty severe as we can create orders with invalid key data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas would be appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Keith&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Dec 2005 18:31:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/orders-idocs-processing-with-wrong-data/m-p/1024158#M81945</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-12-06T18:31:37Z</dc:date>
    </item>
    <item>
      <title>Re: Orders IDocs Processing With Wrong Data</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/orders-idocs-processing-with-wrong-data/m-p/1024159#M81946</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Keith!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My first questions in case of such problems is always: do you use somewhere export/import?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also global data in function modules is a dangerous place for overwriting - but just inside one session, not cross-session. (e.g. reading two times different articles into global MARA)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Something in synchronic part of IDOC creation? Only if you use user-exits, otherwise it's just simple value moving and IDOC saving for parallel execution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would be much easier, if you have no error in case of double numbers... than a lot about missing / late commit work and buffering could be said.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible, that you e.g. book 5 IDOCs sequential in one session, parallel with other session à 5 IDOCs? &lt;/P&gt;&lt;P&gt;Then maybe errors inside one session can occur. Using global data, which was neither refreshed or overwritten by new access... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Strange, but still have a look for export into memory!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Christian&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Dec 2005 18:01:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/orders-idocs-processing-with-wrong-data/m-p/1024159#M81946</guid>
      <dc:creator>christian_wohlfahrt</dc:creator>
      <dc:date>2005-12-08T18:01:33Z</dc:date>
    </item>
    <item>
      <title>Re: Orders IDocs Processing With Wrong Data</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/orders-idocs-processing-with-wrong-data/m-p/1024160#M81947</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;Maintain the sequence# to the field Serialization in control record. &lt;/P&gt;&lt;P&gt;This Serialization feild allows the IDoc types to be placed in the correct order in the target system if this order was changed during transmission.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Naga&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Dec 2005 18:14:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/orders-idocs-processing-with-wrong-data/m-p/1024160#M81947</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-12-08T18:14:42Z</dc:date>
    </item>
  </channel>
</rss>

