<?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: Adding New Auth Object to a Tx in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/adding-new-auth-object-to-a-tx/m-p/4488351#M1062427</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; I didnt get you ????&lt;/P&gt;&lt;P&gt;What I meant is that if the checks are added to the standard system, then they are added for everyone (with a standard system).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Julius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 19 Sep 2008 07:43:18 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-09-19T07:43:18Z</dc:date>
    <item>
      <title>Adding New Auth Object to a Tx</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/adding-new-auth-object-to-a-tx/m-p/4488343#M1062419</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am facing problem in adding client specific Auth restriction in a Tx: CJ20n.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried makig new aurth object with u201Cauth fieldsu201D containg the above fileds . And added the Auth object to Tx : CJ20n using su24. &lt;/P&gt;&lt;P&gt;But it is not checking the Auth Oject at all. I am not sure if some Authority-check needs to need to be coded in CJ20n program. I spoke to ABAPer to modify the STD CJ20n program to insert AUTHORITY-CHECK but he said it will be a huge modification and such things should be avoided, even I feel the same.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know what are the possible solutions and how to go about it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Details of the Requirement:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In Tx: CJ20n which is PS Project Builder. We need to implement a specific senario in which Project builder (CJ20n) the WBS elements are to restricted on basis of HR positions. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Assignment of WBS elements to project team is done in the same tcode. In which a Relationship between WBS element and HR postion is doneu2026.And HR postion in turn is assigned to a user id.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Requirement :&lt;/STRONG&gt; &lt;/P&gt;&lt;P&gt;Not sure of the funtionality provided by SAP of the above assignment. It just assigns team members to the WBS elements but dose not restic the  access of that WBS elements only to those assigned users.We need to restric this WBS elemets according to the assigments made here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i.e. for eg. only user whos are assigned to HR postion u201Cmanageru201D should be able to access WBS element u201CTEST(00000106)u201D&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Difficulty:&lt;/STRONG&gt;  &lt;/P&gt;&lt;P&gt;NON of the  auth objects provided by SAP in su24 contain HR position as field. Hence not able to check the postion of the user accessing the WBS element.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Further Findings:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;The above relation is stored in two different tables &lt;/P&gt;&lt;P&gt;Table 1 : PRPS&lt;/P&gt;&lt;P&gt; field name1: POSID (contains wbs project)&lt;/P&gt;&lt;P&gt;field name2: OBJNR (WBS id)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Table 2 : HRPS1001 &lt;/P&gt;&lt;P&gt;field name1: SOBID (WBS id)&lt;/P&gt;&lt;P&gt;field name2: OBJID (HR position id)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Sep 2008 07:05:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/adding-new-auth-object-to-a-tx/m-p/4488343#M1062419</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-18T07:05:15Z</dc:date>
    </item>
    <item>
      <title>Re: Adding New Auth Object to a Tx</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/adding-new-auth-object-to-a-tx/m-p/4488344#M1062420</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; I tried makig new aurth object with u201Cauth fieldsu201D containg the above fileds . And added the Auth object to Tx : CJ20n using su24. &lt;/P&gt;&lt;P&gt;&amp;gt; But it is not checking the Auth Oject at all. I am not sure if some Authority-check needs to need to be coded in CJ20n program. I spoke to ABAPer to modify the STD CJ20n program to insert AUTHORITY-CHECK but he said it will be a huge modification and such things should be avoided, even I feel the same.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think your abaper is right. Authority checks need to be in the code to work. One thing that is worth investigating is the availability of user exits in the program. Maybe there is one in the right part of the program that can be activated to create additional authorization checks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I do not know enough about CJ20n to comment on your requirements.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jurjen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Sep 2008 07:15:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/adding-new-auth-object-to-a-tx/m-p/4488344#M1062420</guid>
      <dc:creator>jurjen_heeck</dc:creator>
      <dc:date>2008-09-18T07:15:53Z</dc:date>
    </item>
    <item>
      <title>Re: Adding New Auth Object to a Tx</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/adding-new-auth-object-to-a-tx/m-p/4488345#M1062421</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Its vierd that SAP needs us to modify std code to add new authorization reqirements... &lt;/P&gt;&lt;P&gt;I belive CJ20n has something called User Fileds. But PS consultant is relectant to use it as an option for this.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Sep 2008 07:52:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/adding-new-auth-object-to-a-tx/m-p/4488345#M1062421</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-18T07:52:57Z</dc:date>
    </item>
    <item>
      <title>Re: Adding New Auth Object to a Tx</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/adding-new-auth-object-to-a-tx/m-p/4488346#M1062422</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; Its vierd that SAP needs us to modify std code to add new authorization reqirements... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Supposing you meant "weird", I have to disagree. It is impossible for a software company to satisfy everybodies' needs in advance. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;They try very hard, so quite a lot of programs come with additional authority-checks which are disabled throught SU24 by default. Also user-exits create the possibility to add authority checks or other customer enhancements without having to change SAP code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maybe someone else can comment on the user fields you mentioned. Why is the PS consultant reluctant to use those? What is the motivation not to use them?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jurjen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Sep 2008 08:01:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/adding-new-auth-object-to-a-tx/m-p/4488346#M1062422</guid>
      <dc:creator>jurjen_heeck</dc:creator>
      <dc:date>2008-09-18T08:01:44Z</dc:date>
    </item>
    <item>
      <title>Re: Adding New Auth Object to a Tx</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/adding-new-auth-object-to-a-tx/m-p/4488347#M1062423</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There are10 user fields available. I believe he want to use it for other purposes. &lt;/P&gt;&lt;P&gt;But the question here is not just about this perticulat Tx .&lt;/P&gt;&lt;P&gt; But for any other tx for which there is no std Auth ojbect which satisfy the security need , modification is nessary in the abap code it self. &lt;/P&gt;&lt;P&gt;No ther options available ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Sep 2008 08:16:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/adding-new-auth-object-to-a-tx/m-p/4488347#M1062423</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-18T08:16:00Z</dc:date>
    </item>
    <item>
      <title>Re: Adding New Auth Object to a Tx</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/adding-new-auth-object-to-a-tx/m-p/4488348#M1062424</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Actually that's &lt;STRONG&gt;the option&lt;/STRONG&gt; from SAP that it allows custom development to meet company specific requirements. I agree with Jurjen that it is not possible for SAP ( as a matter of fact, anyone) to develop something which meets everyones requirements.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Zaheer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Sep 2008 12:45:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/adding-new-auth-object-to-a-tx/m-p/4488348#M1062424</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-18T12:45:04Z</dc:date>
    </item>
    <item>
      <title>Re: Adding New Auth Object to a Tx</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/adding-new-auth-object-to-a-tx/m-p/4488349#M1062425</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Hussain &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; But the question here is not just about this perticulat Tx .&lt;/P&gt;&lt;P&gt;and...&lt;/P&gt;&lt;P&gt;&amp;gt;  But for any other tx...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have also asked such questions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your best bet is to identify the point at which you want this functionality (a function module, or a method of whatever class...) and then focus on SAP note # 11.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The idea behind this (note 11) is to differentiate between specific implementation wishes and "big enough" requirements.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Depending on the size, you might get:&lt;/P&gt;&lt;P&gt;- Nothing (choice of transaction is incorrect, or functionality is simply not foreseen)&lt;/P&gt;&lt;P&gt;- An enhancement point.&lt;/P&gt;&lt;P&gt;- A configurable or activatable check.&lt;/P&gt;&lt;P&gt;- A future standard solution.&lt;/P&gt;&lt;P&gt;- A downportable backward compatable fix.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In addition to respecting the software logistics, we should also respect other (standard) customers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Julius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Sep 2008 20:03:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/adding-new-auth-object-to-a-tx/m-p/4488349#M1062425</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-18T20:03:29Z</dc:date>
    </item>
    <item>
      <title>Re: Adding New Auth Object to a Tx</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/adding-new-auth-object-to-a-tx/m-p/4488350#M1062426</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What I can do in such a case of MIssing funtionality is check with ABAPer if some enhancement or User exit exists .&lt;/P&gt;&lt;P&gt;If not can I raise a OSS msg and ask SAP if they have a work around or if they can include it in next support pack?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;P.S.&lt;/P&gt;&lt;P&gt;&amp;gt;Julius&lt;/P&gt;&lt;P&gt;&amp;gt;In addition to respecting the software logistics, we should also respect other (standard) customers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I didnt get you ????&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Sep 2008 06:05:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/adding-new-auth-object-to-a-tx/m-p/4488350#M1062426</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-19T06:05:11Z</dc:date>
    </item>
    <item>
      <title>Re: Adding New Auth Object to a Tx</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/adding-new-auth-object-to-a-tx/m-p/4488351#M1062427</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; I didnt get you ????&lt;/P&gt;&lt;P&gt;What I meant is that if the checks are added to the standard system, then they are added for everyone (with a standard system).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Julius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Sep 2008 07:43:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/adding-new-auth-object-to-a-tx/m-p/4488351#M1062427</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-19T07:43:18Z</dc:date>
    </item>
    <item>
      <title>Re: Adding New Auth Object to a Tx</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/adding-new-auth-object-to-a-tx/m-p/4488352#M1062428</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok accepted the SAP standards. ANd have to find out some unique way for work with my unique requirement.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Feb 2009 05:08:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/adding-new-auth-object-to-a-tx/m-p/4488352#M1062428</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-02-11T05:08:52Z</dc:date>
    </item>
  </channel>
</rss>

