<?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: BAPI_MATERIAL_SAVEDATA and roll back in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-material-savedata-and-roll-back/m-p/11721804#M1948235</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When you simulate the creation of the material then the database will not be updated.&amp;nbsp; You therefore shouldn't need a rollback at that point.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However,&amp;nbsp; to get to the functionality that you want in that nothing should be created if there is a problem for example with a storage location not existing or something then you can pass all of the view data to the Bapi in one call using the Material header structure with the _View parameters checked,&amp;nbsp; and with all the relevant structures for the views populated.&amp;nbsp; You can then check the returned messages and if there is a problem then Rollback work otherwise commit work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To do the operations as a set of discrete Bapi calls means that you will need to commit the data for each view after the basic data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you just need to simulate the operation,&amp;nbsp; set the simulate flag as you are doing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest that you have a read about Logical Units Of Work (LUW's) and Rollback/Commit statements.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rich&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 21 Jun 2016 11:37:45 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2016-06-21T11:37:45Z</dc:date>
    <item>
      <title>BAPI_MATERIAL_SAVEDATA and roll back</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-material-savedata-and-roll-back/m-p/11721803#M1948234</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;im creating basic data by using bapi_material_Savedata in the simulation mode , once i have created basic data i done the roll back..now im trying to create plant data for the material&amp;nbsp; by calling bapi again here im doing view wise upload ,,now system thro's error material does not exist. because i have done the roll back...my requirement is i have to roll back the basic data after simulating all the views for the material ,,how to acheive this...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Jun 2016 11:30:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-material-savedata-and-roll-back/m-p/11721803#M1948234</guid>
      <dc:creator>former_member211992</dc:creator>
      <dc:date>2016-06-21T11:30:59Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_MATERIAL_SAVEDATA and roll back</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-material-savedata-and-roll-back/m-p/11721804#M1948235</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When you simulate the creation of the material then the database will not be updated.&amp;nbsp; You therefore shouldn't need a rollback at that point.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However,&amp;nbsp; to get to the functionality that you want in that nothing should be created if there is a problem for example with a storage location not existing or something then you can pass all of the view data to the Bapi in one call using the Material header structure with the _View parameters checked,&amp;nbsp; and with all the relevant structures for the views populated.&amp;nbsp; You can then check the returned messages and if there is a problem then Rollback work otherwise commit work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To do the operations as a set of discrete Bapi calls means that you will need to commit the data for each view after the basic data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you just need to simulate the operation,&amp;nbsp; set the simulate flag as you are doing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest that you have a read about Logical Units Of Work (LUW's) and Rollback/Commit statements.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rich&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Jun 2016 11:37:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-material-savedata-and-roll-back/m-p/11721804#M1948235</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-06-21T11:37:45Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_MATERIAL_SAVEDATA and roll back</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-material-savedata-and-roll-back/m-p/11721805#M1948236</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Peter,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you state the requirement in detail? Why do you want to rollback after the creation of the BASIC data view.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Jun 2016 11:42:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-material-savedata-and-roll-back/m-p/11721805#M1948236</guid>
      <dc:creator>AniketB</dc:creator>
      <dc:date>2016-06-21T11:42:20Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_MATERIAL_SAVEDATA and roll back</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-material-savedata-and-roll-back/m-p/11721806#M1948237</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;He has to simulate the creation of the views.&amp;nbsp; He is rolling back because he is under the impression that there are db records waiting to be committed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Jun 2016 12:01:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-material-savedata-and-roll-back/m-p/11721806#M1948237</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-06-21T12:01:24Z</dc:date>
    </item>
  </channel>
</rss>

