<?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: RE:CALL FUNCTION update_function IN UPDATE TASK in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/re-call-function-update-function-in-update-task/m-p/3686373#M887708</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello George&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In a project dealing with material master data I had the problem that I needed to update &lt;STRONG&gt;standard&lt;/STRONG&gt; as well as &lt;STRONG&gt;customer&lt;/STRONG&gt; tables at the same time when the user pushed the SAVE button.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For the standard tables I used BAPI_MATERIAL_MAINTAINDATA_RT (retail material) and for the customer tables I created my own SAVE function modules.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How to ensure that either both (standard and custom) tables are updated or not simultaneously?&lt;/P&gt;&lt;P&gt;I created a special SAVE function module which called both the standard BAPI and my custom SAVE function modules.&lt;/P&gt;&lt;P&gt;This "wrapper" SAVE function module was then called IN UPDATE TASK.&lt;/P&gt;&lt;P&gt;This way I created a &lt;STRONG&gt;LUW&lt;/STRONG&gt; (logic unit of work) which comprised both standard and custom tables. If everything was ok both types of tables were updated, otherwise the entire transaction was rolled back.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Further reading: [Special LUW Considerations|http://help.sap.com/saphelp_nw04/helpdata/en/9f/dbae3435c111d1829f0000e829fbfe/content.htm]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Uwe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 17 Apr 2008 04:17:40 GMT</pubDate>
    <dc:creator>uwe_schieferstein</dc:creator>
    <dc:date>2008-04-17T04:17:40Z</dc:date>
    <item>
      <title>RE:CALL FUNCTION update_function IN UPDATE TASK</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/re-call-function-update-function-in-update-task/m-p/3686372#M887707</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;Can anyone give a sample code or a simple scenario for CALL FUNCTION update_function IN UPDATE TASK .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;Alex.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Apr 2008 04:03:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/re-call-function-update-function-in-update-task/m-p/3686372#M887707</guid>
      <dc:creator>alex_georgek</dc:creator>
      <dc:date>2008-04-17T04:03:42Z</dc:date>
    </item>
    <item>
      <title>Re: RE:CALL FUNCTION update_function IN UPDATE TASK</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/re-call-function-update-function-in-update-task/m-p/3686373#M887708</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello George&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In a project dealing with material master data I had the problem that I needed to update &lt;STRONG&gt;standard&lt;/STRONG&gt; as well as &lt;STRONG&gt;customer&lt;/STRONG&gt; tables at the same time when the user pushed the SAVE button.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For the standard tables I used BAPI_MATERIAL_MAINTAINDATA_RT (retail material) and for the customer tables I created my own SAVE function modules.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How to ensure that either both (standard and custom) tables are updated or not simultaneously?&lt;/P&gt;&lt;P&gt;I created a special SAVE function module which called both the standard BAPI and my custom SAVE function modules.&lt;/P&gt;&lt;P&gt;This "wrapper" SAVE function module was then called IN UPDATE TASK.&lt;/P&gt;&lt;P&gt;This way I created a &lt;STRONG&gt;LUW&lt;/STRONG&gt; (logic unit of work) which comprised both standard and custom tables. If everything was ok both types of tables were updated, otherwise the entire transaction was rolled back.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Further reading: [Special LUW Considerations|http://help.sap.com/saphelp_nw04/helpdata/en/9f/dbae3435c111d1829f0000e829fbfe/content.htm]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Uwe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Apr 2008 04:17:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/re-call-function-update-function-in-update-task/m-p/3686373#M887708</guid>
      <dc:creator>uwe_schieferstein</dc:creator>
      <dc:date>2008-04-17T04:17:40Z</dc:date>
    </item>
  </channel>
</rss>

