<?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: Authorization object for parameter transactions in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-object-for-parameter-transactions/m-p/2599043#M595412</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Mohan,&lt;/P&gt;&lt;P&gt;Have you check for your particular user if he/she has another role with authorization object V_LIKP_VST. It could happen that the user has the access because the value * or others shipping point number are in field VSTEL.&lt;/P&gt;&lt;P&gt;For example, if you have for two roles and different values in V_LIKP_VST for them. The final access will be the sum of both.&lt;/P&gt;&lt;P&gt;regards, Leandro&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 08 Aug 2007 13:45:02 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-08-08T13:45:02Z</dc:date>
    <item>
      <title>Authorization object for parameter transactions</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-object-for-parameter-transactions/m-p/2599040#M595409</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;I'm trying to restrict transaction VL10h for shipping point,this transaction is a parameter transaction and is not controlled by an authorization object directly.when I run a trace , transaction Vl10x shows up. The authorization object that is being checked is V_LIKP_VST.&lt;/P&gt;&lt;P&gt;Note : The requirement is when the user executes transaction VL10h he/she should be able to display only those shipping points they are authorized to.&lt;/P&gt;&lt;P&gt;Please advice.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Mohan.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Aug 2007 20:11:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-object-for-parameter-transactions/m-p/2599040#M595409</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-06T20:11:49Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization object for parameter transactions</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-object-for-parameter-transactions/m-p/2599041#M595410</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mohan,&lt;/P&gt;&lt;P&gt;For transaction VL10H you can specify values for the following fields in authorization object V_LIKP_VST:&lt;/P&gt;&lt;P&gt;-Activity: &lt;/P&gt;&lt;P&gt;01	Create or generate&lt;/P&gt;&lt;P&gt;02	Change&lt;/P&gt;&lt;P&gt;03	Display&lt;/P&gt;&lt;P&gt;04	Print, edit messages&lt;/P&gt;&lt;P&gt;18	Deliveries from coll. proc.&lt;/P&gt;&lt;P&gt;24	Archive&lt;/P&gt;&lt;P&gt;25	Reload&lt;/P&gt;&lt;P&gt;85	Reverse&lt;/P&gt;&lt;P&gt;-Shipping point: Here you must set the restriction for each group of users that are allowed for the maintenance of the shipping points that are used for delivery processing.&lt;/P&gt;&lt;P&gt;You can restrict the access through these fields.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Leandro&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Aug 2007 16:45:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-object-for-parameter-transactions/m-p/2599041#M595410</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-07T16:45:06Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization object for parameter transactions</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-object-for-parameter-transactions/m-p/2599042#M595411</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Leandro,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your reply, the problem is/was when I speicfy a value for shipping point in the object V_LIKP_VST for the field VSTEL it is not being restricted to that value.I have cheked maintained this object for the transaction VL10H in SU24 also.&lt;/P&gt;&lt;P&gt;For example: If I restrict this value to 3115 in the role the user is still able to display  shipping point 3116 0r any valid shipping point.Please advice.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Mohan.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Aug 2007 12:18:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-object-for-parameter-transactions/m-p/2599042#M595411</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-08T12:18:08Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization object for parameter transactions</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-object-for-parameter-transactions/m-p/2599043#M595412</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Mohan,&lt;/P&gt;&lt;P&gt;Have you check for your particular user if he/she has another role with authorization object V_LIKP_VST. It could happen that the user has the access because the value * or others shipping point number are in field VSTEL.&lt;/P&gt;&lt;P&gt;For example, if you have for two roles and different values in V_LIKP_VST for them. The final access will be the sum of both.&lt;/P&gt;&lt;P&gt;regards, Leandro&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Aug 2007 13:45:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-object-for-parameter-transactions/m-p/2599043#M595412</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-08T13:45:02Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization object for parameter transactions</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-object-for-parameter-transactions/m-p/2599044#M595413</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Leandro,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have checked there is no access from any other role.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;Mohan.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Aug 2007 17:47:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-object-for-parameter-transactions/m-p/2599044#M595413</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-08T17:47:17Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization object for parameter transactions</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-object-for-parameter-transactions/m-p/2599045#M595414</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Greetings Mohan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;      Were you ever able to solve this issue?  I have the same problem and I am currently working to find an answer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank You&lt;/P&gt;&lt;P&gt;   - Rollin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Aug 2007 17:14:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-object-for-parameter-transactions/m-p/2599045#M595414</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-30T17:14:42Z</dc:date>
    </item>
  </channel>
</rss>

