<?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 How authorization comes into play in Persistent Classes in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-authorization-comes-into-play-in-persistent-classes/m-p/6458288#M1415140</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We can directly update the standard database table via persistent objects without authorization. How can i include authorization before getting update the database.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 20 Jan 2010 09:44:41 GMT</pubDate>
    <dc:creator>sudarmanikandan</dc:creator>
    <dc:date>2010-01-20T09:44:41Z</dc:date>
    <item>
      <title>How authorization comes into play in Persistent Classes</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-authorization-comes-into-play-in-persistent-classes/m-p/6458288#M1415140</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We can directly update the standard database table via persistent objects without authorization. How can i include authorization before getting update the database.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Jan 2010 09:44:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-authorization-comes-into-play-in-persistent-classes/m-p/6458288#M1415140</guid>
      <dc:creator>sudarmanikandan</dc:creator>
      <dc:date>2010-01-20T09:44:41Z</dc:date>
    </item>
    <item>
      <title>Re: How authorization comes into play in Persistent Classes</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-authorization-comes-into-play-in-persistent-classes/m-p/6458289#M1415141</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;you can directly update any table from ABAP program. So your application should have all required authorization checks before writing anything to DB (it does nor matter if you use SQL statement of persistent object). I don't think that there is a special point within persistent object for authorization check. You could use [check agent|http://help.sap.com/saphelp_nw2004s/helpdata/en/fa/f23c12330411d5992100508b6b8b11/frameset.htm] but I don't think that it is a good idea.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jan 2010 00:45:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-authorization-comes-into-play-in-persistent-classes/m-p/6458289#M1415141</guid>
      <dc:creator>mvoros</dc:creator>
      <dc:date>2010-01-27T00:45:40Z</dc:date>
    </item>
  </channel>
</rss>

