<?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: Call transaction inside Update task in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-inside-update-task/m-p/2492729#M562656</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;   Calling a FM in Update Task is one of the bundling techniques used in ABAP to avail functionality provided by SAP Update System. Here all database updates are processed at the end of the SAP LUW in contrast to normal FM call where the database updates are done and commited at the time of call (Database LUW). It is necessary to bundle all your database updates in an SAP LUW e.g. all database updates in a transaction (like VA01) should be bundled. Almost all standard SAP transactions use bundling techniques.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This technique separates the dialog process and update process. The dialog part of the transaction can span more than one screen(one dialog step) and can be processsed by more than one dialog work process. A work process is released when the dialog step changes (screen changes) and the work process sends a database commit (called Implicit Database LUW). So with each screen change there is a database commit and database remains in consistent state. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now when using bundling technique, when a COMMIT WORK is encountered, system ends the dialog process with a dialog work porcess and starts the update process using an update work process. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The dialog step containing the COMMIT WORK is considerd as the last dialog step of the transaction and all the update function modules are processed now in the last dialog step by the update work process though they were called earlier during the earlier dialog steps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is necessary to create update FMs to take advantage of this technique. The update FM is created FM by setting the Update moduleradiobutton in the Attributes tab in SE37.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In a normal FM call, if there are database updates (UPDATE, INSERT, MODIFY, DELETE) than database is commited after the FM processing is over as the FM starts its own Database LUW and ends it too. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Reward Points&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 17 Jul 2007 12:06:53 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-07-17T12:06:53Z</dc:date>
    <item>
      <title>Call transaction inside Update task</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-inside-update-task/m-p/2492728#M562655</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;lt;b&amp;gt;Is it possible to use call transaction inside an update function module?&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My requirement is like this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I execute LB10 storage units will be created..then we have to go to lt09 and then create a TO's there for all these Storage units..&lt;/P&gt;&lt;P&gt;Now, when I try to call a bdc session from an exit, the storage units are not  updated there. so the BDC is getting failed..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To resolve this, I kept all the BDC code in to a Zfunction module and made it an update funtion module. I am calling this function module form the exit IN UPDATE TASK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But the call transaction is not working....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have tried with L_TO_CREATE_MOVE_SU inside the Z function module..Still no use..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;is there any other way that I can solve this?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jul 2007 11:58:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-inside-update-task/m-p/2492728#M562655</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-17T11:58:33Z</dc:date>
    </item>
    <item>
      <title>Re: Call transaction inside Update task</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-inside-update-task/m-p/2492729#M562656</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;   Calling a FM in Update Task is one of the bundling techniques used in ABAP to avail functionality provided by SAP Update System. Here all database updates are processed at the end of the SAP LUW in contrast to normal FM call where the database updates are done and commited at the time of call (Database LUW). It is necessary to bundle all your database updates in an SAP LUW e.g. all database updates in a transaction (like VA01) should be bundled. Almost all standard SAP transactions use bundling techniques.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This technique separates the dialog process and update process. The dialog part of the transaction can span more than one screen(one dialog step) and can be processsed by more than one dialog work process. A work process is released when the dialog step changes (screen changes) and the work process sends a database commit (called Implicit Database LUW). So with each screen change there is a database commit and database remains in consistent state. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now when using bundling technique, when a COMMIT WORK is encountered, system ends the dialog process with a dialog work porcess and starts the update process using an update work process. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The dialog step containing the COMMIT WORK is considerd as the last dialog step of the transaction and all the update function modules are processed now in the last dialog step by the update work process though they were called earlier during the earlier dialog steps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is necessary to create update FMs to take advantage of this technique. The update FM is created FM by setting the Update moduleradiobutton in the Attributes tab in SE37.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In a normal FM call, if there are database updates (UPDATE, INSERT, MODIFY, DELETE) than database is commited after the FM processing is over as the FM starts its own Database LUW and ends it too. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Reward Points&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jul 2007 12:06:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-inside-update-task/m-p/2492729#M562656</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-17T12:06:53Z</dc:date>
    </item>
    <item>
      <title>Re: Call transaction inside Update task</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-inside-update-task/m-p/2492730#M562657</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;have u marked that function module as &amp;lt;b&amp;gt;'UPDATE'&amp;lt;/b&amp;gt; in se37 Attributes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;and be sure that commit work should not be inside the function module called instead it should be in the calling program after function module gets executed.&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;ravish&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;plz dont forget to reward if useful&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jul 2007 12:07:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-inside-update-task/m-p/2492730#M562657</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-17T12:07:42Z</dc:date>
    </item>
    <item>
      <title>Re: Call transaction inside Update task</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-inside-update-task/m-p/2492731#M562658</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Use  Call transaction always&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you use call transaction in your case use update mode 'S',then your problem will be solved.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you use update mode 'S',it will update record transaction level as well database level,then cursor will go next record,you get message number in BDCMSGCOLL if you want to have ..read the message using T100 table so that you will get language description.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;syntax :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;call transaction tcode using bdcdata&lt;/P&gt;&lt;P&gt;           mode 'A/E/N'&lt;/P&gt;&lt;P&gt;           update 'S'&lt;/P&gt;&lt;P&gt;          messages into bdcmsgcoll.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Seshu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jul 2007 12:11:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-inside-update-task/m-p/2492731#M562658</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-17T12:11:03Z</dc:date>
    </item>
    <item>
      <title>Re: Call transaction inside Update task</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-inside-update-task/m-p/2492732#M562659</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;and add addition as separate unit it will work&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jul 2007 12:11:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-inside-update-task/m-p/2492732#M562659</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-17T12:11:28Z</dc:date>
    </item>
    <item>
      <title>Re: Call transaction inside Update task</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-inside-update-task/m-p/2492733#M562660</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Does this mean we can't call BDC programs from Update function module?&lt;/P&gt;&lt;P&gt;I have already set appropriate settings in attributes...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jul 2007 12:14:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-inside-update-task/m-p/2492733#M562660</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-17T12:14:01Z</dc:date>
    </item>
    <item>
      <title>Re: Call transaction inside Update task</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-inside-update-task/m-p/2492734#M562661</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;as u add a addition as &amp;lt;b&amp;gt;As separate unit&amp;lt;/b&amp;gt; the FM will be excuted as separate unit and it will reflect to the current &amp;lt;b&amp;gt;luw&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jul 2007 12:14:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-inside-update-task/m-p/2492734#M562661</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-17T12:14:46Z</dc:date>
    </item>
    <item>
      <title>Re: Call transaction inside Update task</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-inside-update-task/m-p/2492735#M562662</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;sorry some correction&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;as u add a addition as &amp;lt;b&amp;gt;As separate unit&amp;lt;/b&amp;gt; the FM will be excuted as separate unit and it will not reflect to the current &amp;lt;b&amp;gt;luw&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jul 2007 12:15:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-inside-update-task/m-p/2492735#M562662</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-17T12:15:58Z</dc:date>
    </item>
    <item>
      <title>Re: Call transaction inside Update task</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-inside-update-task/m-p/2492736#M562663</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;AS SEPARATE UNIT addition is applied for IN BACKGROUND TASK ..Isn't it?&lt;/P&gt;&lt;P&gt;can be given for IN UPDATE TASK too?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jul 2007 12:24:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-inside-update-task/m-p/2492736#M562663</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-17T12:24:35Z</dc:date>
    </item>
    <item>
      <title>Re: Call transaction inside Update task</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-inside-update-task/m-p/2492737#M562664</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Kalyan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; As far as my knowledge goes in Updates in SAP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; We cannot use CALL TRANSACTION...&lt;/P&gt;&lt;P&gt;                        LEAVE TO TRANSACTION...&lt;/P&gt;&lt;P&gt;                        SUBMIT...&lt;/P&gt;&lt;P&gt;                        SUBMIT.. AND RETURN&lt;/P&gt;&lt;P&gt; statements in update Function Modules. They do not stand any significance in update Function Modules.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Try to do a Synchronous update by COMMIT WORK AND WAIT instead of Asynchronous Update using COMMIT WORK. After the explicit COMMIT WORK AND WAIT statement try to do your CALL TRANSACTION...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I do not know whether the above can be done in your scenario, But i am pretty sure that you cannot use CALL TRANSACTION in update FM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Goutham.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please let me know if you have further inputs.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jul 2007 12:50:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-inside-update-task/m-p/2492737#M562664</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-17T12:50:22Z</dc:date>
    </item>
  </channel>
</rss>

