<?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 SHD0 Transaction Authorization in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/shd0-transaction-authorization/m-p/4966891#M1157785</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We need to deactivate certain fields in CV02N document maintenance transaction (DMS) for specific document types. &lt;/P&gt;&lt;P&gt;For all other document types, all the fields of the transaction are required.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are using SHD0 transaction in SAP to create a new Z* transaction. &lt;/P&gt;&lt;P&gt;All users need to have access to both ZCV02N and CV02N..&lt;/P&gt;&lt;P&gt;However, through CV02N certain document types need to be blocked. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible to have the authorization object assigned to a SHD0 transaction variant different from the original transaction itself?&lt;/P&gt;&lt;P&gt;Is there any other approach that we can consider?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;&lt;P&gt;Sana.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 14 Jan 2009 10:25:36 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-01-14T10:25:36Z</dc:date>
    <item>
      <title>SHD0 Transaction Authorization</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/shd0-transaction-authorization/m-p/4966891#M1157785</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We need to deactivate certain fields in CV02N document maintenance transaction (DMS) for specific document types. &lt;/P&gt;&lt;P&gt;For all other document types, all the fields of the transaction are required.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are using SHD0 transaction in SAP to create a new Z* transaction. &lt;/P&gt;&lt;P&gt;All users need to have access to both ZCV02N and CV02N..&lt;/P&gt;&lt;P&gt;However, through CV02N certain document types need to be blocked. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible to have the authorization object assigned to a SHD0 transaction variant different from the original transaction itself?&lt;/P&gt;&lt;P&gt;Is there any other approach that we can consider?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;&lt;P&gt;Sana.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jan 2009 10:25:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/shd0-transaction-authorization/m-p/4966891#M1157785</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-01-14T10:25:36Z</dc:date>
    </item>
    <item>
      <title>Re: SHD0 Transaction Authorization</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/shd0-transaction-authorization/m-p/4966892#M1157786</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, were you able to resolve this? I have a similar requirement and trying to research on possible approach.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thank you in advance &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Apr 2016 07:10:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/shd0-transaction-authorization/m-p/4966892#M1157786</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-04-27T07:10:01Z</dc:date>
    </item>
  </channel>
</rss>

