<?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: Controling attachment authorizations in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/controling-attachment-authorizations/m-p/10947421#M1892651</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;Appreciate your prompt reply Martin. Will look into it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 03 Mar 2015 09:19:32 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2015-03-03T09:19:32Z</dc:date>
    <item>
      <title>Controling attachment authorizations</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/controling-attachment-authorizations/m-p/10947419#M1892649</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Everyone&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we've got this issue:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If one user is attaching a document to sales contract / order&lt;BR /&gt;or quotations then other users can ba able to delete / Change the attachment. This&lt;BR /&gt;should not be permitted. Other users can be able to view or attach more documents&lt;BR /&gt;but should not be able to delete the attachment uploaded by another user.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you please advise what is the best practice to control it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Mar 2015 06:49:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/controling-attachment-authorizations/m-p/10947419#M1892649</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-03-03T06:49:13Z</dc:date>
    </item>
    <item>
      <title>Re: Controling attachment authorizations</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/controling-attachment-authorizations/m-p/10947420#M1892650</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;similar questions have been answered on this forum multiple times. Hence using a search functionality will give you an answer to your question. Summary is that you can try to use standard object provided by SAP or SAP provides a BADI that can be used to implement custom authorization checks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Mar 2015 08:10:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/controling-attachment-authorizations/m-p/10947420#M1892650</guid>
      <dc:creator>mvoros</dc:creator>
      <dc:date>2015-03-03T08:10:08Z</dc:date>
    </item>
    <item>
      <title>Re: Controling attachment authorizations</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/controling-attachment-authorizations/m-p/10947421#M1892651</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;Appreciate your prompt reply Martin. Will look into it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Mar 2015 09:19:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/controling-attachment-authorizations/m-p/10947421#M1892651</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-03-03T09:19:32Z</dc:date>
    </item>
  </channel>
</rss>

