<?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: SU22 documentation in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/su22-documentation/m-p/4362628#M1038329</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;SU22 contains values present in tables USOBT and USOBX tables.&lt;/P&gt;&lt;P&gt;When a t-code is executed, the t-code checks for many authorization objects with their respective values depending upon the event.&lt;/P&gt;&lt;P&gt;Just imagine the state of security if all the objects that were checked were present in USOBT and USOBX tables and subsequently transferred to USOBT_C and USOBX_C through SU25.There would be no security at all as everyone who would have access to such t-codes could do everything associated with that t-code. Thats why some very critical objects are only checked and not check-maintained. They can be manually added to certain roles depending upon the position. May be that is the reason why S_CTS_ADMI and S_DEVELOP are not maintained for OB52.&lt;/P&gt;&lt;P&gt;I am not infront of the system, but if I am not wrong for pfcg, S_AGR_USER auth object doesnot have * value check-maintained.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 24 Aug 2008 02:33:14 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-08-24T02:33:14Z</dc:date>
    <item>
      <title>SU22 documentation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/su22-documentation/m-p/4362627#M1038328</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;Does anyone have a link to a detailed documentation on SU22? I would like to find out how to read the following outputs. I have the following questions and I was hoping that reading the documentation will help:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do all of the objects listed below need to be granted in order to change posting periods?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Table TSTCA shows that OB52 requires auth objects S_TABU_DIS with fields ACTVT=02 and DICBERCLS=FC31? Should not this be sufficient and why SU22 shows all these additional objects? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If all the objects below are required by transaction OB52, why  fields and required values are not displayed by SU22 (with the exception of S_TABU_DIS)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="---------------------------------------------------------------------------------------------------" /&gt;&lt;P&gt;|U  N  C  CM Check ID      |Object                  |ObjectDescription            &lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="---------------------------------------------------------------------------------------------------" /&gt;&lt;P&gt;|.  .     .  Check                 |S_CTS_ADMI       |Administration Functions in Change and Transport System&lt;/P&gt;&lt;P&gt;|.  .     .  Check                 |S_DEVELOP       |ABAP Workbench&lt;/P&gt;&lt;P&gt;|.  .     .  Check                 |S_DOKU_AUT     |SE61 Documentation Maintenance Authorization              &lt;/P&gt;&lt;P&gt;|.  .     .  Check                 |S_PROJECT        |Project Management: Project authorization                   &lt;/P&gt;&lt;P&gt;|.  .  .     Check/maintain    |S_TABU_DIS       |Table Maintenance (via standard tools such as SM30)         &lt;/P&gt;&lt;P&gt;|.  .     .  Check                 |S_TCODE            |Transaction Code Check at Transaction Start                 &lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;.  .     .  Check&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;S_TRANSLAT&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Translation environment authorization object                &lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="---------------------------------------------------------------------------------------------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Transaction      OB52                           C FI Maintain Table T001B&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check indicator  Object     ObjectDescription&lt;/P&gt;&lt;P&gt;Check               S_CTS_ADMI Administration Functions in Change and Transport System&lt;/P&gt;&lt;P&gt;Check               S_DEVELOP  ABAP Workbench&lt;/P&gt;&lt;P&gt;Check               S_DOKU_AUT SE61 Documentation Maintenance Authorization&lt;/P&gt;&lt;P&gt;Check               S_PROJECT  Project Management: Project authorization&lt;/P&gt;&lt;P&gt;Check/maintain  S_TABU_DIS Table Maintenance (via standard tools such as SM30)&lt;/P&gt;&lt;P&gt;                            -&lt;/P&gt;&lt;HR originaltext="-------------------------------------------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Fld&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Val.from&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Val. to&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;                            -&lt;/P&gt;&lt;HR originaltext="-------------------------------------------------" /&gt;&lt;P&gt;                            &lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;ACTVT&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;02&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;                            &lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;03&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;                            &lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;DICBERCLS&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;FC31&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;                            -&lt;/P&gt;&lt;HR originaltext="-------------------------------------------------" /&gt;&lt;P&gt;Check            S_TCODE    Transaction Code Check at Transaction Start&lt;/P&gt;&lt;P&gt;Check            S_TRANSLAT Translation environment authorization object&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks!&lt;/P&gt;&lt;P&gt;Martin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Aug 2008 15:34:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/su22-documentation/m-p/4362627#M1038328</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-08-22T15:34:40Z</dc:date>
    </item>
    <item>
      <title>Re: SU22 documentation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/su22-documentation/m-p/4362628#M1038329</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;SU22 contains values present in tables USOBT and USOBX tables.&lt;/P&gt;&lt;P&gt;When a t-code is executed, the t-code checks for many authorization objects with their respective values depending upon the event.&lt;/P&gt;&lt;P&gt;Just imagine the state of security if all the objects that were checked were present in USOBT and USOBX tables and subsequently transferred to USOBT_C and USOBX_C through SU25.There would be no security at all as everyone who would have access to such t-codes could do everything associated with that t-code. Thats why some very critical objects are only checked and not check-maintained. They can be manually added to certain roles depending upon the position. May be that is the reason why S_CTS_ADMI and S_DEVELOP are not maintained for OB52.&lt;/P&gt;&lt;P&gt;I am not infront of the system, but if I am not wrong for pfcg, S_AGR_USER auth object doesnot have * value check-maintained.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 24 Aug 2008 02:33:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/su22-documentation/m-p/4362628#M1038329</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-08-24T02:33:14Z</dc:date>
    </item>
    <item>
      <title>Re: SU22 documentation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/su22-documentation/m-p/4362629#M1038330</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt;Table TSTCA shows that OB52 requires auth objects S_TABU_DIS with fields ACTVT=02 and DICBERCLS=FC31? Should not this be sufficient and why SU22 shows all these additional objects? &lt;/P&gt;&lt;P&gt;This is to tell you that OB52 does need S_TABU_DIS... (so Check/Maintain indicator) but also has the ability if used in a certain way (see the menus) to do more than just change the posting periods (so the Check indicator is set as information) - however to be able to use the menu in a certain way, the authority for it should come from a different transaction (so, one which has S_DEVELOP as a Check/Maintain indicator).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In higher releases, Chech/Maintain is now called "Proposal"...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The most important documentation on SU22 in my opinion, is that you should never change anything there. The correct approach is for SAP to change it and import the new settings via Support Packages. SU24 is the "customer equivalent" of Su22 and you can make changes there.&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>Sun, 24 Aug 2008 07:08:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/su22-documentation/m-p/4362629#M1038330</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-08-24T07:08:16Z</dc:date>
    </item>
    <item>
      <title>Re: SU22 documentation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/su22-documentation/m-p/4362630#M1038331</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;if you think, that some proposals are missing for OB52, please open a message at SAP at the component of OB52.....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;b.rgds, Bernhard&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Aug 2008 07:07:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/su22-documentation/m-p/4362630#M1038331</guid>
      <dc:creator>Bernhard_SAP</dc:creator>
      <dc:date>2008-08-25T07:07:25Z</dc:date>
    </item>
  </channel>
</rss>

