<?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: Delay in table update after commit work in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/delay-in-table-update-after-commit-work/m-p/6688923#M1450717</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 your BADI, check the call stack if the main program is available(In debug mode u can check this). In main program, the data you want will be in some internal table. Identify that and try in below way.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;eg: If i want to access delivery item data....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;FIELD-SYMBOLS:&amp;lt;lfs_xlips&amp;gt;  TYPE ANY.

  ASSIGN: ('(SAPMV50A)XLIPS[]')     TO &amp;lt;lfs_xlips&amp;gt;.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAPMV50A is the main program name and XLIPS is the internal table in the main program which has item data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;Other way could be EXPORT from some user exit (Say MV50AFZ1) and IMPORT in BADI.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check F1 help for more details on this. If both the ways won't work, then wait is the only option. But i am sure that one of the above will work for you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vinod.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 15 Mar 2010 14:36:35 GMT</pubDate>
    <dc:creator>vinod_vemuru2</dc:creator>
    <dc:date>2010-03-15T14:36:35Z</dc:date>
    <item>
      <title>Delay in table update after commit work</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/delay-in-table-update-after-commit-work/m-p/6688922#M1450716</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, I'm implementing a badi, this is executed after commit work executed by vl02n t-code. Here I want to access the table "SER01" to get the serial list codes associated with the materials in the delivery orders, but  the  "SER01" table is not updated yet. I give 5 seconds through "wait up to" statement until the table is updated and then get the records.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;is there another way to obtain these records without using the wait up to?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Mar 2010 14:24:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/delay-in-table-update-after-commit-work/m-p/6688922#M1450716</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-03-15T14:24:29Z</dc:date>
    </item>
    <item>
      <title>Re: Delay in table update after commit work</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/delay-in-table-update-after-commit-work/m-p/6688923#M1450717</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 your BADI, check the call stack if the main program is available(In debug mode u can check this). In main program, the data you want will be in some internal table. Identify that and try in below way.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;eg: If i want to access delivery item data....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;FIELD-SYMBOLS:&amp;lt;lfs_xlips&amp;gt;  TYPE ANY.

  ASSIGN: ('(SAPMV50A)XLIPS[]')     TO &amp;lt;lfs_xlips&amp;gt;.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAPMV50A is the main program name and XLIPS is the internal table in the main program which has item data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;Other way could be EXPORT from some user exit (Say MV50AFZ1) and IMPORT in BADI.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check F1 help for more details on this. If both the ways won't work, then wait is the only option. But i am sure that one of the above will work for you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vinod.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Mar 2010 14:36:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/delay-in-table-update-after-commit-work/m-p/6688923#M1450717</guid>
      <dc:creator>vinod_vemuru2</dc:creator>
      <dc:date>2010-03-15T14:36:35Z</dc:date>
    </item>
  </channel>
</rss>

